You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When deploying a code artifact on Acquia Cloud Site Factory, the following issues occur:
JS and CSS files are not generated, leading to 404 errors on all pages.
Pages such as /user and /user/login returns 404 (Page Not Found).
The plugin is overriding/removing the drupal-scaffold settings in composer.json, instead of only making necessary changes.
Root Cause
The issue arises because the .htaccess file under the project docroot directory is not being pushed when deploying the code artifact.
Without .htaccess, requests for static assets (JS, CSS, images) do not get routed correctly to index.php, causing 404 errors.
To Reproduce
Run the following commands to reproduce:
// Create a fresh new Drupal project.
$ composer create-project acquia/drupal-recommended-project acsf && cd acsf
// Download acquia/drs-acsf plugin.
$ composer require acquia/drs-acsf
// Run all commands as recommended by acquia/drs-acsf plugin.
$ ./vendor/bin/drush drs:acsf:init:all
$ ./vendor/bin/drush drs:acsf:init:drush
$ ./vendor/bin/drush validate:acsf
// Commit all changes.
$ git add . && git commit -m "The initial source code committed."
// Use acli to push code artifact to Site Factory.
$ acli push:artifact
// Install site on Site Factory and navigate to home page and you should see js/css broken.
Expected behavior
Site pages should load without 404 errors.
The text was updated successfully, but these errors were encountered:
Describe the bug
When deploying a code artifact on Acquia Cloud Site Factory, the following issues occur:
drupal-scaffold
settings in composer.json, instead of only making necessary changes.Root Cause
The issue arises because the
.htaccess
file under the project docroot directory is not being pushed when deploying the code artifact.Without
.htaccess
, requests for static assets (JS, CSS, images) do not get routed correctly toindex.php
, causing 404 errors.To Reproduce
Run the following commands to reproduce:
Expected behavior
Site pages should load without 404 errors.
The text was updated successfully, but these errors were encountered: