Possible fix for "0 is a protected WP option and may not be modified"

  • ResolvedPlugin Author JS Morisset

    (@jsmoriss)


    12 years, 1 month ago

    In some rare cases, there seems to be an issue when upgrading from NGFB v1.x/2.x to NGFB v3.x — WordPress seems to think a protected option name (‘alloptions’ or ‘notoptions’) is being updated, though it is not. NGFB only ever updates one option name, which is ‘ngfb_options’. This problem has been reported by many, for several different plugins, themes, etc., not just NGFB. ?? Hopefully the WordPress developers will address the issue before too long. In the meantime, you can try the following procedure:

    1) Delete the existing nextgen-facebook plugin folder.
    2) Go to the WordPress plugin admin page. WP will deactivate NGFB since the plugin is missing.
    3) Add the following to your wp-config.php file and re-install NGFB.

    define('NGFB_RESET', true);

    4) Go to the NGFB settings page and save the new default settings.
    5) Remove the NGFB_RESET entry from your wp-config.php file.

    If you need to re-install an older version, you can find them here: https://www.ads-software.com/extend/plugins/nextgen-facebook/developers/

    js.

Viewing 9 replies - 1 through 9 (of 9 total)
  • esnieto

    (@esnieto)

    I’m at a loss. I updated all of my plugins this morning, NextGEN Facebook being one of them, and am now locked out of my site – the dashboard, the homepage (www.erinsnieto.com), everything.
    I am finding your suggestions to remedy the error (at which my eyes are kind of crossing, as I am not a programmer, just an owner of a humble website), but for the moment, I have no way of accessing my page. Suggestions for access when a blank page reading “0 is a protected WP option and may not be modified” is ALL that is left of my site?

    Thanks in advance,
    Erin

    Plugin Author JS Morisset

    (@jsmoriss)

    Do your have FTP access to your site? Pretty much all hosting services offer this…

    You can FTP to your website and remove the nextgen-facebook.php file from the wordpress/wp-content/plugins/nextgen-facebook/ folder.

    The next time you visit the admin interface, the plugin will be disabled automatically.

    After that, just add the following to your wp-config.php file before re-installing:

    define('NGFB_RESET', true);

    js.

    I’ve been trying to completely remove this plugin. Is there anything I’ve missed besides the usual deactivate/delete and DB scan for NGFB options? I’m still getting the “0 is a protected WP option and may not be modified” error.

    Just wanted to cover my bases before looking elsewhere. But the only search for this error only comes up with threads/posts related to this plugin (which I have used and had issues with on my install).

    Thanks!

    -Stephen

    Plugin Author JS Morisset

    (@jsmoriss)

    The 0 is a protected WP option and may not be modified error is a known issue with other plugins and themes as well — I just seem to provide better support than most plugin authors. ??

    To completely remove NGFB manually, you can delete the plugins/nextgen-facebook/ folder and if you have access to MySQL (using phpmyadmin for example), remove the single ‘ngfb_options’ entry in the ‘options’ table. NGFB stores all it’s settings under one table entry, so it’s pretty easy to cleanup. ??

    Let me know if you figure out what was causing the issue, even if it’s not related to NGFB.

    Luckily this problem is a rare exception, and in the case of NGFB, seems to only happen when upgrading from v2.x to v3.x.

    Thanks,

    js.

    I just experienced this problem.

    Tried deleting everything and didn’t work. Even tried updating to 3.7 and still the same. It was a minor update from 3.5.X/3.6 or so.

    I’ll try to access the database and find that NGFB as define(‘NGFB_RESET’, true); didn’t work either.

    FYI I did the update using the automatic update UI from WordPress and updating 3 or 4 plugins at the same time. This is the only one that fails.

    Plugin Author JS Morisset

    (@jsmoriss)

    If you have access to the database tables, you can look for and delete an ngfb_options entry in the wp_options table (replace wp_ with your chosen prefix). Using the NGFB_RESET constant would have done the same, so I’m not sure this will be enough. You may have some corrupted entries in your table that happened to trigger this.

    The “0 is a protected WP option and may not be modified” problem can happen to any plugin or theme, generally when upgrading, and common wisdom suggests it may be related to a corrupt or empty entry in the options table.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    FYI – Known bug with WP.

    https://core.trac.www.ads-software.com/ticket/23289

    js.

    I’ve been receiving the below error since Jan on my site (thepassportreport.com):

    0 is a protected WP option and may not be modified

    I’ve tried to delete the NGFB plugin via FTP as other posts have suggested as I cannot log into my site at all. Unfortunately, I’m not very technical so I don’t know how to reload the plugin with the bug fix. I’m to the point that I’d be willing to pay someone to fix my site for me. Any suggestions of someone who can assist as I am clearly not qualified to correct this with my knowledge base?

    Thank you,

    TPR

    Plugin Author JS Morisset

    (@jsmoriss)

    If you delete the wordpress/wp-content/plugins/nextgen-facebook/ folder, WordPress will disable the plugin automatically. From the admin interface, you can then download and install the latest version. The “0 is a protected WP option and may not be modified” error was finally fixed in v4.0.2, so the latest version should work fine for you. ??

    Thanks,

    js.

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