TYPO3 Core

Why thas this issue been change to 'should have'? We cannot publish timed content elements at the moment and this is a huge issue for us.

Please reconsider the importance of this bug. Thank you.

I agree with Sara.
This is a very important point for us to set different publish and unpublish dates.

We never discovered that this feature never worked. But this is somehow better for clients than disabling the fields.

This feature has always worked for us until we upgraded.

Please could someone bump this so it is solved. We have a huge problem in not being able to use this feature.

I also can't recall, that this feature "never worked".

The only thing that never worked, was to disable the default content element and only enable the overlay. But this is the case for pretty much all extensions.

getRecordOverlay uses enableFields and if the TS is set like this, then a disabled overlay will not be shown, either if it is hidden or due to start/endtime restriction

config.sys_language_overlay = hideNonTranslated
config.sys_language_mode = strict

enableFields does not analyse the l10n settings, so if you have previously entered dates in starttime/endtime, then you can't change them anymore...

@Sara and Henrik (hope it may still help you):
If you need to "enable" the fields again, you can unset the TCA config in your extTables.php

t3lib_div::loadTCA('tt_content');
unset($TCA['tt_content']['columns']['starttime']['l10n_display']);
unset($TCA['tt_content']['columns']['starttime']['l10n_mode']);
unset($TCA['tt_content']['columns']['endtime']['l10n_display']);
unset($TCA['tt_content']['columns']['endtime']['l10n_mode']);

I would highly appreciate to reconsider this change. If you use e.g. templavoila, i think it is very common to create content elements that have no "default" record. You can't even set a starttime/endtime for these elements, because sys_language_uid is tested in t3lib_TCEforms, and not if there is a value set for l18n_parent.
With the "classic" page module and styles.content.get, this is also doable, but probably not that common.

I would also appreciate if this could be reconsidered. If you add an element in the non-default language only, you have no way of setting the starttime/endtime. Therefore I don't see the advantage of disabling the fields...

I back that thought.

Configuration should probably be:
l10n_mode = mergeIfNotBlank

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44101

Could we have this bugfix to TYPO3 6.2, too?

Sorry, no chance for 6.2.