TYPO3 Core

We discussed that during the TCA optimization project and came to the conclusion, that "new until" is not related to access at all.

Reason: It changes the look of the page in the frontend but has no influence on the user access like the rest of the fields in the access tab.

start/stop, disable, hide in menus will remove access to the page partly or completely either by removing it from the navigation or by deactivating it for a certain group of users or within a certain timeframe.

"new until" does nothing like that, since out of the box it's just a marker. Of course you could abuse it for a kind of timeframe as well, but then it's up to you to provide the necessary change to the TCA palettes as well.

So IMHO this one should be closed.

You are right in the sense that at first sight "new until" seems not to be related to "access". But on the other hand, and looking into the field documentation, you can see clearly that it's related to "Publication Date" (as reminder of outdated content) event it's directly related there to field "Page/ Start" (through section "See also:")

Maybe a new discussion could be the fact that "Publish Date" and "Access Rights" are under the same tab named only "Access", but for some reason they are good looking together, not disturbing, hey they are related in some way.

I'm strongly convinced that "New until" will be definitely less disturbing near "Publish Date" than near "Page layout", as you don't expect that field between BE,FE layout selection, and as stated above, it's already related to "Publication Date" in doc.

This just means that the doc has to be changed accordingly, since it's misleading and outdated. "New until" has nothing to do with "publication date", since it will work completely indepently in the way I described in my first comment.

This is not the first time that the usage of a field has been wrongly interpreted in the label and/or CSH description.

Even the field name implies just the contrary of "mark pages in the backend that are outdated". Actually most of the projects I know of (if any) that made use of this field, created a real marker "new" in the frontend. This marker was removed as soon as the date given in "new until" was reached. This is why it has been used almost exclusively by shop systems presenting product pages of new articles this way.

BTW: The "Publish Date" and "Expiration Date" fields are not just related to Access. Actually they are by default part of the so called "enable fields" that will remove access to a page completely, when the timeframe and/or the usergroup is not matching the criteria set in these fields.

nav_hide is a kind of hybrid that will do the same for any menu that would have rendered the page, thus restricting access partly, since the page will still be active when you type in the url.

Sure, from a " 'New until' can be used to change the page rendering in the frontend" point of view, to place it near "Page Layout" fields make sense now.

My suggestion for the new placement for the field was made from a point of view were the usage of it was a described in the CSH doc. In such case I wasn't able to find the field related to page layout more than to content publication.

I agree with Joey, if you give the field a meaning in your project, you can rearrange the fields. But as pointed out, it has nothing to do with Access.

Are you fine with closing this issue?

Sure, I guess maybe should us to open another issue so CSH is changed, as suggested by Joy? That way the field placement has sense for everybody and not same issue arises.