NextGen V2.1.56 Output Bufferring Never Closes and Breaks Multiple Other Plugins

  • Resolved SooBahkDo

    (@soobahkdo)


    8 years, 4 months ago

    Hello,

    We have NextGen network activated on a WP 2.61 multisite network.

    The only reason we have NextGen network activated is so the import from media library tools will appear. They will not appear when NextGen is activated on a site-by-site or on a single site.

    It would be an improvement to allow access to those tools when NexGen is activated on a single site of a multisite network or site-by-site on a multisite network.

    After upgrading to 2.1.56 we could no longer connect Jetpack to Worpress.com due to this error:

    Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. Please check to make sure https://xxxxxxxxx.com/xmlrpc.php is working properly. It should show ‘XML-RPC server accepts POST requests only.’ on a line by itself when viewed in a browser and should not have any blank lines or extra output anywhere. Find out how to fix this issue here: https://jetpack.com/support/getting-started-with-jetpack/what-do-these-error-messages-mean/blank-lines-xmlrpc/

    The translation plugin Prisna (in use on one subsite of the network) also ceased working.

    Our developer reported the following findings:

    ******************************************

    Jetpack / XML-RPC issue

    After some debugging, I found that the NextGen gallery plugin was the reason the XML-RPC feature stopped working. The plugin starts output buffering, but never closes it which means the output is never displayed.

    It looks like this plugin was updated on the 29th of October so you may want to get in touch with the developers and see if they are aware of this issue.

    Prisna Translation Plugin Issue:

    Any attempt to translate resulted in the following message: “Invalid JSON response” as the AJAX request didn’t return a response. I discovered that the issue was once again linked to output buffering being left open by the Nextgen Gallery plugin.

    I installed and tested the NextGen Gallery plugin locally without any issue and after going through their code, I noticed they had added functionality to disable the resource management (which is where all these output buffer issues are caused). They disable it if certain plugins are enabled such as AdminerForWP, Cornerstone & Genesis Tabs, so I don’t know if this is a bug within their plugin or simply an incompatibility between certain plugins that they can’t resolve.

    I’ve defined the constant that disables Nextgen Gallery resource management within the wp-config.php file; this has resolved all the output buffering issues. I cannot say which plugin may be conflicting with it, though, not without going through all them disabling/re-enabling, etc.

    ******************************************

    Any assistance would be appreciated.

    Thanks

    • This topic was modified 8 years, 4 months ago by SooBahkDo.
    • This topic was modified 8 years, 4 months ago by SooBahkDo.
    • This topic was modified 8 years, 4 months ago by SooBahkDo.
    • This topic was modified 8 years, 4 months ago by SooBahkDo.
Viewing 1 replies (of 1 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @soobahkdo – As your “developer” noted, it is likely a specific conflict with another active plugin and not necessarily the ones you are currently referencing. Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?

    If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.

    Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.

    If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.

    Thanks!

    – Cais.

Viewing 1 replies (of 1 total)
  • The topic ‘NextGen V2.1.56 Output Bufferring Never Closes and Breaks Multiple Other Plugins’ is closed to new replies.

Tags