Could you provide an updated Local Log for us as well? There are some different ways to access and share Local Logs. For us to be able to troubleshoot thoroughly, please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering.
Also, what Windows version are you on? 10 or 11 for example or something else?
Could you also do the following?
Open Site Shell and using this command, cd app/public/wp-content && ls -al check the local permissions of the mu-plugins directory.
If you can do the same via SSH for the remote WPE site as well, that could help!
Win 10 Pro - I think I might have figured it out. You were on the right track, the local permission for this specific site got messed up. I used this to reset to default and things are working now for the site in question ( cloning…etc. ). Just confirming when the permissions got corrupted.
icacls “full path to the folder” /reset /t /c /l
I did this a the for the entire \app\public folder and subfolders.
With the site working with Flywheel Push/Pull/Clone I connected it to a default site on WP Engine and did a push. This worked as expect. Then when I did the pull I get PHP warning related the mu-plugins folder which get added by WP Engine. The permissions on the folder are such that I cannot access. These are just PHP Warning errors so the list still loads and this is much better then before when my theme was blocked from loading due to permissions. As an admin I was able to delete the mu-plugin folder and the error/warning is gone.
Locally permissions for the mu-plugin folder:
drwxr-xr-x 1 mu-plugins/
-rw-r–r-- 1 advanced-cache.php
Looks like the folders inside the mu-plugin folder are 555 and files are 444
WP Engine - from tech support I got this:
drwxrwxr-x 6 www-data 4.0K mu-plugins
File Permissions for what is inside the mu-folder is:
drwxrwxr-x 6 www-data 4.0K Aug 11 18:07 .
drwxrwxr-x 7 www-data 4.0K Aug 11 18:28 …
dr-xr-xr-x 3 nobody 4.0K Aug 8 20:44 force-strong-passwords
-r–r–r-- 1 nobody 8.1K Aug 8 17:53 mu-plugin.php
-r–r–r-- 1 nobody 565 Aug 8 17:53 slt-force-strong-passwords.php
dr-xr-xr-x 6 nobody 4.0K Aug 8 20:44 wpe-cache-plugin
-r–r–r-- 1 nobody 1.3K Aug 8 17:53 wpe-cache-plugin.php
dr-xr-xr-x 3 nobody 4.0K Oct 14 2019 wpe-wp-sign-on-plugin
-r–r–r-- 1 nobody 17K Aug 8 17:53 wpe-wp-sign-on-plugin.php
dr-xr-xr-x 7 nobody 4.0K Aug 8 20:44 wpengine-common
-r–r–r-- 1 nobody 15K Aug 8 17:53 wpengine-security-auditor.php
I guess WP Engine specific plugins and files should get excluded on a pull?
Thank you for all of the testing and details @codeshed! I’m sharing all this information with the Dev Team so we can look into what might be going on.
FYI - This is still happening. Just did a fresh install on local, pulled from WP Engine and the permission are now messed up on my local site and various errors related to WP Engine plugins and files are generated.
Sorry I asked previously but I think it got lost in the shuffle. Can you share an updated Local Log as well? I’ll run that back to the Devs for a deeper look.
Please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering.
Hi @codeshed! Thank you for your patience. Our dev team has reviewed your Logs but nothing is really standing out unfortunately to help pinpoint the issue. Seemingly it looks like a normal pull to Windows without obvious errors.
The most recent pull in the logs suggests that no files from mu-plugins were pulled. As a test could you try to pull to a fresh site in Local and actually verify that no WPE-specific mu-plugins are being pulled? We can confirm from our end they shouldn’t be.
If it helps, feel free to make a screen recording using something like Loom or similar to showcase any errors or where things are going wrong. If you’d prefer not to share that in the thread you can send it direct to me as well.
I will do and report back, but that is the route of the issue… the mu plugins and permissions.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.