Disabling/re-enabling plugin required after making changes

  • Resolved elaborate

    (@azinfiro)


    6 months, 1 week ago

    It looks like the plugin fails to affect changes made in the classic menu editor after the plugin has been up and running for a while. Disabling and re-enabling the plugin fixes the problem, letting you make changes which are visible instantly afterwards again.

    I’ve had the plugin enabled on both a dev and a production site which have been running uninterrupted for a couple of months. Neither one has been updated or seen any backend activity for the entire duration. I’ve recently had to add a menu item to a menu managed by the classic menu editor, but the changes failed to propagate to the Navigation block. The sites use a caching plugin (LiteSpeed Cache), but busting the cache didn’t fix the issue. I’ve also ensured the “block menu cache” option in the appearance>customize>menus>classic menu in Navigation block is enabled, which didn’t make any difference.

    Only after I went into the block editor and selected a different value for the “menu location” option inside the “classic menu” panel, saving, and switching it back did the site show the updated menu contents. On the production site, I tried to just disable and re-enable the plugin instead, which also fixed the issue, letting me make changes in the classic menu editor directly again.

    I’m using the plugin to let a client edit menus without access to the block editor. The client also doesn’t have access to manage plugins, so it’s important that I find a workaround.

    I’ll keep on an eye on whether the problem occurs again.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter elaborate

    (@azinfiro)

    6 months, 1 week ago

    I just encountered the issue again. It looks like the culprit is not whether the plugin has been running for a while, but instead an incompatibility with LiteSpeed Cache, which isn’t correctly busting its cache. Disabling LiteSpeed fixes the issue. I’ve updated LiteSpeed Cache to version 7.5.0.1, but the issue still occurs.

    I’ll file a bug report with LiteSpeed Cache as well, but I would appreciate if you could share your thoughts on what might be source of the incompatibility. I’ve tried toggling the “block menu cache” option before and after disabling and updating Litespeed Chace, but it doesn’t have any effect.

    Thanks again.

    Plugin Author WebMan Design | Oliver Juhas

    (@webmandesign)

    6 months, 1 week ago

    Hi @azinfiro,

    Thank you for providing thorough description of the issue.

    Indeed, I don’t experience the issue on my test server or in WordPress playground (you can try testing with WP playground by clicking the link).

    Unfortunately, as I don’t know the LiteSpeed Cache plugin and its code, I can’t really provide any specific debug info here.

    If I should guess, I’d say it may be related to HTML output cache as I presume each page is cached by the plugin (although, flushing the cache should definitely help). Or the plugin might cache Site Editor templates and template parts? Or it caches directly the output of the Navigation block?

    Please try to ask the plugin’s support if there is a way to remove Navigation block (or theme’s header template part) from caching somehow.

    If needed, you can provide them with link to my plugin code at https://github.com/webmandesign/classic-menu-in-navigation-block and the actual Navigation block render modifications are in includes/Block.php file.

    Please note that I’m closing this support ticket as the issue is caused by 3rd party caching.

    Best regards,

    Oliver

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

The topic ‘Disabling/re-enabling plugin required after making changes’ is closed to new replies.