Can no longer pull/push from WP Engine since upgrading to MacOS Ventura on M1 Mac
Since I upgraded my Apple M1 mac to MacOS Ventura I can no longer pull / push environments from WP Engine. I also can not see what files were updated in the preview window. No matter what changes it’s always 0 files.
The following error also occurs when sync is attempted:
Error: Command failed: /Applications/Local.app/Contents/Resources/extraResources/lightning-services/mysql-8.0.16+6/bin/darwin/bin/mysql local -B --disable-column-names -e SELECT option_value FROM wp_options WHERE option_name = ‘siteurl’;
ERROR 1146 (42S02) at line 1: Table ‘local.wp_options’ doesn’t exist
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular? All sites though the error doesn’t always show, nothing syncs
Are you able to create a new, plain WordPress site in Local and access it in a Browser?
Yes I can create new sites, and those work. I can also create a new sync and use other tools to load content but can’t use Local WP
Replication
Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!
System Details
Which version of Local is being used? 6.5.2 but also happens in two previous versions
What Operating System (OS) and OS version is being used?
MacOS Ventura 13.0.1 on Apple M1 Max
Attach the Local Log. See this Help Doc for instructions on how to do so:
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.
If you’re still having trouble can you start here?
After that, if you still have issues please share your Local Log again and we’ll be happy to look further.
Additionally, you can reach out to WPE support directly to get additional assistance in real time. They will be happy to collect logs, create a ticket for you and escalate as needed.
Does downloading a backup, and doing a direct import instead of using the native Local Connect feature function as a workaround? Or does that produce an error as well?
In order to refresh here and start with a clean slate you could you give the below troubleshooting steps a try:
Export any sites that you have on Local and save them to a folder somewhere on your computer.
When the computer is restarted and turned on, close any applications that automatically run in the background (AntiVirus, Firewall, and other Developer applications included).
Check and see if the issue still persists. If so, please provide us with an updated log. Retrieving Local’s Log File
Lastly, apologies for the wait times but the Local Forums aren’t monitored 24/7. If you’re WPE customers you can always reach out to their support directly however which is monitored 24/7 to get some assistance via chat or get a ticket created for further follow-up.
@Nick-B I will have to schedule attempting a full uninstall / reinstall as in active development on many sites and that might take a hwile. As for “downloading a backup” and doing a direct import, I haven’t tested that yet but will try to.
I can say that we are able to create blank sites fine, sync with Flywheel fine, and import using WP Migrate DB fine. The only functionality that doesn’t work is when syncing with WP Engine.
@Nick-B did a full reinstall following the steps and the same issue persists. The very first site I tried to pull down pulls down completely empty and broken. Logs attached.
@Nick-B that’s exactly what I did when I reinstalled it. I’ll do it again but I’ve deleted the credentials from WP engine multiple times and resynced them. The error is the same.
As for the “download and direct import” do you mean from a WP Engine backup? what’s the process for that?
Okay thanks for giving those steps a try and confirming! The download and import method would be downloading a backup and then just dragging and dropping that zip file into Local. You can read more about this here: Import a WordPress Site into Local - Local
As another test, I’d be curious if you have access to another machine you could download Local on, set up credentials and see if you’re able to pull there.
To clarify have you tried pulling multiple sites from WPE or is this always the same site? Curious if it’s happening across the board or just in one spot.
@Nick-B I’ll test the export/import now. And yes I’ve tried multiple sites, the site creates but it’s empty and doesn’t work. I can sync with Flywheel (that works fine).
I can create blank sites with no issues and then install WP Migrate and import sites that way.
Testing right now I’m downloading a backup from WP Engine and will update shortly if it works for importing into local.
I have a PC I can test imports on but I’m pretty sure this is only affecting those of us on Apple silicone on Ventura. It worked flawlessly before upgrading to the new OS. Will update once I’ve tested both export and another machine.
Hi @mdavoli Glad to hear it! Do you know if any of these sites are on the larger side? Around or over 5 GB in total size? Or do any of them have databases that are large or have tables/rows that could be bloated? Sometimes with things like those Local Connect can be fairly spotty so the direct import method is the recommended workaround.
@Nick-B some are large some are small and completely empty. Doesn’t matter for the magic sync as the database / files never download. I’ve used local for years now never had this issue before until Ventura.
No syncing at all works and the site won’t even load if you “Create” it by importing rom WP engine through local connect. Have to delete the site and recreate it manually and or via the direct import method from exporting from backup.
Obviously that’s doable but something more serious is preventing the syncing
@mdavoli Thank you for all of your testing! I’ve raised this up to the Dev team so we’ll be taking a deeper look and seeing what else we can uncover here. We’ll let you know if we need any other details or further logs, etc. Thank you again for your patience!
