- This topic has 15 replies, 6 voices, and was last updated 13 years, 9 months ago by
.
-
Posts
-
After update, desactivate and activate this new version, all events, locations, parameters… are lost.
Tables wp_dbem_xxx are recreated
Did you have the setting “Delete all EME data when uninstalling?” activated prior to the deactivation?
I always unset this parameter upon activation, so unless this was activated no data is deleted. And no other persons have mentioned this as well.
Edit: can you reproduce this? I mean: if you deinstall 3.3.1 + all eme tables (set the option mentioned above before deactivating then), reinstall 3.3.0, add some events and then update again, are the events still there?
Hi Franky.
I mentioned this to you with version 3.3.0. I use google Chrome BTW.
Cheers
Eric
Well, but I can’t reproduce this and I tried several updates …
So I need other people telling me they can reproduce this
I have had the same issue; everything gone upon reactivation. I’m doing a database restore to bring the tables back, but not sure if that will help.
Database restore brought everything back.
I can successfully restore the data from backup, but when I try to deactivate and reactivate, everything is overwritten again.
I don’t have that problem here. I frequently deactivate, upgrade to the latest trunk version, and reactivate without ever losing anything in the database.
I wonder if a malfunction caused by use of an obsolete version of PHP might cause data loss. What version of PHP is the server using?
Whether or not use of an obsolete version of PHP is causing this particular problem, I was just thinking in relation to this that user and developer frustrations in having to troubleshoot that class of problems could be reduced if EME checked the PHP version upon activation and displayed a warning if the version is less than 5.
PHP on my server is 5.2.14. I’m looking for the place in the code where the tables are getting dropped or a place where I can check the setting of the deactivate/activate parameter to see where it was set. I don’t think that I had it set to destroy data, but I’m not sure. Just started using the plugin on Monday.
Well, the parameter is set in the Settings page (called “Delete all EME data when uninstalling”). The corresponding WP option name is “eme_uninstall_drop_data”.
I check for this in events_manager.php (see function _eme_uninstall())
and I explicitely set this parameter to “0” upon activation:
update_option(’eme_uninstall_drop_data’, 0);
so it’s puzzling …
Check in the wp options table if this parameter has anything else but “0” in it after activation. What WP version are you using?
If you want: I can debug this, but I need ssh/ftp and WP admin access for this … my mail: liedekef [at] telenet.be
All is fine now. I checked the wp-options and sure enough, some idiot (that would be me) had set the eme_uninstall_drop_data to 1. I’m not sure why I would have done this, but I’ll plead unfamiliarity with the plugin. After a little session with phpMyAdmin to reset the parameter, all is well. This is a great plugin and is saving me a lot of time! Thank you for the support and I’ll try to add to my donation!
The only bug involved was letting me install it.
The editor will not allow you to insert a photo. The add image dialog box looks the same except the insert section image section near the bottom does not appear. When you close out the add image box it hangs and crashes WordPress.
I was also prompted by WordPress to deactivate and re-activate due to a database error. I lossed all events.
First of all, it’s not possible to crash wordpress … it would mean it crashes apache/iis, which would be a bug in php.
The image button doesn’t appear because wordpress doesn’t allow it to appear, read my last post here:
http://www.e-dynamics.be/bbpress/topic.php?id=106
The deactivation/reactivation issue: I never delete events unless you activated the option “Delete all EME data when uninstalling” (see above). I clarified that option a bit more in the trunk version and adapted the warning for deactivation so you can still check this setting.
Btw: please open a seperate post in the bug section to report bugs.
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.