The CSS path indicated for the HTML in the editor window is attached by javascript. Javascript caches all URLs/Pathes so this CSS is also violently cached by the browser, which created very significant problems for themers - once they indicate custom CSS file, and start editing it, all edits after the first one are ignored, until you clear browser cache or restart browser. It almost makes the feature unusable.
Attached patch adds ?nocache=[timestamp] at the end of the CSS file path to avoid caching (it's obviously not a performance issue since content edit screen is not a performance-sensitive page, anyway).
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | ckeditor.module-772134.patch | 819 bytes | irakli |
Comments
Comment #1
irakli commentedComment #2
irakli commentedComment #3
mephir commentedi'll review that asap and commit changes. Thanks for help.
Comment #4
jcisio commentedI don't think it is not a performance issue. Every node view page normally has a comment form, and CKEditor of course can be use for comment.
The number of CSS can be large, especially when theme breaks stylesheet into a couple files for logic seperation.
Versionning is ok, but not timestamp, please.
Comment #5
mephir commentedMy propose is that, if choose ckeditor_source.js load method, 5this time stamp will be added automatically.
Comment #6
mephir commentedChanges commited into CVS.