Thread

After I updated to EE 1.6.9, build: 20100430, my style sheets no longer update.

Here’s the setup:

- The style sheet is an EE ‘CSS Stylesheet’ template type.
- The style sheet is named ‘styles/global.css’ (‘styles’ is the template group, ‘global.css’ is the template name).
- The template is saved as a file.

It is being called like this:

<style type="text/css" media="all"><!-- @import url("/styles/global.css"); --></style>

When I edit the file (not through EE but externally), and save, this is the behaviour:

Prior to updating EE:
The file would save and the changes would be reflected when I reloaded the browser.

After updating EE:
The file saves, I can see the saved changes if I look at the template in EE, but the old version is sent to the browser UNTIL I update the template through EE (i.e. navigate to the template in the CP and click the ‘update’ button).

Other templates saved as files (non stylesheet ones) DO update.
It’s not a browser caching issue.

To my knowledge I haven’t changed anything about the setup or execution except for updating EE.

Is there anything about the latest EE point release that would cause this? Or another explanation?

Thanks

Adam,

Sounds odd especially since other template types update.
Can you quickly clear your cache manually by deleting all the folders in system/cache/ bar the index.html file.

Change the the template type to weblog. Update the saved file and save does it work? Switch back to CSS type again and test again.

I’m seeing this exact issue in MSM in EE 2.2.0 Build 20110622. My style sheets are held outside EE, but the templates themselves will not be reflected in the rendered page until I synchronize the templates in the EE CP. Frustrating.

Hi, highlands.

Are you caching your templates? Have you tried with a different browser? What about manually removing your cache folders? Does that help?

Thanks, Sue! It does not appear to be related to caching, however, I had been needing to tweak the config to get the templates to save as files and had removed this in a troubleshooting effort and forgot to restore it. Once I added back all references to the template path in each config and index file, everything worked as it should.

Glad you were able to figure out what the problem was. Don’t hesitate to post again as needed.