0001428: Some TCAdefaults work only with "Page (inside)" and not with the Wizard

(0003838)
Sebastian Kurfuerst (administrator)
10.11.05 12:26

Hi,
can you please make a screenshot to clarify this?
Thank you, Sebastian

(0004830)
old_MarkusWagner (reporter)
29.12.05 18:42

Hi Sebastian! Sorry for being late, I had no time for it until now. Made 2 screenshots to show the problems (zipped), had configuration "TCAdefaults.pages.hidden=1" and "TCAdefaults.pages.doktype=2" in User TSConfig.
This configuration only works when working without the wizard (pic 1), with the wizard it seems that the configuration doesn't work (pic 2). It is funny that this all does not happen when using the wizard to add a page UNDER the currently selected page (looks like pic 1).
I used a fresh 3.8 install to test it.

(0004863)
Jesus Hormigo (reporter)
29.12.05 23:07
edited on: 30.12.05 21:07

After trying over a 3.8.1 over an empty installation with 1 page created and with the following TSConfig:

TCAdefaults.pages.hidden = 1
TCAdefaults.pages.doktype = 2

I tested that works perfectly well when creating it with the wizard or creating it with Page (inside).

I evaluated the pictures you sent and I noticed that the error you noticed is because you point where you try to create the PIC2.jpg page is underneath the page and NOT inside. So you can observe it'll sit on / and not under /root/ page you created and therefor is not affected by any TSConfig.

(0004864)
Sebastian Kurfuerst (administrator)
29.12.05 23:10

Hi,
I close the bug for now. If there is more information, please re-open the bug.

Thanks, Greets, Sebastian

(0004877)
old_MarkusWagner (reporter)
30.12.05 13:00

@Jesus:
I think I understand what point you are taking me to, but I don't think you're right.
User TSConfig (!!) should ALWAYS affect ANY site, no matter if it is under or on a specific site.

(0004878)
Sebastian Kurfuerst (administrator)
30.12.05 13:13

It might be that the problem just exists when the new page is in the root level.. Just a guess.

Greets, Sebastian

(0004880)
Jesus Hormigo (reporter)
30.12.05 13:25

I confirm that this don't happens on a PAGE TSCONFIG level but IT HAPPENS on a USER TSCONFIG level.

Markus thanks for the clarification specifying it was at USER TSCONFIG level (sorry for not read it properly in your comment 29.12.05 18:42). It only happens when adding the page at a root level, if you add it inside a root level page works for Page inside and wizard.

(0004881)
old_MarkusWagner (reporter)
30.12.05 13:47

I can also confirm this: it only happens when adding a page to the rootlevel with the wizard.

(0004882)
Ernesto Baschny (administrator)
30.12.05 15:15

Hi,

This only happens if you choose to place the new page "AFTER" some existing page, no matter which level you are. Placing the page right on top of the presented page tree or as the first page INSIDE some other page the problem doesn't appear.

The problem is: the defaults set in TCEdefaults conflict with the "ctrl.useColumnsForDefaultValues" setting in TCA for the pages table (which is "doktype,fe_group,hidden" by default). This setting tells TYPO3 to use the values from the previous peer page for these fields in the newly created page.

So this might be considered a bug if you want TCEdefaults to override any other setting (even useColumnsForDefaultValues). In that case, the fix would be to reverse the "Default values as set in userTS:" and "Fetch default values if a previous record exists" parts in class.t3lib_transferdata.php, method fetchRecord().

In my opinion they should be reversed, as the expected behaviour is exactly that one: TCEdefaults override any other setting, even TCA.

(0011961)
Benjamin Mack (developer)
24.01.07 21:49

This bug still exists in 4.0.4 and it is a bug as long as it behaves different when clicking on "New page inside" and "New page after".

(0023339)
Marc W?hlken (reporter)
16.07.08 16:21

This bug is still present in TYPO3 version 4.2.1

(0024084)
Steffen Kamper (developer)
25.08.08 18:47

Thanks Ernesto for this very good description of the problem.
With this i was able to write a patch in short time.

Please test it and confirm.

What i did? After reading the useColumnsForDefaultValues i look if a value is set befor by TSconfig and only use the value if it's not. So TS overrides useColumnsForDefaultValues in any case.

vg Steffen

