Support

Hi,

Firstly, I hope I've posted in the correct category? I couldn't see a specific 2.4 category but saw other 2.4 related posts here so forgive me if I've got it wrong.

My problem is that I have just upgraded from 2.4.1 from 2.4 (and before that was using the beta) but when I run a backup, I now get the following message as soon as I start the process:
Fatal error: Call to a member function update() on a non-object in /libraries/joomla/html/editor.php on line 196

After upgrading I did manage 1 backup without any issue. However, the 2nd time I ran it, the process failed halfway through so I deleted the archive and ran the process again. That's when I then received the error above.

The error is being returned on a development site. The same live site (which was updated via a JoomlaPack 2.4.1 archive 48 hours earlier) runs the backup process without any problem so the error I am getting seems to be specific to the development installation.

I have tried uninstalling JP and then re-installing several times without success. I also tried reverting to 2.3.3 but that also returned the same error.

The only difference between the development site and the live site is a number of new components and plugins have been installed since the last backup 48 hours ago. This leads me to think that perhaps one of these is causing the issue. But, before I go and remove them one by one and consequently loose 2 days worth of development work, I would appreciate if anyone can offer some insight as to what might be the problem.

I have attached the log file and the site is hosted on GoDaddy.

Many thanks... JoomlaPack_Debug_Log-20100120.zip

The error message mentions the editor, we've had occasional problems with third party editors in the past. Try switching the default editor for the user doing the backup to TinyMCE or no editor. I don't think this is it because the log is too long.

Try switching your backup to the jpa format. I could never get the zip format to work after GoDaddy's June 2008 server changes. I would get a timeout every single time. The jpa format is a little easier on server resources.

This is probably a silly question, but do you have enough disk space on your host account?

Dale to the rescue (again)!

That was it. I switched to the .jpa format and also switched editor to "No Editor" and then ran a successful backup. Of course now that I look at the error message, it seems obvious that the cause was related to the editor. For the record, I was using JCE 1.5.7 as my editor.

Thanks again for your help Dale. JoomlaPack rocks!!

I use JCE too and mine doesn't interfere with JoomlaPack. The error message led me there, but those editor errors are usually fatal, the backup stops immediately. I'll buy that the timeout was caused by the extra overhead in the zip format. At your convenience, switch the editor back to see if there is still a problem.