Cloner 1.1 Problem
Development and Programming
Ok, this does appear to be a bug, but not the one I was originally thinking; it is a bug with isset() and empty() in certain versions of PHP. I have left a test.php file on your server that duplicates the error, which you can share with your host if necessary. (PHP bug report)
<?php
error_reporting(E_ALL);
ini_set('display_errors', 1);
$str = '';
foreach (array('yee', 'yaw', 'yat') as $val)
{
$foo = (isset($str[$val])) ? 'foo' : 'bar';
}
?>PHP 4.3 was released 5 years ago, so updating to a current stable release of 4.4 should be more than sufficient, though you might use this opportunity to try to put gentle pressure on your host to update to PHP 5.
Thanks for your Help Derek. Much appreciated.
Derek, can you help me with Cloner please. I’ve downloaded and installed and the Clone button appears in EDIT, but when I click it, I get a blank entry, not a clone. Actually it’s not totally blank, there are digits in the fields, 1’s and 3’s as I recall. But that’s all. Even weirder, with Cloner activated, EVERY entry goes blank even if I just open it to edit it. I de-activated Cloner without having saved anything, and thank God everything went back to normal. It’s very scary, I resorted to cut and paste which is much more work, but safe.
You using any other extensions, johnnyb? And what version of EE are you using?
This is the first and only extension I’ve ever used.
The version, unfortunately, is the ancient 1.4.1. I didn’t mention this right off because when I did so on the How To forum, Ingmar responded with “It’s very hard to say, but you definitely should upgrade. EE 1.4.1 is almost 3 years old.” I’m not sure what “it’s very hard to say” means, but as “you really should upgrade” is long way from saying that Cloner won’t work under 1.4.1, I suspect it’s something along the lines of not having a copy of 1.4.1 available to work with, or not being familiar enough with it to know where to go with this problem. I switched over to you at the Extensions forum hoping you might not make upgrading the only option.
I’d like nothing better than to upgrade, but I’ve been unable to do so for the six months or so I’ve been recommending it to my client. If it were a simpler process, I could make the case for doing it a lot better. But it’s not at all the easy “click to install latest version” I’m used to with apps. I can’t even describe what’s involved, especially how long the process will take, clearly enough to get an OK. After slogging through the complications of the documentation for hours, it seemed to my throbbing head that it would take several sessions, many more hours of work than I put into maintaining the site. I’ve pretty much given up on upgrading. But I’d really like to be able to clone entries.
Well, you really do need to come to grips with being familiar how to update ExpressionEngine. Updating your installation is a fundamental part of using web based software; in fact, if you read your host’s Terms of Use, most demand that you keep reasonably up to date, primarily for security issues. Three updates since 1.4.1 were security related, so it’s pretty imperative that you take the time to do this. My recommendation on that front is to start a new thread in the how-to asking for suggestions from other users both on how they handle updates in a practical manner, as well as how they handle explaining it or contracting it with their clients.
As for the current problem, do you have error reporting enabled (Admin > System Preferences > Output and Debugging) as well as having error reporting enabled in the PHP environment (Admin > Utilities > PHP Info - looking for display_errors)? I suspect you do not, and that a PHP error would reveal the source of the problem, be it a version compatibility problem or something else.