Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.That's affecting version 1.0 and 1.1. Although I only really tested version 1.0, but I'm pretty sure 1.1 has the same problem, as the significant line of code is the same in both versions.
Basically we had a problem with the combination of Advanced aggregation and Advanced form. For some reason the advanced form CSS gets completely dropped by Advanced aggregation as soon as CSS aggregation is enabled. I only managed to prevent that from happening by implementing hook_css_alter and setting the preprocess attribute for the advanced form CSS file manually to FALSE.
That way it won't be picked up by Advanced aggregation and the Advanced form button will show as expected.
As the CSS is meant to be rendered freashly on each form request I would recommed to set this value already in the module, see the attached patch file.
| Comment | File | Size | Author |
|---|---|---|---|
| disable_prepocessing_of_dynamic_css.patch | 935 bytes | stefan lehmann |
Comments
Comment #2
stefan lehmannComment #4
dman commentedSeems sane and safe. I have no end of troubles with advagg.
Patch did not apply - was built from drupal root, not project root ;-)
Re-applied manually, adjusted for Drupal patch conventions, and committed.
Thanks & Cheers.