Project

General

Profile

Actions

Bug #20659

closed

TCAdefaults in Page TSConfig without effect on creating new element after existing one

Added by Ralf Hettinger over 15 years ago. Updated almost 15 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2009-06-23
Due date:
% Done:

0%

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

Description

TCAdefaults set in Page TSConfig don't have effect when creating a new element after an existing one.

This happens e.g. in list module when hitting a new button placed at some existing element or when using the "saveDocNew" button.

Reason is that the pid doesn't make it through t3lib_transferData->fetchRecord, since no translation from the "new" id takes place (new element after existing one => negative value of the existing element uid). Therefore the proper rootLine cannot be fetched and no Page TSconfig can be assigned to this to be created record. Attached patch fetches pid of the "-uid" element in that case before getting the rootline and Page TSConfig.

Page TSConfig:
TCAdefaults.tt_content.CType = textpic

1) create new tt_content as the very first element => type is textpic
2) create new tt_content after existing tt_content element => type is text (or the one set by User TSConfig)

(issue imported from #M11395)


Files

11395.patch (882 Bytes) 11395.patch Administrator Admin, 2009-06-23 21:57
11395_v2.patch (736 Bytes) 11395_v2.patch Administrator Admin, 2009-11-28 20:01
11395_v3.patch (727 Bytes) 11395_v3.patch Administrator Admin, 2009-11-28 23:00
0011395_v5.patch (735 Bytes) 0011395_v5.patch Administrator Admin, 2009-11-29 17:44
Actions #1

Updated by Oliver Hader almost 15 years ago

Committed to SVN Trunk (rev. 6588)

Actions

Also available in: Atom PDF