Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The Nov 24th and 25th releases seem to crash the whole front end - I'm getting tags with region classes echoed to the screen, including in the block-display page. Restoring to previous version brings the site back. Clearing cache doesn't help. It could be something I did, but I wanted to get this report out there. I'm using Drupal 8.0.0.
Output now looks like this:
< class="l-r region pr-leaderboard__leaderboard">
User menu
My account
Log out
< class="l-r region pr-header__header-first">
Comment | File | Size | Author |
---|
Comments
Comment #2
Todd Young CreditAttribution: Todd Young commentedI don't know if this was happening before, but I am now getting the following 404 errors:
Comment #3
Jeff Burnz CreditAttribution: Jeff Burnz commentedIs this online?
Strait off I am pretty stumped as to why this would happen, the output is wrong because there is no region or block markup, and as to why this escaping output to screen is very odd.
I need you to do a few things:
1) zip your version of AT Core AND your sub theme and attach them here.
2) zip sites/default/files/php/twig and attach it here.
The map 404 errors you can ignore, I will fix this shortly, basically in the past I was removing the .map files from generated themes but not deleting the references in CSS files (hence Chrome etc will record a 404 as it tries to load the .map). map files are used when debugging SASS during development.
Comment #4
Todd Young CreditAttribution: Todd Young commentedNot online yet, but here are the zips you requested. At some point, if nobody else reports the same issue, then I must be the edge case. If at any point this isn't helpful to you please feel free to close/more-info the issue. I just wanted to make sure it wasn't a system-wide bug, and thought it was strange that it happened reliably after up/downgrading the theme.
Comment #5
Jeff Burnz CreditAttribution: Jeff Burnz commentedOK, I have figured this out. Basically there were template changes between the time you created your theme and now. Here are the steps to fix your theme:
After all this clear the cache and you should be good to go.
One final thing you could do is add this to your themes info.yml file, anywhere in there will do, this will give nice styles in CK Editor:
Comment #6
Todd Young CreditAttribution: Todd Young commentedWorking! Thanks for the fix. I have new issues with my CSS losing the battle against the color module now, but that's something I can tackle another day.
As always, thanks for the great work!