Project

General

Profile

Actions

Bug #90194

closed

Question / Bug? shortcut_mode still set (not "0") after switch page back to page of type "standard"

Added by Jürgen Kulawig almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Pagetree
Target version:
-
Start date:
2020-01-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hello everybody,
this is my first post here and i hope i do everythng right and sorry for my bad english.

After investigation i found out, there had been a few issues with the functionality of the shortcut_mode.
I also saw that there are fixes for that in the TYPO3 version 9.5.13.
After updating now to the version 9.5.13 I probably found another bug.
Creating a standart page shows by debugging the fluid template the expected value shortcut_mode => 0
Changing the standart page to a page in shortcut-mode debugging shows me also the expected value shortcut_mode => 1 or 2 or 3 (depends on the selected option).
But after switch the shortcut-page back to a standard page, it still keeps the shortcut_mode => 1 or 2 or 3 and not reset the value and become shortcut_mode => 0 like expected.

Maybe someone can confirm that behavior and it is not because of some other settings of my system.
I am using english as default language and german as first foreign language. I also tryed to use only one language, because i read about the problems with shortcut and languages issues.

My setting:
TYPO3 9.5.13
Ext.: bootstrap_package 10.0.5
php 7.2.25

I hope i choose the right category "Pagetree" (could also be link handling, site handling ?)
Thanks for any hint or solution. Tahnks for reading and have a nice day.


Related issues 2 (2 open0 closed)

Related to TYPO3 Core - Feature #88908: Add "migration wizard" when changing CType of content elementsNew2019-08-03

Actions
Related to TYPO3 Core - Feature #76925: Switching from one content type to another should clear fields not usable anymoreNewBenni Mack2016-07-04

Actions
Actions #1

Updated by Jürgen Kulawig almost 5 years ago

update:
ok, now i found out that everything works like expected if you do it that way:
if you switch a standard page to become a shortcut page you have to select a mode option:
- selected page
- First subpage of selected / current page
- Random subpage
- Parent page
if you do so and select for example "First subpage of selected / current page" save that and watch. Everything is fine. Now you want to go back to a standard page without set the mode option "First subpage of selected / current page" back to "selected page" the shortcut-mode still shows the wrong state even the page is no more a shortcut-page and is not set back to be "0". So this keeps the value of the short-cut page even if the page is no longer a page of type short-cut. Shoult this value not switch back to "0" if the page is no shortcut page anymore?

If you first set the option mode back to "selected page" before you change the shortcut-page back to be a "standard" page, then the state shortcut-mode is like expectet "0"

So make sure, before you switch back a page of type shortcut to be a standart page set first back the option mode to "selected page" and dont let there be for example "First subpage of selected / current page" selected.

Can someone reproduce that behavior? And if so, is this the desired behavior
Thx.

Actions #2

Updated by Riccardo De Contardi over 4 years ago

  • Related to Feature #88908: Add "migration wizard" when changing CType of content elements added
Actions #3

Updated by Riccardo De Contardi over 4 years ago

  • Related to Feature #76925: Switching from one content type to another should clear fields not usable anymore added
Actions #4

Updated by Riccardo De Contardi over 4 years ago

  • Status changed from New to Closed

Hello and sorry for the late answer; this is the expected behavior, when you switch the page type (e.g. from shortcut to standard), the fields you have edited don't reset themselves and keep their value.

The same thing happens for example if you create a "Regular Text Element" content element, type something in the pagebody field and then switch its CType to "Header": the bodytext field does not reset its value, and when you switch back the element to "Regular Text Element", the content will be restored.

I close your issue as this is the expected behavior; if you think that I have misunderstood you and this is the wrong decision, please reopen it or ping me.

Actions

Also available in: Atom PDF