ReStructured Text Infrastructurewiki.typo3.orgOfficial Documentation

Bug #12824

mod.wizards.newRecord does not work in User TSconfig

Added by Chris topher over 2 years ago. Updated about 2 years ago.

Status:Closed Start date:2011-02-06
Priority:Should have Due date:
Assignee:Chris topher % Done:

100%
Category:-
Target version:4.5.1
Votes: 0

Description

The caption of the table (in the manual) says it would work in both Page and User TS.

In my test
mod.wizards.newRecord.order = tt_news

only had an effect when set in the Page TS.

Setting it in the User TSconfig did not change the order of the options.

Wrong documentation or bug in PHP code?

mod.wizards.newRecord.order.gif - Effect of "mod.wizards.newRecord.order = tt_news" in Page TSconfig (17.5 kB) Chris topher, 2011-02-06 14:34

Related issues

related to TSconfig - Bug #12831: Update Table Captions New 2011-02-06

History

#2
Updated by Francois Suter over 2 years ago

Did you write as:

page.mod.wizards.newRecord.order = tt_news

?

#3
Updated by Chris topher over 2 years ago

Francois Suter wrote:

Did you write as: page.mod.wizards.newRecord.order = tt_news ?

No, I wrote it without "page." at the beginning. It in fact works when you put it starting with "page.".

But it should also work without, see User TS, TLO, mod:

see ->MOD of Page TSconfig
Overriding values for the backend modules
Deprecated. Use page.mod instead!

However, that this does not work is no "bug" in the docs.

But something else:
What about the table caption?
It says: "[page:mod.wizards.newRecord; beuser:mod.wizards.newRecord]"
And the second does not work that way.

#4
Updated by Francois Suter over 2 years ago

You're right that it should work, but OTOH we're not going to fix a deprecated behavior. So I would say we should rather adjust the doc so that it fits the current behavior of the Core.

#5
Updated by Chris topher over 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Chris topher
  • % Done changed from 0 to 100

Francois Suter wrote:

(...) So I would say we should rather adjust the doc so that it fits the current behavior of the Core.

Will be part of the next commit. See #11398.

#6
Updated by Francois Suter about 2 years ago

  • Target version set to 4.5.1

#7
Updated by Francois Suter about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF