Project

General

Profile

Actions
Copy link

Bug #78134

closed

config.noScaleUp no longer works

Added by Josef Glatz over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Josef Glatz
Category:
Frontend
Target version:
8.4
Start date:
2016-10-03
Due date:
% Done:

100%

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

Description

Problem/Description

TypoScript config.noScaleUp no longer works since:

Commit 1f4b97454d05d7cb1be2a78b6a6e9f8fad736942
https://review.typo3.org/#/c/42385/
https://forge.typo3.org/issues/43085
https://github.com/TYPO3/TYPO3.CMS/commit/1f4b97454d05d7cb1be2a78b6a6e9f8fad736942#diff-2706384679a406d049dd75857e4c4ebeL105

Since then, config.processor_allowUpscaling is checked and it's reversed now.

Generally, it would make sense to switch to (e.g.) config.allowUpscaling, but we have to announce that as breakingchange-rst or by deprecating the old one config.noScaleUp AND of course, adding that information in the TYPO3 documentation!

My suggested solution

I would suggest to deprecate the old one and switch to a meaningful naming like config.allowUpscaling

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Task #43085: Rename setting im_version_5 to something more appropriateClosedMorton Jonuschat2012-11-18

Actions
Related to TYPO3 Core - Bug #78317: Deprecate config.noScaleUpClosed2016-10-17

Actions
Actions
Copy link

Also available in: Atom PDF