TYPO3 Core

i would say option two is more logical and maybe easier to implement. to me it is not be a new pagetype.

doktype IMHO is a no go, since there might be different doktypes to be hidden/unhidden in menus.
So "hide in menu" always adds up to the selected doktype, which is why it should be a click menu option.

I'd also go for option two, pretty much for the same reasons JoH pointed out. Hide in menu is an option available to most doctypes, so it can't be a doctype itself.

I don't think 1) is a good option since we had doktype 5 (not in menu) already in former times and it got removed with TYPO3 4.2 (see http://bugs.typo3.org/view.php?id=7370)

Okay, many points for option 2 and I am positive about it now, too.

So, my next questions:
Where should it be positioned in the click menu?
Below the hide function?
In the submenu "page actions"?

Thomas Loeffler wrote:

Now looks like this.

Having this action below the delete action does not look right for me. The most logical place for me would be below or above the Disable action in the top level.

I think the Usability Team should have a look on it.
A new position is implemented very fast.

Hi,

I would suggest:

A.)¶

1. Show
2. -------
3. Edit
4. Info
5. History
6. -------
7. Hide in Menu
8. Disable
9. -------
10. Page actions
11. Branch actions

Or:

B.)¶

1. Show
2. -------
3. Edit
4. Info
5. History
6. -------
7. Disable
8. -------
9. Page actions
   1. New
   2. -------
   3. Hide in Menu
   4. -------
   5. Cut
   6. Copy
   7. -------
   8. Delete
10. Branch actions

I think "A" would be the better way to go.

Because all actions we moved into "Page actions"
are "Drag&Drop" actions we could archive in the
Page-Tree. This would Exclude "Hide in Menu" as
part of this Sub-Menu. Right?! :)

Greez Jens

Sounds good, but do you want to move the "disable" action?
Right now it is above "Edit" action and is it possible that many people will be confused to see it below "history"?
Maybe:

1. Show
2. -------
3. Disable
4. Not in menu
5. -------
6. Edit
7. Info
8. History
9. -------
10. Page Actions
11. Branch Actions

I'd also go with Jens' plan A

@Thomas:

I think we should order it more in terms of "priority by demand".
But I would try to keep the groups - as we have them right now.
So "Edit" is part of the Group (Edit, Info, Undo), but that is more
often used than "Not in menu" / "Disable". That's why I would like
to reorder that. And in terms of "priority by result-dependency"
"Hide in menu" needs to be before "Disable", as this creates a lot
more "result-dependency's" for the user :) And "result-dependency"
always get sorted descending. I'm sure: This is the right way to go.

This is why I suggested "A", like I did :)

Greez Jens

BTW: Great Idea, to have this in there! :) THX

You're welcome! And "A" is good. :)
I will change the patch set tonight.

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15252

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15252