• ricardomoro

    (@ricardomoro)


    Hello.

    Sorry if this problem was already reported.

    The plugin entered on a kind of UPDATE loop on the database, spamming dozens of UPDATE queries on each page access. The query was targeting the nestedpages_menu option, this occurs even with the option to completly disable menu sync is on.
    Below is a example sent by my sysadmin.

    UPDATE portal_options SET option_value = ‘O:8:\\”WP_Error\\”:2:{s:6:\\”errors\\”;a:1:{s:11:\\”menu_exists\\”;a:1:{i:0;s:92:\\”The menu name Nested Pages 1 conflicts with another menu name. Try another one.\\”;}}s:10:\\”error_data\\”;a:0:{}}’ WHERE option_name = ‘nestedpages_menu’

    I think this is caused by an exception not catched by the plugin and sent directly to the DB. When it needs to be read, the query return this exception instead of a valid value, and the erroneous loop begins.

    I will try to search through the code to find the error. If I find it, I can send a pull request.

    Thanks for any help. This plugin is very useful and I am looking forward to use it again.

    • This topic was modified 6 years ago by ricardomoro. Reason: Add a complete query for example
    • This topic was modified 6 years ago by ricardomoro.
Viewing 1 replies (of 1 total)
  • Thread Starter ricardomoro

    (@ricardomoro)

    Hi.

    I can’t find what is causing this loop. Even raising the rand() threshhold didn’t made any difference.

    Is there a way of completly disable the menu sync? I mean, through code?
    If anyone can guide me, I may end up creating a fork without the menu sync, with only the “pages” fucnionality.

Viewing 1 replies (of 1 total)

The topic ‘DB UPDATE loop’ is closed to new replies.