Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Matthew Reilly

    (@creativemashwp)

    Hi Nathan,

    Thanks so much for the detailed feature request, it was spot on.

    I’m happy to let you know that version 1.3.0 now includes full support for custom post_meta on menu items. This works exactly as you described. Any third-party plugin data stored in post_meta on nav_menu_item posts is now automatically captured during backup and included in exports.

    This means If Menu visibility rules, icon assignments, and any other plugin that follows the WordPress pattern of storing data in post_meta will be preserved through backup, restore, import, and export. No configuration needed, it just works.

    We’ve tested this with If Menu, Menu Icons by ThemeIsle, WP Menu Icons, Menu Image, and Easy Menu Icons, and it should work out of the box with any plugin that uses post_meta on menu items.

    Along with this, 1.3.0 also includes a few other improvements:

    • In-place restore (replaces the existing menu directly instead of creating a duplicate)
    • Multi-menu export/import (select multiple menus and export them in a single file)
    • Bulk backup actions (select and export or delete multiple backups at once)
    • Inline backup rename

    Thanks again for taking the time to write up the request. Your suggestion made the plugin significantly more useful for everyone.

    Best,
    Matthew

    Plugin Author Matthew Reilly

    (@creativemashwp)

    Hi Nathan,

    Thanks a lot for the detailed message and for taking the time to explain your setup so clearly, it really helps 😉

    This is a great suggestion. It’s not something we had fully considered before, but the way you’ve outlined it makes a lot of sense, especially around supporting additional post_meta for menu items.

    We’re going to look into this now and figure out the best way to handle it. From an initial look, it seems very doable. The idea of including post_meta in the JSON and then restoring it where available is exactly the direction we’d explore. As you mentioned, the logic would need to be careful not to create empty placeholders when data isn’t present.

    We’ll also review whether this should be on by default or behind an option like “Export all menu item data”, but either way it feels like a solid addition.

    I’ll let you know once we’ve made progress or have something ready to test.

    Thanks again, really appreciate the suggestion.

    Matthew

    Plugin Author Matthew Reilly

    (@creativemashwp)

    Hi ez2498

    I’ve found the source of the issue and have now fixed it. I’ve tested it on my side with WordPress 6.8.1 and PHP 8.1.33, and those deprecation warnings no longer appear.

    It was only visible because debug mode was turned on, but it was still worth resolving so no one else runs into the same thing.

    Thanks again for taking the time to report it. Let me know if you spot anything else.
    Matthew

    Plugin Author Matthew Reilly

    (@creativemashwp)

    Hi there

    Thanks for the message and for using the plugin. Glad to hear you find it useful.

    Those notices are PHP 8.1 deprecation warnings. They happen when something passes a null value into strpos or str_replace, and WordPress then throws the warning from wp-includes/functions.php.

    I’ll set up a test install with WordPress 6.8.1 and PHP 8.1.33 and try to reproduce this with the plugin active so I can track down where the null value is coming from and fix it.

    It is also likely you are seeing this because debug mode is turned on. When debug is on, WordPress will show every notice on screen. Turning debug off would hide these messages, though I know that is not ideal. I still want the plugin to work at its best, so I will look into this properly.

    Can you confirm two quick things
    • the notices disappear when the plugin is deactivated
    • the warnigns reappear when you reactivate it with everything else unchanged

    These are only deprecation notices so nothing will break, but they shouldn’t appear and I’ll sort it.

    Thanks again for flagging it.

    Plugin Author Matthew Reilly

    (@creativemashwp)

    Thanks so much for the kind words and for sharing your thoughts. I totally get what you’re saying about the list taking up space and the Save/Delete buttons sitting at the bottom. The idea behind keeping backups open by default was just to make sure new users see what’s there straight away.

    That said, your point makes a lot of sense. I’m thinking of adding a toggle in a future update so the list is open the first time, but you can fold it away if you prefer. Once it’s hidden, it would stay that way for everyone until it’s switched back on again.

    Really appreciate the suggestion, it’s great to hear how people are using the plugin in real life.

    Plugin Author Matthew Reilly

    (@creativemashwp)

    Hi there, and thanks for the kind words.

    At the moment the plugin only supports WordPress core menus saved via Appearance > Menus. Third party menu managers like Menu Manager Ultra use their own save process, which bypasses the hooks my plugin relies on.

    This might be something I look at in the future if there is enough demand, but it is not supported right now.

    Best wishes,
    Matthew

    Matthew Reilly

    (@creativemashwp)

    I’ve done the same thing before and know how frustrating it is. Sadly, once a menu is deleted there’s no built-in way to get it back unless you have a site backup. I created a free plugin called Menu Backup & Restore that can’t recover your menu this time, but it will protect you in the future by automatically saving a backup every time you save or update it, so you can restore it with one click:
    https://ww.wp.xz.cn/plugins/menu-backup-restore/

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