• We are running our wordpress site on development and staging servers.

    Every time I run a deploy to move any development work onto the staging server, one of the last tasks it runs is a database upgrade with
    “wp core update-db –network”

    This has the effect of removing the Megamenu Css record (stored in wp_options with an option_name of “_transient_megamenu_css” and rewriting it.

    Unfortunately this has the side effect of removing any text widgets that I have entered on the Mega Menu.

    How can I stop this happening, apart from skipping the db upgrade please?
    Also, why does MegaMenu use transient records for storage?

    Any help/advice gratefully received.

    Delyth

Viewing 1 replies (of 1 total)
  • Plugin Author megamenu

    (@megamenu)

    Hi Delyth,

    Thanks for getting in touch.

    The _transient_megamenu_css stores a copy of the generated CSS. It’s not necessarily permanent – you can delete it without affecting the behaviour of the plugin.

    I do not understand why updating the DB will remove the widgets, if the same process is run through the normal update process (through your browser), the widgets will not be moved, so I think something else must be going on. The css is also not connected in any way to the widgets so I think that’s a red herring.

    I do know that WordPress will move all widgets from their selected sidebars to the “Inactive Widgets” sidebar every time you switch theme. Please can you investigate further and make sure the update process you’re running isn’t switching the selected theme (and back) for some reason?

    Regards,
    Tom

Viewing 1 replies (of 1 total)

The topic ‘Database upgrade removes widgets from menu’ is closed to new replies.