Ticket #19634 (confirmed Bug)
Css registry broken after saving with session expired
Reported by: | bglatt00 | Owned by: | bglatt00 |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Templates/CSS | Version: | 4.3 |
Keywords: | cssregistry | Cc: |
Description
It happend twice to me to finish with an empty css registry, by saving my settings in zmi, while my session has already been expired. This is what I've done:
Making css modifications, I put my site into development mode under portal_css. When everything works, I make a final test as anonymous user, therefore logging me out. Finally I want to disable development mode again. I've kept the zmi page in a separate tab, and after clicking the Save button, the login window appears, since I have already logged out. Inserting my login data, I end up with a blank css registry without entries and a broken plone site without css.
I don't know if this can be considered a bug, maybe it doesn't reflect a "normal" user behaviour, but it's rather annoying and shocking at the first moment. Using the "undo" tab in zmi I was able to restore everything again.
The exact Plone version is 4.3.3
Change History
comment:1 Changed 18 months ago by cwainwright
- Owner set to bglatt00
- Component changed from Unknown to Templates/CSS
comment:2 Changed 18 months ago by cwainwright
- Status changed from new to closed
- Resolution set to invalid
Clearing out spam as a batch. Let me know if a real ticket got mixed in.
comment:3 Changed 18 months ago by cwainwright
- Status changed from closed to reopened
- Resolution invalid deleted
oops, closed this one. Moving it to confirmed just so I don't do that again
comment:5 Changed 18 months ago by bglatt00
I've tried quickly to redo the steps I have described, but the problem didn't reappear neither with Firefox nor Chrome, usually I've used only Firefox. There must have been some intermediate steps I don't remember, anyway the result was the broken registry.
Maybe I come back here if it happens again, with more detailed information.
I am unable to reproduce this right now, but I have seen something similar happen in Firefox in the past, along with some other weirdness in the CSS and JS registries. I was able to fix the problem by completely uninstalling Firefox and starting with a fresh install.
Are you only seeing this behavior in one browser, or several?