Page status dialog: sortable: false should hide num dropdown

[plagasul]

Setting sortable: false prevents the user from manually sorting pages BUT unless an alternative sortBy option is set, the same user needs to manually sort the page when publishing it.

I find this contradictory. Why would I prevent the user to manually sort but require her/him to manually sort ?

Instead I would find logical and useful that, if sortable is set to false AND no other sortBy method is provided, published pages are automatically sorted by number in the order of publication.

First page published gets 1, second gets 2, etc.

To be able to keep the pages in the order they were published seems to me a very logical, normal and expectable thing to be able to do. But right now that is only possible by some process such as creating a hook that saves publication date-time in a hidden field, then defining sortBy that field.

It seems to me that is perhaps a bit overkill in contrast to how basic and expectable such a feature seems to me.

Perhaps I am missing something here, of course.

Thank you very much

[plagasul]

A possible problem may arise when a published page is returned to draft status and published again, as I assume the page would get the last index position, as it has just been published.

If that happens by mistake, the user would find her/himself tied by the panel, as s/he would not have a way to fix the mistake.

Perhaps it would make sense to just have an option to deactivate the dropdown sorting menu on page publish dialog, but still keep drag and drop manual sorting. So pages are automaticallt sorted by number in their order of publication, but the user can still move them around in cases such as mistakes and similar.

[CydGoblin]

I Agree, I would love to be able to disable the option to pick the number and just add the entry at the end of the list