Changes between Initial Version and Version 1 of Ticket #10685, comment 22
- Timestamp:
- Jul 7, 2015, 12:25:31 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10685, comment 22
initial v1 11 11 A specific example would be the smileys. A huge headache that I ran into was that I was ending up with a huge bunch of broken <img tags for smileys when upgrading from one ckeditor version to another and using the folder version approach. (300,000+ users... major pain) The reason, of course, was that the smileys are essentially content that is bundled with the editor builds, and they are inserted into the content via <img tags that reference their file folders in the current editor folder structure, *unless you specifically tell the editor to look in another folder location in the config*. It took me a while to sort out isolating the smileys folder separate from the cke folder structure and setting the smiley folder location in the editor config. 12 12 13 Therefore, the folder version approach can cause problems for anything that the editor *inserts into the content* via a link or image tag that references bundled content in the current folder structure. Since I do not know what types of content (beyond smileys) you may bundle with the editor in the future, ''I specifically choose not to use the folder version approach, and I am also very much in favor of using a version/timestamp query parameter instead.'' What I would prefer is that you include it as an version/timestamp value as "buried" config setting that I can override via a config setting I specify--that will help with special cases where I may need to force a resource reload for my users. (A specific example is forcing a reload for mono vs color toolbar icons.)13 Therefore, the folder version approach can cause problems for anything that the editor *inserts into the content* via a link or image tag that references bundled content in the current folder structure. Since I do not know what types of content (beyond smileys) you may bundle with the editor in the future, ''I specifically choose not to use the folder version approach, and I am also very much in favor of using a version/timestamp query parameter instead.'' What I would prefer is that you include it as an version/timestamp value as "buried" default config setting that I can override via a config setting I specify--that will help with special cases where I may need to force a resource reload for my users. (A specific example is forcing a reload for mono vs color toolbar icons.)
