Project

General

Profile

Actions

Bug #48213

closed

compressJs wrong filenames

Added by Philipp Müller over 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Content Rendering
Target version:
Start date:
2013-05-15
Due date:
% Done:

100%

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

Description

Hello

If the Javascript-Compression is active (config.compressJs=1), the wrong file will be linked in frontend.

Example 1 (okay):

We activate the concatenation without compression, this will be rendered correctly.

Configuration:

config.concatenateJs = 1
config.compressJs = 0

Current output (okay):

<script src="/typo3temp/compressor/merged-095e3e9d46fe1467bd0fcc810eecfebc.1368606638.js" type="text/javascript"></script>

Example 2 (not okay):

We activate the concatenation and the compression, now we get the same output (what's wrong).

Configuration:

config.concatenateJs = 1
config.compressJs = 1

Current output (wrong):

<script src="/typo3temp/compressor/merged-095e3e9d46fe1467bd0fcc810eecfebc.1368606638.js" type="text/javascript"></script>

Correct output:

<script src="/typo3temp/compressor/merged-095e3e9d46fe1467bd0fcc810eecfebc-2e491ef033fef81687e5e020c7445d74.js.1368606673.gzip" type="text/javascript"></script>

The error occurs in the function compressJsFiles in TYPO3\CMS\Core\Resource\ResourceCompressor. There the new filename will not be set as array-key (the array-key will be used as filename in output). In compressCssFiles this error is already fixed.

I've added a patch to fix this issue.

Best regards
Philipp


Files

compressJsIssue.diff (993 Bytes) compressJsIssue.diff Philipp Müller, 2013-05-15 12:03

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #27694: Speedup backend and allow compression in frontend ClosedKai Vogel2011-06-25

Actions
Actions

Also available in: Atom PDF