Project

General

Profile

Actions

Bug #68043

closed

Unable to set Publish Dates and Access Rights on any alternative language content element in TYPO3 6.2.14

Added by Eric Rupp over 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2015-07-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I try and search Google and all TYPO3 sites to find a solution.

I have a multilanguage site and want to set a publish date in all languages, sometimes on all, sometimes only on one. It is only possible to set the time and date of the default language but the fields in other languages are just grey and not editable...


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #55237: Make Publish/Expiration Date editable for CEs in non-default languageClosed2014-01-22

Actions
Related to TYPO3 Core - Bug #24211: starttime / endtime l10n_mode exclude in core tablesClosedTolleiv Nietsch2010-11-26

Actions
Actions #1

Updated by Riccardo De Contardi about 9 years ago

Premise: when you translate a content element from default language to alternate language, it is correct that the fields publish/expiration dates are disabled: see #68312
the correct way to set publish/expiration dates is to create the CE as an indipendent record only in the alternate language.

Please be sure that you set

config.sys_language_overlay = 0

I performed a test with both 6.2.15 and 7.6-dev (latest master) and these are my findings:

1) set config.sys_language_overlay = 0
2) create a CE ONLY in the alternate language

RESULT
- on version 6.2.15 the publish/expiration dates are still disabled
- on version 7.6 they are editable and work as expected

Actions #2

Updated by Riccardo De Contardi over 8 years ago

  • Category set to Localization
Actions #3

Updated by Riccardo De Contardi about 8 years ago

Still present on 6.2.26

Actions #4

Updated by Mona Muzaffar over 7 years ago

  • Status changed from New to Closed

I am closing this ticket.
As Riccardo said this seems to be fixed in 7.6 and it won't be fixed for 6.2 anymore.

If you think that this is the wrong decision or experience this issue again,
then please reopen this ticket or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF