Project

General

Profile

Actions

Bug #42476

closed

pageTSconfig: mod.web_layout.menu.function.3=0 does not work

Added by Edward Lenssen over 11 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-10-29
Due date:
% Done:

0%

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

Description

pageTScofig mod.web_layout.menu.function.3=0 does not work in TYPO3 4.7
(disable page information in pagemodule)

does work in 4.5

Actions #1

Updated by Felix Kopp over 11 years ago

Hi Edward,

could you please try to use the function "disablePageInformation"?

Here you can find the documentation
http://typo3.org/documentation/document-library/core-documentation/doc_core_tsconfig/4.7.0/view/1/4/#id552919

You can put the line

mod.web_layout.disablePageInformation = 1

into the field "Page TSConfig" on a page to remove the Page Information for this and all sub pages.
The Page Information function will be removed in TYPO3 6.0 completely.

Actions #2

Updated by Edward Lenssen over 11 years ago

Hi Felix,

thanks for feedback. You are right. It works.

Edward

Actions #3

Updated by Thorsten Kahler over 11 years ago

  • Project changed from TYPO3 Core to 1111
  • Category deleted (Backend User Interface)

Moved to project Documentation > Official Documentation > TSconfig.

Don't know if it's worth the effort to add the info to the documentation of a single version (4.7).

Actions #4

Updated by Chris topher over 11 years ago

  • Subject changed from pageTScofig mod.web_layout.menu.function.3=0 does not work 4.7 to pageTSconfig: mod.web_layout.menu.function.3=0 does not work

I don't think that we should start documenting bugs instead of fixing them.
Apart from that something like "Is still there and is supposed to work, but got broken." in the docs would be kind of a silent "removal through the backdoor", which would circumvent our deprecation policy that TypoScript options, which should be removed, must be deprecated first. If we wanted to remove this option, we would have to deprecate it, wait for two major versions and then it could finally be removed. However, neither deprecation nor removal have been done, so there is nothing to document.

I can't see that the function mod.web_layout.menu.function.x=y (which has neither been removed, nor deprecated) would not make sense anymore. Hiding unneeded items in the interface always is a good thing to prevent clutter. Such options have proven to be helpful for editors - deprecating useful options (to finally be able to remove them) is the wrong way.

Instead this bug should be fixed.

Actions #5

Updated by Chris topher over 11 years ago

  • Project changed from 1111 to TYPO3 Core
Actions #6

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Closed
  • Is Regression set to No

works in master

Actions

Also available in: Atom PDF