Thank you for the report. Despite the results of your experiments, it seems unlikely that Jetpack could be the source of the problem. Jetpack is one of the most popular plugins in the world, and if it had such a noticeable conflict with AME, I would expect to see many more reports about that.
There are a few known ways menu settings can be lost:
- Migrating the WordPress database using a tool or plugin that incorrectly modifies serialized PHP data or JSON data.
- Doing a global search & replace on the WordPress database.
- Database corruption.
- (Multisite only) Duplicate
ws_menu_editor entries in the wp_sitemeta table caused by DB issues or race conditions.
Could any of the above apply to your site? Based on the predictable-but-not-immediate nature of the problem, I would guess it might be related to some periodic task like backups, migration, etc.
I think the problem has something to do with the way that Jetpack forces itself to near the top of the admin menu. Is there any way to keep Jetpack in its literal place?
That’s probably a separate issue. Does it show up near the top even if you move it to the bottom with AME? (Before the settings get reset, of course.)
Sorry — you’re absolutely right! I can’t explain why experiments seemed to pin the blame on Jetpack, but long after I deleted it the problem recurred — with W3 Total Cache as the real culprit! And this conflict has been documented before. With W3 Total Cache gone and Jetpack restored, the problem hasn’t resurfaced.
Thank you for your help, Janis, and sorry for the false allegation, Jetpack!
Just to let you know: The very same happened to me some minutes ago and I have no idea why.
