option tale error

  • Resolved Flyhead

    (@bukers)


    9 years, 11 months ago

    I forgot: we have this following warning and forwarded it to our hosting service. They have no idea either. I can post the hosting name here if needed to, but they are one of the major one and a better service already. So what should we do?

    The plugin settings (wpsso_options) have been upgraded, but WordPress returned an error when saving them to the options table (WordPress update_option() function did not return true). This is a known issue in some shared hosting environments. The plugin will attempt to upgraded and save its settings again. Report the issue to your hosting provider if you see this warning message more than once.

    https://www.ads-software.com/plugins/wpsso/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    Have you seen this error more than once? The plugin will attempt to save it’s upgraded settings — issuing an error when it fails — but usually it succeeds on the second try.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Can I assume this issue is resolved?

    js.

    Thread Starter Flyhead

    (@bukers)

    The error is still there. I have just upgraded WPSSO UM hoping that it will help. Didn’t.

    Plugin Author JS Morisset

    (@jsmoriss)

    There’s really not much I can do if your WordPress update_option() does not return true when WPSSO update’s its option… The WordPress documentation is quite specific:

    https://developer.www.ads-software.com/reference/functions/update_option/

    Return: (bool) False if value was not updated and true if value was updated.

    WPSSO simply reports the fact that update_option() did not return ‘true’. The funtion may also return false if there was no change, but WPSSO checks for this before calling update_option().

    I wonder if another plugin might have hooked into update_option and is returning an incorrect value (1 instead of true, for example). Have you tried disabling other plugins to see if WPSSO is then able to save it’s option?

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Where you able to track down the reason why update_option() was returning an incorrect value?

    js.

    Thread Starter Flyhead

    (@bukers)

    Thanks for following up. We were able to spend only little time in doing this. Will do the numerous recent updates and see if the problem persist and let you know.

    Thread Starter Flyhead

    (@bukers)

    The error message is gone after updates. It seems to me it was a conflict with the favicon plugin. We are not sure though. Maybe it was just the cache lagging to show this plugin, it was perhaps your update harmonises with WP better now.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘option tale error’ is closed to new replies.