Bug #80235
closed
sectionIndex and CEs like shortcut and mailform
0%
Description
There is a checkbox Show in Section Menus in the Access-tab of nearly all CEs.
But some CEs still are missing this feature when they are selected
as a content-element using the Type select-field.
The checkbox to enable the CE for the sectionIndex
will disappear from the Backend if you select Shortcut (or Mailform for ex.).
So at the moment you have to use a work-around and switch back to
another content-type like Text,
choose enable/disable for the sectionIndex-checkbox,
reselect your wanted content-type like Shortcut
and you will finally get what you want:
Your Shortcut is taken care for in the sectionIndex-menu.
So my suggestion is:
Please enable the checkbox for Shortcut and other CEs who still
do not show this field in their BE dialog.
The working function to show up/hide the CE in the sectionIndex-menu are already
implemented and ready to use in typo3 v7.6!
And by the way: This is a great new feature!
Use it in responsive layouts and enjoy.
Updated by Riccardo De Contardi about 7 years ago
- Description updated (diff)
- Category set to Backend User Interface
- Status changed from New to Needs Feedback
Hello. As far as I can see, on TYPO3 7.6.16 the following behavior occurs:
the "show in section menu" checkbox is still present on both the "mail form" and "login form" CE but it is placed on the wrong tab! It is on the "Access" tab instead of the "Appearance" tab.
This behavior is streamlined on 8.x, where it always appear on the "Appearance" tab.
Can you confifrm? Thank you!
Updated by Benni Mack almost 7 years ago
- Target version changed from 8 LTS to Candidate for patchlevel
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
Candidate for patchlevel)
As there has been no feedback I tend to close this issue for now.
Moreover, TYPO3 7.6.x is in its "priority bugfix" phase of life, and only security and critical bugfixes will be developed.
If you think that this is the wrong decision or experience the issue again on newer TYPO3 versions, please reopen it or open a new issue with a reference to this one. Thank you.