TYPO3 Core

Those fields where added in February 2009 for TYPO3 4.3.
The reasons are available here: http://forge.typo3.org/issues/16935

Maybe the change for 4.6 how shortcuts are treated causes this behavior.

Markus Klein wrote:

Those fields where added in February 2009 for TYPO3 4.3.
The reasons are available here: http://forge.typo3.org/issues/16935

Maybe the change for 4.6 how shortcuts are treated causes this behavior.

Ok, I understand. I've come back to see what was happening to the alternative page language. What I've seen is that when you come from an update from an old typo3 and the page is a shortcut, in the alternative page language the page type is still standard page.

May be the upgrade wizard must solve this incongruence or in any case advert for this.

http://forge.typo3.org/issues/28686

Same after Update from 4.5 to 4.7.2

All translation pages type shortcut are not working anymore. They are all back to page type standard.

Same after Update from 4.5 to 4.7.2

New tranlations of shortcuts only work if the target is set manually. No fallback to origin target, even though it's shown in the backend. Frontend just renders empty a-Tag with translated shortcut title

Sorry for the negative vote. That happened by accident. Unfortunately I'm not able to remove my vote again.

I seem to have the same bug in a 6.0.4 project (new site, no update). Can someone confirm the bug in 6.0?

Shortcut pages don't get linked in menue. The solution was to remove "shortcut" and "shortcut_mode" from $TYPO3_CONF_VARS['FE']['pageOverlayFields']. Thanks @ Goncal!

bug confirmed for 6.1.8

...well - bug or feature? lol

I consider it a bug:
translation of shortcut should be created as shortcut with same shortcut-mode/-target (by default)

not a bug:
you may still switch settings in translated record (in other words: keep "shortcut" and "shortcut_mode" in $TYPO3_CONF_VARS['FE']['pageOverlayFields'])

(hi JKI :-))