• We are running a fairly large multisite installation that uses Admin Menu Editor Pro. This morning our dev site stopped working and it looks like the reason was that we have over 17,000 entries in our wp_sitemeta table from ws_menu_editor_pro. Our php errors log also showed SQL errors from menu editor pro. Deleting those 17,000 entries brought the dev site back online. Fortunately it doesn’t seem to be an issue in production.

    Has anything like this been raised before? Any ideas what’s the cause of the error? Any planned updates to fix it? Any helpful tips meanwhile?

    Thanks –
    Patrick Noonan

    http://wordpress.org/plugins/admin-menu-editor/

Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    I’ve heard of a similar issue once before, but I have no idea what could cause it aside from some kind of a more general MySQL server problem. Or maybe some arcane race condition that makes WP create new wp_sitemeta entries instead of updating the existing ones… AME doesn’t really do anything special with the database in general or wp_sitemeta in particular. It doesn’t even run any direct SQL queries. It just uses standard WordPress APIs to load/store the menu configuration.

    Some thoughts:

    • You mentioned SQL errors. What were they? How did you determine that they are related to AME Pro?
    • Does the number of ws_menu_editor_pro entries match the number of sites where you activated this plugin? If you activate it individually on each site (as opposed to, say, installing it in mu-plugins), it will create one DB entry per site to store the menu configuration.
    • On a related note, were there multiple entries per site, or perhaps all of the entries were for the same site?

    Side note: This support forum is mostly intended for free plugins. Please use this contact form for Pro-version-related support requests in the future.

Viewing 1 replies (of 1 total)
  • The topic ‘Thousands of repeated metadata entries’ is closed to new replies.