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.

Sign up for GitHub

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

Jump to bottom

Bug: Path Issue on Fresh Repo Clone #111

Open
bd-viget opened this issue Jun 14, 2024 · 0 comments
Open

Bug: Path Issue on Fresh Repo Clone #111

bd-viget opened this issue Jun 14, 2024 · 0 comments
Assignees
@bd-viget

Comments

@bd-viget
Copy link
Contributor

bd-viget commented Jun 14, 2024 •
edited
Loading

Summary

When cloning the repo for the first time and running ddev start, there are a few issues related to directory resolution that need to be resolved.

What We Know

  • Upon completion of all the Composer install scripts, user gets 403 Forbidden
  • Error is also showing: directory index of "/var/www/html/" is forbidden, client: 192.168.247.5
  • The wp core download command isn't completing correctly causing the wp-* files to not be present.
  • Running ddev wp core download post installation still works and resolves the issue.

There was a second error that only showed up on Eric's computer:

  • Viget\ComposerScripts\ProjectEventHandler::postInstall Created TensorFlow Lite XNNPACK delegate for CPU.

Another path-related error that showed up while installing for IAFF that could be related:

  • Invalid working directory specified, /var/www/html/wp-content/themes/iafffoundation/wp-content/mu-plugins/viget-wp does not exist.

Steps to reproduce

  1. On a fresh instance (no existing traces of the wp-starter ddev project), clone this repo.
  2. Run ddev start
@bd-viget bd-viget self-assigned this Jun 14, 2024
@bd-viget bd-viget mentioned this issue Jul 1, 2024
Merged
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Pre-populate Site info for fresh install
aacd15a
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Include ENV reading step
f736664
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Move VigetWP Composer Install to ddev post-start hook
e152824
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Added Composer version to VigetWP MU Plugin Composer File
986c2d4
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Pre-populate Site info for fresh install
6634299
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Include ENV reading step
bd3cc77
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Move VigetWP Composer Install to ddev post-start hook
dccbda5
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Added Composer version to VigetWP MU Plugin Composer File
70530d9
bd-viget added a commit that referenced this issue Jul 1, 2024
@bd-viget
[#111] Installation Fixes (#118)
83153f8 
* [N/A] Fix a small bug in Gravatar fix

* [N/A] Fix issue where WordPress isn't installed on repo clone.

* [#111] Pre-populate Site info for fresh install

* [#111] Include ENV reading step

* [#111] Move VigetWP Composer Install to ddev post-start hook

* [#111] Added Composer version to VigetWP MU Plugin Composer File
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bd-viget bd-viget

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bd-viget