I am running a WP site on WPEngine. It includes both a staging and production server. We use a plugin called Admin Custom Login.

After setting up the plugin on staging, I push the code-only (not the database) from Staging to Production. The plugin appears on Production, but the settings are all missing. I manually added the settings on Production and everyone is happy.

But then, when I roll back the database (not the code) from Production to Staging. ACL on Staging loses it's settings. I manually re-enter them and everything is working again.

But the next time code (not the database) is pushed from Staging to Production, production again lost its settings. Next time I roll back the data, Staging loses its settings.

Any ideas? How can I stop having to re-enter the settings for this plugin everytime something changes?

I tried to contact the plugin maker, but (1) They do not maintain a Github issues page, (2) Their Tak issues page has over 1000 active entries dating back to 2005, and (3) Their company support forum only provides support for paid plugins. Seems like a bad vendor to me.

1 Answer 1


Most plugins store their settings in the database. So whenever you push code from one site to another, you need to at least push the plugin-specific data along with your files.

You could hire a developer to determine where the plugin is storing data, or if you're comfortable using phpMyAdmin, you can use that and also browse through the plugin files themselves. Some plugins create their own custom tables, in which case, you can probably copy just that table from staging to prod and vice versa. But keep in mind there may be relative data, such as user IDs, that will also have to be identical between the two databases in order for things not to break.

Another option would be to copy your Production site to Staging each time you want to make changes in the plugin. Have a freeze on Production (there are plugins available to accomplish this, or you can temporarily demote all of your users to Subscribers so they have no power to make changes) so that while you're working, no one can make changes to either the files or the database. Test things out on Staging, make sure all looks good, and you can then push from Staging to Prod and then unlock the freeze (either disable the site-freeze plugin or promote your users back to their normal roles).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.