When pulling from or pushing to a remote WP Engine environment the application previously remembered whether you were connected to production/staging/dev. Now it always defaults back to production each time you open the application. This could easily result in accidentally overwriting work/pushing dev work to a live site.
Open the pull or push menu when connected to a WP Engine site
OS X 12.7.4
Local Version 9.0.5+6706
Agreed on this. The application should remember which environment you last pushed/pulled to/from so as to avoid having “in-progress” dev work accidentally being pushed to Production.
Whenever I close the application and re-open it later on, my local sites always default back to Production for the destination environment, even though my last push was to a Development environment.
Local should remember which environment the last action was associated with.
This would easily avoid any accidental overrides of Production sites while there is Dev work in progress that’s not ready to be live yet…
I feel like it used to remember it, but that does not appear to be the case anymore.
Thank you for your comments @shaunmilo! I’ve merged your other post here to keep everything together and changed this topic to a Feature Request. I’ve passed this along to the Dev team as well to inform them of the continued interest.
If you start a push set to Staging and pick “Select Files,” but then cancel the sync, while it will remember the site you’ve chosen, it switches itself back to Production.
Start a push.
Pick a site.
Pick Staging.
Choose “Select Files”
When the file list comes up, click the X to cancel.
The site will not be reset, but the other drop down will now have changed from Staging to Production.
Describe your environment.
I have a screen recording of it in action with it slowed down so you can see it actually snap back to production.
Hi @CTomele! I’ve merged your post into this related Feature Request. This one isn’t technically a bug, but we can definitely understand the dangers here. We’ll discuss this more internally, but for now merging this to keep all related conversation in one place.