#1447 - yoursite.com/themes/YourTemplates/templates_cached/EN/global.css dated 12/31/1969
| Identifier | #1447 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | yoursite.com/themes/YourTemplates/templates_cached/EN/global.css dated 12/31/1969 |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | core_configuration |
| Description | Seems after doing a cache clear and rebuild the "global.css" is made with a date of 12/31/1969 and the file is locked in the folder.
Why is the date not current? |
| Steps to reproduce | Tried to change or comment out a line of code in global.css and save it then rebuild the cache. Site reverts to an hang state because the global.css file is to old for windows to recognize.... |
| Additional information | Chris we had an issue with the setup wizard I traced it to this issue as well. My host says the file is to old to be recognized and locks it up. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
(Click to enlarge)
Is it possible I can get access to your hosting account to check this? It's a very odd problem, possibly a bug in PHP.
This issue is private, but other non-ocProducts developers can see it. You can post private and encrypted access details in a support ticket:
https://compo.sr/site/tickets/ticket.htm?ticket_template=bug&cost=free
Mr Rat
The 1969 is a timestamp of zero, it's when computer time (counted in seconds) starts.
Composr sets it if there was an error generating the CSS, as a trick to basically disable the cache until the error is fixed. I doubt it is the cause of the problem, but rather a symptom.
I think I definitely need to run a lot of tests on your server.
[email protected]
Also the underlying condition, which sets the date back, only happens on a failed disk write, which isn't a normal condition. I'm getting a fair few errors on the hosting (freezes etc even in the control panel), so I don't have a lot of faith in the host's stability at the moment.
I also manually knocked global.css back to 1969 and I could delete, so I'm pretty sure it is a red-herring.
I will look into your Setup Wizard problems next (in your forum topic).