Since last week I noticed that backups I try to create from the manager fail. In the SQL file I see that the backup runs up to and including table modx_keyword_xref, then it stops. When I make a backup through phpmyadmin I get a complete SQL backup as usual.
According to the hosting company no changes in versions of MySQL and PHP have taken place. Has anyone had similar experiences or have a hint as to where I can look?
Thanks in advance,
I could solve the problem by exporting the database with phpmyadmin using the same parameters that modxcms uses. The standard sql file that phpmyadmin creates, contains different characters for special characters such as Ã« and is therefore not properly imported into my testing modx installation and probably also not on the production version.
Can anyone tell me where to find the export parameters that modx uses when exporting an sql file?
Have a look at "manager/actions/bkmanager.static.php
", down near the bottom of the file.
I looked at the bkmanager.static.php file but soon realised that would not be useful as I already know that the database parameters canâ€™t be the cause of this problem. Backup of the database starts correctly but halts after table modx_keyword_xref. No error message, nothing except the fact that I see that my backup file is much shorter than it used to be.
On my local version (in an XAMPP environment) backup proceeds as usual and I get the complete file. I asked my hosting provider if MySQL or PHP version or something else have changed; they say nothing changed but their PHP version went from 5.2.9 to 5.2.10. My local PHP is at version 5.2.6
This has me looking at bkmanager.static.php again: does this file contain functionality that could have problems with PHP 5.2.10?
Could an upgrade to a newer modx version solve my problem? Now I use 0.9.6.2 to my full satisfaction, but if necessary I will upgrade to 0.9.6.3
thanks for your answers,
Last weekend I upgraded to Evo succesfully! Then I tried to backup and I had the same problem...But I decided to empty the log after I saw that the modx_manager_log table was over 1 MB. And guess what: the backup works again!
My salutations to the modx developers by the way for making the upgrade such an easy and reliable process!
Itâ€™s always a good idea to clear the manager actions log and the system events log, as well as clear the site cache, before doing a backup.
probably something to do with memory limits or timeouts; phpMyAdmin is a lot more complex.