Feature #47850
open
Better BE preview for tt_content.type=shortcut (linked CE)
Added by Kay Strobach almost 11 years ago. Updated over 1 year ago.
0%
Description
It would be great if the backend preview of linked tt_content elements would be more detailed.
I think the best would be have the same preview as for the original content element + a prefix, which indicates that this item is a linked element :D
Updated by
Updated by Kay Strobach almost 11 years ago
hello georg,
currently not, i'm fully taken into account with may day work and the work in ext:themes, which will make it possible to use themes in TYPO3 CMS :(
As there is a hook for rendering the preview it shouldn't be to complicated to solve this :)
I think the solution will be:
1. Hook into the preview mechanism for content elements in the pagemodule
2. fetch the preview of the other record by running the hook pipe with the other plugin as parameter
After reading the article, which points to the hook, perhaps i find the time. - Should be a no brainer with big Usability improvement :D
Thanks Kay
Updated by Thorsten Kahler almost 11 years ago
- Subject changed from Better Preview for tt_content.type=shortcut (linked CE) to Better BE preview for tt_content.type=shortcut (linked CE)
- Status changed from New to Accepted
- Complexity set to medium
Updated by Ernesto Baschny over 10 years ago
- Priority changed from Should have to Could have
Yes, that would be a cool feature. Still time to work on that, Kay?
Updated by Jo Hasenau over 10 years ago
We already got that for Gridelements 1.x and 2.x so maybe we can do something about it during the Gridelements weekend.
Otherwise somebody else of the active contributors might want to take a look at the code and just copy the appropriate parts.
We just need to know if this will happen with 6.2 LTS at all, since we would have to provide a compatibility version of Gridelements then.
Updated by Nicole Cordes over 10 years ago
IMHO we shouldn't forget that the shortcut can handle more than one element. So maybe we should consider to use only limited text, uids and/or header
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 8 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Felix Nagel almost 8 years ago
A client called my attention to something we might wan't to improve: when translating a CE shortcut, the preview is in the default language - even if there is a translation available for the referenced record.
Steps to reproduce:- Create a new page A with a record
- Translate page B incl. its content
- Create a new page B
- Create a shortcut to the default language record on page A
- Translate page B incl. its content
Preview of translated page B now shows default language of our referenced record as preview. Of course it's possible to change the translated shortcut reference to the translated record but should't this work without changing? Using the default record seems more suitable and works as expected in frontend.
I've confirmed this in a 6.2 and a 8.1 installation.
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Susanne Moog over 6 years ago
- Target version changed from 9.0 to 9 LTS
Updated by Susanne Moog over 5 years ago
- Target version changed from 9 LTS to Candidate for Major Version
Updated by Oliver Hader over 1 year ago
- Sprint Focus deleted (
On Location Sprint)