Support » Plugin: Fast Velocity Minify » Settings keep going back to default

  • Resolved aaronjpitts


    I have the latest version of the plugin on the latest version of WordPress. I uncheck ‘Fix Page Editors’ and after a while I see it’s being checked again which is causing my site to not function how I wish (I want it to show the optimised JS/CSS for logged in users). I do not know what is triggering it to go back to default. Do you have any ideas? I’m on the Roots stack if that makes a difference (Trellis, Bedrock and Sage).

    • This topic was modified 1 month ago by  aaronjpitts.
Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.


    When you select the option and then save, is it still saved if you navigate somewhere else and come back to that page?

    Do you have wordfence installed, or some other security plugin?

    If returning to the settings page shows that your settings are still selected, the only think can think of, is that your hosting is resetting the wp_options table for some reason.

    It could be replication on their database servers failing (depends on what they use), or it could be as well, the database being corrupted, which will then rollback that table to a previous state.

    I can suggest, contacting your hosting about that and ask if they are restoring or doing any failover (or whatever that may be causing that).

    If you know what you are doing, then you can try as well export and import again, a mysqldump on your hosting control panel. Usually exporting and re-importing, fixes corrupted databases.

    Another possibility would be, if you have some plugin or code disabling plugins conditionally, and then re-enabling them again. If something triggers the disable / enable plugin routines, the plugin will reset itself (though the fix page editors should be on by default)… for which case, you can select the option to preserve settings.

    Also take a look at any mysql errors (ask your hosting).

    If your hosting uses object storage, sometimes they may keep things on object storage memory rather than the database. It’s unlikely, but a possibility.

    Other than these, I have no idea.
    The logic is simple, save options and it’s either saved or not.
    If it’s saved and it’s still saved once you navigate away and back again, then there is something else going on somewhere else, other than FVM.

    Take a look at the browser console as well, for any possible javascript errors once you submit. Maybe try other device as well.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.