Hot answers tagged plugin-development
Did you try just using option.php? <form method="post" action="options.php">
From what you are saying you have translated your plugin and now you want to be sure the future update won' be overwritten. So to avoid that happening you can always put your po/mo translation files (if provided) in global languages folder that is located on your server in wp-content/languages/plugins folder. If plugin have language file name for example ...
In the context of official plugin repository this is very explicitly forbidden by the guidelines (emphasis mine): 7. No "phoning home" without user's informed consent. This seemingly simple rule actually covers several different aspects: No unauthorized collection of user data. For example, sending the admin's email address back to your own ...
This is probably the root cause - https://core.trac.wordpress.org/changeset/36510. Core have moved from saving menus in $_POST to sending them as json encoded and then decode it into $_POST. I am not very familiar with how menus are sent to the server, but you probably either use the wrong hook, use the right hook but too early, or there is a bug in core.
Only top voted, non community-wiki answers of a minimum length are eligible