Project

General

Profile

Actions

Bug #89086

closed

Third party extension requireJS modules are cached by browsers despite version update

Added by Benjamin Franzke about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Category:
Backend JavaScript
Start date:
2019-09-05
Due date:
% Done:

100%

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

Description

An Extension that contains requireJS modules in Resources/Public/JavaScript and includes a module in the backend using

    $this->getPageRenderer()->loadRequireJsModule('TYPO3/CMS/ExtensionName/JavascriptModule');

can not update the JavascriptModule on extension updates, as the TYPO3 PageRenderer calculates a cache busting hash (for all requireJS modules)
from the current TYPO3_version and project path. Third party extension version are not taken into account.

That means a cache bust parameter, e.g "abcdefghijklmnopqrstuvwxyz1234567890abcdef" would be applies to the url:

/typo3conf/ext/extension_name/Resources/Public/JavaScript/JavascriptModule.js?bust=abcdefghijklmnopqrstuvwxyz1234567890abcdef

…but that hash is not changed when the Extension Version changes.

Note: For performance reasons only the extension version number should be taken into account. (File modification times would only be important for development scenarios where a separate development cache parameter override is available).


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #91886: No automatic reload of changed static assets (JavaScript, css, images) in TYPO3 backendClosed2020-07-29

Actions
Actions

Also available in: Atom PDF