sylgour
Forum Replies Created
-
Rolled back the database, problem fixed. Now I have to reload all the galleries we had loaded up since updating to NextGEN 2.0.61 🙁
Anyway, again, my question is, can we update WordPress to 3.9 with NextGEN at the 1.9.13 version? Anybody? We are now at WordPress version 3.8.3.So here is the latest scoop: after pulling our hair out trying to figure out what happened with our resource usage, we decided to go back to our website state, a few days before 3/28/14, which is when we upgraded NextGEN to version 2. We just checked the resource usage after a day, and it’s back to normal, however, rolling back the plugin of course broke our website. I’m trying to roll back our database to it’s previous state now, so hopefully that will fix our problem. At least we will have a happy host, without having to move to a VPS (costly). Question though, if we do not upgrade NextGEN to it’s latest version, will it be OK to upgrade WordPress itself?
Hi ph_remy,
After some surfing, I did find that post. The part that fixed my problem was one you added to the thread:
What you can do, if you have “edit” access to the source files on your web host is to make a manual change in the “update” method.
What I would suggest is the following:
– first and foremost, backup your site (!)
– then copy the original wp-content/plugins/nextgen-gallery/non_pope/class.photocrati_installer.php file “somewhere” safe (a directory outside of your document root would do)
– in the wp-content/plugins/nextgen-gallery/non_pope/class.photocrati_installer.php file, locate the line of code (should be line number 122 or there about) that says: $last_module_list = self::_get_last_module_list($reset);
– Just before that line, include a line that says $reset = TRUE;
– Then deactivate and reactivate NextGen Gallery
– Reinstate the original version of the wp-content/plugins/nextgen-gallery/non_pope/class.photocrati_installer.php file from where you copied it.In theory, this should trigger the NextGen installer to recreate the Display Types posts (which is the info that is shown on both the Attach to Post dialog as well as on the Settings page).
Thank you very much, you are a lifesaver. Now if I could just figure out how to not have it happen again! I truly believe there is a conflict with one of the other plugins on our site. Also having a problem since upgrading NextGEN, with serious increase in resource usage to the point of having to move to VPS. Not liking it one bit. Do you think downgrading back to a previous version of NextGEN would solve my problem?