Viewing 15 replies - 1 through 15 (of 37 total)
  • Thread Starter flokohlert

    (@flokohlert)

    Version 2.3.1 works
    Thank you!

    Plugin Author JS Morisset

    (@jsmoriss)

    If you want to try, I just tagged v2.4.1, which should fix that problem…

    https://downloads.www.ads-software.com/plugin/nextgen-facebook.2.4.1.zip

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Which version of WordPress are you using? The “0 is a protected WP option and may not be modified” seems to be a known issue with older WP MU sites…

    Thanks,

    js.

    Thread Starter flokohlert

    (@flokohlert)

    Hi!
    I′m using WP 3.5.
    Thanks

    Plugin Author JS Morisset

    (@jsmoriss)

    It’s hard to tell where the error might be coming from — Google says it was/is a bug, that might be related to some faulty entries in the DB options table… About all I can do is try to add extra checks in the code to make sure all input/output related to options is super tight. I’ve improved the activate() function with some extra checks that *might* help.

    You could try installing the current dev version at https://downloads.www.ads-software.com/plugin/nextgen-facebook.zip.

    Have to tried uninstalling the plugin? I doubt the problem is related to the NGFB options entry, but just in case, uninstalling the plugin would remove that options entry. I suspect it’s something else in the DB that’s having this affect though…

    Let me know if the dev version works out for you.

    Thanks,

    js.

    I already said in the other read but I had the same error and it went away after installing version 3.0 of the plugin.

    I also had version 3.5 of WP (with my custom theme if that matters).

    Installing 3.0 version did not go smoothly trhough. On first try I got PHP error telling that “headers had already been sent” (I already lost the exact error message so can’t copy paste it here). After this I got WP error message on the plugin page that Facebook OG plugin has been disabled because of some error. This caused the whole plugin to disappear from the list, I could not even delete it the normal way. If I tried to install it again, it didn’t let me, I got only the “details” option when I searched the plugin, no “install” option. The solution to fix this was to delete the plugin folder from the server, then go search the plugin again. This time it was again possible to install it and it installed smoothly without error.

    Currently the plugin is fully working on my site.

    Plugin Author JS Morisset

    (@jsmoriss)

    I’ve added extra error handling when reading the options in v3.0.99, currently the release candidate for v3.1.

    You can pickup a copy from:

    https://downloads.www.ads-software.com/plugin/nextgen-facebook.zip

    This should/will fix the “0 is a protected WP option and may not be modified” error.

    Thanks,

    js.

    The same for me, v3.0.99 does not work and i get the same message.

    The same problem for me after update NextGen Facebook v3.1. The old version v3.0 works fine!

    Plugin Author JS Morisset

    (@jsmoriss)

    Ok, I’ve made some changes to the current dev version which may help… https://downloads.www.ads-software.com/plugin/nextgen-facebook.zip

    – Instead of using update_option() when activated, I’m using add_option(). It might make a difference, I don’t know (they’re almost the same).

    – I added an optional constant you can use. Define it BEFORE you activate the new dev version.

    define('NGFB_RESET', true);

    This will reset the options every time you activate the plugin, so don’t leave it in your wp-config.php. ??

    js.

    Even after update plugin on version 3.1.1 still doesn′t work. I′ve got own custom theme based on Twenty Eleven.

    Plugin Author JS Morisset

    (@jsmoriss)

    I’ve tweeked a few things in the upcoming v3.1.2, so you could try that one:

    https://downloads.www.ads-software.com/plugin/nextgen-facebook.zip

    Also, if you’re not working on a production site, maybe you could turn on debug mode and let me know if there are any significant errors?

    define('WP_DEBUG', true);

    Alternatively, you can send debug out put into a file by adding:

    if ( WP_DEBUG ) {
            define('WP_DEBUG_LOG', true);
            define('WP_DEBUG_DISPLAY', false);
            @ini_set('display_errors',0);
    }

    The debug file is located in wp-content/debug.log.

    The Blackbox plugin might be an alternative to using WP’s debug mode. I run Blackbox on my dev site pretty much all the time. ??

    Thanks,

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    FYI – I just checked in some new code with improvements in the NGFB::sanitize_options() method. This *should* help with any options-related issues…

    https://downloads.www.ads-software.com/plugin/nextgen-facebook.zip

    Give it a spin and let me know if it fixes the issues you’re having.

    Thanks,

    js.

    Version wordpress 3.5, Theme Catch Box version 1.7 Latest nextgen-facebook version. Still error (in Dutch)

    0 is a protected WP option and may not be modified

    Still same problem. ??

    There is my debug.log after activation newest version NextGen Facebook.

    https://temp.lm-blog.cz/files/debug.log. hopefully it will help.

Viewing 15 replies - 1 through 15 (of 37 total)
  • The topic ‘0 is a protected WP option and may not be modified’ is closed to new replies.