Stage file proxy attempts to fetch aggregated JS/CSS.

Created on 3 July 2023, over 1 year ago
Updated 21 July 2024, 5 months ago

Problem/Motivation

The new asset aggregation suppose new public://styles directory is autogenerated but local version may need to use local assets

Steps to reproduce

The change record https://www.drupal.org/node/2888767 β†’

Proposed resolution

Add setting to proxy new styles directory

Remaining tasks

- patch
-review/commit

User interface changes

API changes

Data model changes

Release notes snippet

Original summary

Recently just updated local and development sites to Drupal 10.1, using Apache and aggregate css and js stopped working.

The Chrome inspector tool is showing 404s for some css and js as they are trying to be pulled from prod domain instead from the local domain.

I tried different settings with Hotlink option enabled or not, adding exception for js and css files.

Disabling the file stage proxy module brings back the aggregation functionality and css and js files are being generated just fine by Drupal.

πŸ› Bug report
Status

Fixed

Version

2.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mihaic

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024