Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
The engineers are working on this one and have identified the issue. We’re working on a fix. I’ll move this to the bug category.
I’d be interested in learning more about your dev environment setup. Are any of you running watchers, javascript processes, etc. that could be running and actively modifying files during a push? For one user who reached out to WP Engine, simply stopping the npm process that was running allowed the push to succeed. This could be a temporary workaround.
These watchers could cause files consistently being deleted/renamed during the file push, like a webpack watcher, for example. Stopping those processes, or simply adding those files that you don’t want pushed to a .wpe-push-ignore file, should solve the issue.
upgraded to the new Local 7.1.0 release this-morning and this created a bug that prevents wp-engine from being able to locate the file system to push changes.
Reverting back to 7.0.1 Fixed this change.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Was replicated on another machine with multiple projects. Upgrade version from 7.01 to 7.1.0 and try to push or pull to wp-engine. Local will be unable to locate filesystem.
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
My dev environment is just Local + Visual Studio Code (1.8.0.1). I do usually have the whole app\public folder open in VSCode while I push, but I also tested with an entirely new pull and nothing open and got the same error.
Hi @jking! The bug mentioned above should be related to Push - if you’re having issues pulling can you try downloading a backup and direct importing that as a workaround?
To all the previous folk in the thread and any newcomers, as Austin mentioned this is a known bug being worked on. We should have a fix for it out soon, but in the meantime, if you downgrade your Local version to 7.0.1 that should get Local pushes working again for you.
Hey @Nick-B, my comment was in reference to push, pull works perfectly fine for me! What I was trying to say is, push still didn’t work even after deleting the site and trying to push again from a completely new pull with no other programs open. Hope this clarifies things.
We were able to zero in on the issue with pushing to WP Engine. It seems that there was a regression that wasn’t properly handling slightly different file lists between the local site and the remote site. This situation would arise if there were certain operations happening either locally or remotely at the time a push was done. For example, if you were trying to push while a plugin update was happening, or a Webpack process was watching/rebuilding things during a push.
This most recent beta release should have a fix:
We’d like to confirm that this fixes things before deploying the changes to the stable version of Local.
If you are currently on the stable version of Local, you can try this beta version on your site by following these steps:
Export the site from the stable version of Local by right-clicking on the site and selecting “Export”
Download the Beta version of Local and quit the stable version of Local.
Open Local Beta and import site by dragging and dropping the zip export onto Local Beta
Connect to WPE.
Try pushing the site again.
Can you try that workflow and let us know if it allows you to push successfully to WP Engine?
As reported above reverting 7.0.1 solved it