Logan Yott

I too am experiencing this issue. If I install v3.3, site loads up with no problem. If I bump up to v3.4 or v3.4.1, I get the mysterious WSOD with no error messages…anywhere.

I’ll try out the recommendations and if they don’t work, hopefully provide some more context for how this is happening.

Is that report in a support thread? Running into a few more issues but I want to see if they’ve already been reported/worked on before creating new threads.

Thanks!

Hi Cais,

I tried Reset Option and clearing the image cache and I’m still getting the error. I haven’t been able to see it locally, so I’m assuming it must be related to Pantheon’s distributed filesystem? I’ll see if I can get a stack trace of the issue.

I checked out version 2.0.81 from your bitbucket repo (hoping maybe this problem would disappear).

While the error location changed, it appears to be the same thing happening.
Fatal error: Call to a member function get_entity() on a non-object in /path/to/wordpress/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/datamapper/class.custompost_datamapper_driver.php on line 390

Any ideas would be appreciated! Alternatively, if I should insert a logic check here and submit a PR, let me know and I will be happy to do so.

Thanks!

Hi Marin,

Thanks for the quick response and running those tests. At least I now know the issue isn’t systemic. Unfortunately, I still haven’t found a resolution.

Since it clearly isn’t the plugin though, I guess it’s time to start flipping everything off and turning it back on one by one.

Did either of you find a resolution for this? I know the plugin has been deprecated but moving to qTranslate-x isn’t an option for me right now and this is a seriously annoying issue.

I’ve found that the extra tags only happen on the first qtrans_integrate call (either a timeout or switching languages) but I can’t find what function is injecting the extra tags.

Whoops. Forgot to mark as resolved.

Welp, this ended up being a problem in my theme I just discovered.

Sorry for taking your time. Thanks for the awesome quick support though! It’s much appreciated. You have an awesome plugin. ??

After doing some digging, I found that the widgets are getting saved into postmeta on the back end, so I assume the back end is working.

Existing widgets still display accurately. However, when a new widget is added or an existing one is removed/re-added, they don’t display on the frontend.

I’ll see if non-ww widgets show up in the sidebar that my corrals are located in to make sure that my theme hasn’t broken somehow.

Hi Jonathan,

I’m running WordPress 3.9.1. I’ve tried doing this in the latest versions of Chrome, Safari, and FF.

I’ve tried adding the widget to the proper corral in a preset and assigning the preset to the page with no luck.

Oddly enough, I can see the serialized data in the postmeta for the page I’m trying to add it to. Is there somewhere during the fetch and render I should look?