Project

General

Profile

Actions

Bug #88369

closed

Ckeditor: customs plugins are not refreshed because of browser cache

Added by Rémy DANIEL almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
RTE (rtehtmlarea + ckeditor)
Target version:
-
Start date:
2019-05-16
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When a custom CKEditor plugin is modified, if it was in the browser cache before, the old version can be loaded.

To prevent this, CKEDITOR.timestamp can be used to add a "?t=" parameter to the url of plugins JS files.
CKEDITOR.timestamp has a default value in ckeditor.js and changes with every ckeditor releases.
On TYPO3 8.7 with ckeditor 4.11.1, CKEDITOR.timestamp is "IA8E" (it is not a real timestamp).

TYPO3 should override CKEDITOR.timestamp with a custom hash.
In a ideal scenario, this hash should be recalculated every time a custom plugin is edited.
But it is not very possible.

So I suggest that this hash can be the result of a MD5 of ckeditor configuration.
Every time the configuration is changed (like when adding an external plugin), the hash will change, and the browser cache will not serve an old version of a plugin.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #83626: CKEditor styling: CSS file changes are not visible because of cache handlingNew2018-01-21

Actions
Actions

Also available in: Atom PDF