Story #69712: Further FormEngine development
Unable to set Publish Dates and Access Rights on any alternative language content element
In all alternative language content elements (not localised elements - this is for separate localisation) both 'Publish Date' and 'Expiration Date' fields are uneditable and show 01:00 01-01-1970. This means only the default language can be published as a timed element.
This happens in both live and custom workspaces.
Updated by Michael Stucki almost 10 years ago
- Category set to Backend User Interface
- Priority changed from Must have to Should have
It seems like this functionality was disabled because the feature has never worked (see #24211).
I'm actually wondering why the field was turned into read-only rather than fixing the real problem. Is it so hard to fix?
Updated by Andreas Kiessling over 9 years ago
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.