Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blockset command requires file permissions reset in WPEngine shared hosting each time #1942

Open
1 task done
seanryy opened this issue Aug 21, 2024 · 1 comment
Open
1 task done
Labels
needs: reproduction This issue needs to be reproduced independently

Comments

@seanryy
Copy link

seanryy commented Aug 21, 2024

Description

Hey team!

We're using WPEngine Atlas with a standard WPEngine backend WP server.

Whenever we run the 'blockset' CLI to deploy the blocks to the connected WordPress site it requires the file permissions to be reset in the Utilities > Reset file permissions for any of them to be visible. I've been putting up with this for a while and manually resetting the file perms, but I'd really love to figure out how to fix it so that we can automate the deployment.

Thank you,

Sean

Steps to reproduce

  1. Clone getting-started project
  2. Run blockset CLI command
  3. Navigate to connected WPEngine backend project, open Gutenberg
  4. Blocks are missing
  5. WPEngine -> Utilities -> Reset file permissions
  6. Blocks are visible once again?

(This happens every time the blockset is run)

Additional context

Using @faustwp/cli version 3.0.2.

System: Macbook Pro M2, macOS Sonoma 14.6

  • This is work provided, so perhaps the security settings may be causing the files to be submitted with different permissions than usual?

@faustwp/core Version

3.0.3

@faustwp/cli Version

3.0.2

FaustWP Plugin Version

1.3.2

WordPress Version

6.5.5

Additional environment details

Host: WPEngine - shared hosting + WPEngine Atlas frontend

Please confirm that you have searched existing issues in the repo.

  • Yes
@josephfusco josephfusco added the needs: reproduction This issue needs to be reproduced independently label Aug 22, 2024
@josephfusco
Copy link
Member

Hey @seanryy thanks for creating this issue! We'll update here once we are able to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: reproduction This issue needs to be reproduced independently
Projects
None yet
Development

No branches or pull requests

2 participants