- Issue created by @pratishjha
- Status changed to Postponed: needs info
10 months ago 4:23pm 18 February 2024 - 🇬🇧United Kingdom longwave UK
There is not really enough information to help you here. You say the bug is reproducible when aggregation is disabled which is interesting and suggests that perhaps there is a problem in your JS or CSS that is being accidentally solved when aggregation is enabled again.
You need to try and identify what is different about the sections that are not working. Also are there any errors in the Drupal logs or the JavaScript console?
- 🇮🇳India pratishjha
Thank you for your reply. There is no error in db log and JavaScript console. The interesting part the issue does not occur when I am logged in to the site with any role. It is only happening for anonymous users.
For reproducing it locally by xampp I can only see it by disabling aggregation whereas on ngnix server the issue persists either disable or enable.
Also if I remove the whole custom CSS & JS still some footer parts are still not showing on the browser. For different languages, it shows differently. I have not seen this kind of strange behavior in the entire Drupal experience from 7 to 10. - 🇮🇳India pratishjha
Yes, big pipe is enabled currently. Un-installing big pipe does not resolve the issue.
- 🇧🇪Belgium gorkagr
If it is missing to anonymous only it could be some missing permissions (either general ones or maybe inside group if the module is being used)
Can you confirm you updated the nginx configuration for Drupal 10.1 → ? This is mentioned in release notes.