That’s strange, what version of NextGEN are you running?
Thread Starter
staze
(@staze)
NextGen 2.1.23. For reference, this is on a multisite install.
Thread Starter
staze
(@staze)
Also, running PHP 5.6.18, WordPress 4.2.2.
Ok, are the plugins (nextgen and EWWW) activated multisite, or are you activating them on individual sites?
Thread Starter
staze
(@staze)
Previously, ewww was multisite activated, and nextgen was individual site activated. While attempting to activate ANY other plugins, I would get the error message shown (well, I’d get an error 500 in a browser, but the logs would show the “C_Gallery_Storage” error).
Activating both on an individual site works. So it would seem to be something with EWWW multisite activated?
That is plausible, as I only test multisite with Nextcellent. All my nextgen testing is done on single-site. I think I have another multi-site install that I can use for testing, so I’ll see what I can find out.
Thread Starter
staze
(@staze)
Awesome, thanks.
Note that NextGen was NOT enabled on the primary site in the multisite setup, just one of the sub-sites. So I almost wonder if EWWW was failing because of that.
Anyway, let me know. =)
good information, when I activate them both network-wide, everything seems ok, so i’ll try that next
Hmm, I get no errors no matter how I activate NextGEN if EWWW is active network-wide.
Thread Starter
staze
(@staze)
Interesting. okay, let me try to recreate.
Thread Starter
staze
(@staze)
okay, so, have two sites. Primary and Secondary.
Primary site has NextGen Deactivated, EWWW activated.
Secondary site has NextGen activated, EWWW is deactivated.
Network Activate EWWW.
Now, go to the secondary site, in plugins, and attempt to activate ANY other plugin. Immediate Error 500, and the log shows that same C_Gallery_Storage. =/
Hmm, still getting no problems. I wonder if it has anything to do with a php cache or apache. I’m running nginx on this particular server, and getting no problems with that scenario.
Can you check to see if your webhost or server is employing a php cache like apc or the like?
Thread Starter
staze
(@staze)
definitely running opcache. Hmm, that does make some sense.
Okay, let me see if that is it.
Thread Starter
staze
(@staze)
nope, same result. the webhost does use lsphp… but that shouldn’t be an issue.
Think of any other debugging I could enable?
And just confirmed, EWWW doesn’t need to be network enabled. Both NextGen and EWWW enabled cause the issue. It definitely seems to be EWWW seeing NextGen is enabled, but then bailing because it can’t find that Class. =/
When you say lsphp, you mean Litespeed, right? If so, I can setup a dummy install on my regular webhost that uses Litespeed.
