Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter dm

    (@dmackinn)

    In case other people are curious, this is the value I saw in the database table when the high CPU issue was happening, it’s the exception error generated by WP core

    
    O:8:"WP_Error":2:{s:6:"errors";a:1:{s:11:"menu_exists";a:1:{i:0;s:97:"The menu name <strong>Nested Pages</strong> conflicts with another menu name. Please try another.";}}s:10:"error_data";a:0:{}}
    
    Thread Starter dm

    (@dmackinn)

    I deleted the menu item via the WP admin UI but the database entry with the error had to be deleted through the database.

    Thread Starter dm

    (@dmackinn)

    Yes, it’s due to Nested Plugins storing a WP Error exception in the database table.

    WP core is more strict about duplicate menu item names now and throws an error exception. Nested Pages tries to create a menu item but it one exists already an error is thrown in WP 4.9 and above. Since Nested Pages is expecting that database entry to be an id number and not an error message it chokes.

    My solution was to delete the menu items, clear out the bad database value and then reactivate Nested Pages.

Viewing 3 replies - 1 through 3 (of 3 total)