Issue History
Date Modified	Username	Field	Change
03.09.05 21:30	old_MarkusWagner	New Issue
03.09.05 21:30	old_MarkusWagner	PHP Version	=> 4
03.09.05 21:30	old_MarkusWagner	TYPO3 Version	=> 3.8.0
10.11.05 12:26	Sebastian Kurfuerst	Note Added: 0003838
10.11.05 12:26	Sebastian Kurfuerst	Issue Monitored: Sebastian Kurfuerst
29.12.05 18:42	old_MarkusWagner	Note Added: 0004830
29.12.05 18:43	old_MarkusWagner	File Added: 0001428.tar.gz
29.12.05 23:07	Jesus Hormigo	Note Added: 0004863
29.12.05 23:10	Sebastian Kurfuerst	Status	new => resolved
29.12.05 23:10	Sebastian Kurfuerst	Resolution	open => no change required
29.12.05 23:10	Sebastian Kurfuerst	Assigned To	=> Sebastian Kurfuerst
29.12.05 23:10	Sebastian Kurfuerst	Note Added: 0004864
30.12.05 13:00	old_MarkusWagner	Status	resolved => feedback
30.12.05 13:00	old_MarkusWagner	Resolution	no change required => reopened
30.12.05 13:00	old_MarkusWagner	Note Added: 0004877
30.12.05 13:13	Sebastian Kurfuerst	Note Added: 0004878
30.12.05 13:25	Jesus Hormigo	Note Added: 0004880
30.12.05 13:27	Sebastian Kurfuerst	Status	feedback => confirmed
30.12.05 13:47	old_MarkusWagner	Note Added: 0004881
30.12.05 15:15	Ernesto Baschny	Note Added: 0004882
30.12.05 21:07	Jesus Hormigo	Note Edited: 0004863
24.01.07 21:49	Benjamin Mack	Note Added: 0011961
24.01.07 21:49	Benjamin Mack	Issue Monitored: Benjamin Mack
29.05.08 00:20	Ralf Hettinger	Issue Monitored: Ralf Hettinger
16.07.08 16:21	Marc W?hlken	Note Added: 0023339
25.08.08 18:47	Steffen Kamper	Note Added: 0024084
25.08.08 18:47	Steffen Kamper	File Added: tsconfig_vs_useColumnsForDefaultValues.diff
12.09.08 14:47	Patrick Rodacker	Issue Monitored: Patrick Rodacker
25.05.10 17:58	Christopher	Relationship added	related to 0004388
01.06.10 11:33	Ernesto Baschny	Issue Monitored: Ernesto Baschny

Notes
(0003838) Sebastian Kurfuerst (administrator) 10.11.05 12:26	Hi, can you please make a screenshot to clarify this? Thank you, Sebastian

(0004830) old_MarkusWagner (reporter) 29.12.05 18:42	Hi Sebastian! Sorry for being late, I had no time for it until now. Made 2 screenshots to show the problems (zipped), had configuration "TCAdefaults.pages.hidden=1" and "TCAdefaults.pages.doktype=2" in User TSConfig. This configuration only works when working without the wizard (pic 1), with the wizard it seems that the configuration doesn't work (pic 2). It is funny that this all does not happen when using the wizard to add a page UNDER the currently selected page (looks like pic 1). I used a fresh 3.8 install to test it.

(0004863) Jesus Hormigo (reporter) 29.12.05 23:07 edited on: 30.12.05 21:07	After trying over a 3.8.1 over an empty installation with 1 page created and with the following TSConfig: TCAdefaults.pages.hidden = 1 TCAdefaults.pages.doktype = 2 I tested that works perfectly well when creating it with the wizard or creating it with Page (inside). I evaluated the pictures you sent and I noticed that the error you noticed is because you point where you try to create the PIC2.jpg page is underneath the page and NOT inside. So you can observe it'll sit on / and not under /root/ page you created and therefor is not affected by any TSConfig.

(0004864) Sebastian Kurfuerst (administrator) 29.12.05 23:10	Hi, I close the bug for now. If there is more information, please re-open the bug. Thanks, Greets, Sebastian

(0004877) old_MarkusWagner (reporter) 30.12.05 13:00	@Jesus: I think I understand what point you are taking me to, but I don't think you're right. User TSConfig (!!) should ALWAYS affect ANY site, no matter if it is under or on a specific site.

(0004878) Sebastian Kurfuerst (administrator) 30.12.05 13:13	It might be that the problem just exists when the new page is in the root level.. Just a guess. Greets, Sebastian

(0004880) Jesus Hormigo (reporter) 30.12.05 13:25	I confirm that this don't happens on a PAGE TSCONFIG level but IT HAPPENS on a USER TSCONFIG level. Markus thanks for the clarification specifying it was at USER TSCONFIG level (sorry for not read it properly in your comment 29.12.05 18:42). It only happens when adding the page at a root level, if you add it inside a root level page works for Page inside and wizard.

(0004881) old_MarkusWagner (reporter) 30.12.05 13:47	I can also confirm this: it only happens when adding a page to the rootlevel with the wizard.

(0004882) Ernesto Baschny (administrator) 30.12.05 15:15	Hi, This only happens if you choose to place the new page "AFTER" some existing page, no matter which level you are. Placing the page right on top of the presented page tree or as the first page INSIDE some other page the problem doesn't appear. The problem is: the defaults set in TCEdefaults conflict with the "ctrl.useColumnsForDefaultValues" setting in TCA for the pages table (which is "doktype,fe_group,hidden" by default). This setting tells TYPO3 to use the values from the previous peer page for these fields in the newly created page. So this might be considered a bug if you want TCEdefaults to override any other setting (even useColumnsForDefaultValues). In that case, the fix would be to reverse the "Default values as set in userTS:" and "Fetch default values if a previous record exists" parts in class.t3lib_transferdata.php, method fetchRecord(). In my opinion they should be reversed, as the expected behaviour is exactly that one: TCEdefaults override any other setting, even TCA.

(0011961) Benjamin Mack (developer) 24.01.07 21:49	This bug still exists in 4.0.4 and it is a bug as long as it behaves different when clicking on "New page inside" and "New page after".

(0023339) Marc W?hlken (reporter) 16.07.08 16:21	This bug is still present in TYPO3 version 4.2.1

(0024084) Steffen Kamper (developer) 25.08.08 18:47	Thanks Ernesto for this very good description of the problem. With this i was able to write a patch in short time. Please test it and confirm. What i did? After reading the useColumnsForDefaultValues i look if a value is set befor by TSconfig and only use the value if it's not. So TS overrides useColumnsForDefaultValues in any case. vg Steffen


It's not a bug, it's a missing feature.	bugs.TYPO3.org