Project

General

Profile

Actions

Feature #55237

closed

Make Publish/Expiration Date editable for CEs in non-default language

Added by Markus Kobligk about 10 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-01-22
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

After translating a page on a blank and freshly installed 4.7.17 I added one Text CE in the default language and set the Publish and Expiration date of that CE.
I translated that CE using the button "Copy default content elements" into the other language and additionally I added another CE directly into the other language (see languages.gif).
In both, the translated CE and the not translated CE, the fields for Publish/Expiration Date are not editable at all (see access.gif).

TS-Setup:

page = PAGE
page.10 < styles.content.get

config {
  sys_language_uid = 0
  language = en
  locale_all = en_EN.UTF-8
  htmlTag_langKey = en
  htmlTag_dir = ltr
}

[globalVar = GP:L = 1]
  config {
    sys_language_uid = 1
    language = de
    locale_all = de_DE.UTF-8
    htmlTag_langKey = de 
    htmlTag_dir = ltr
  }
[global]

Is this a missing feature or am I just missing some Typoscript config or a setting in the Install Tool?


Files

languages.gif (61.6 KB) languages.gif Markus Kobligk, 2014-01-22 10:58
access_nottranslated_ce.gif (16.9 KB) access_nottranslated_ce.gif Markus Kobligk, 2014-01-22 10:58
access_translated_ce.gif (18.3 KB) access_translated_ce.gif Markus Kobligk, 2014-01-22 10:58

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #68043: Unable to set Publish Dates and Access Rights on any alternative language content element in TYPO3 6.2.14Closed2015-07-10

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

Actions
Actions #1

Updated by Markus Kobligk about 10 years ago

  • Assignee deleted (Kay Strobach)
Actions #2

Updated by Markus Howald about 10 years ago

I can reproduce the same behaviour in a TYPO3 6.1.7 installation.

Additionaly I realized the following:
I created a Text CE in the default language and set an expiration-date.
Next, I made a translation of this element to the other language – in there I can see (not modify) the correct expiration-date.

After the expiration-date passed, the CE in the default language was hidden correctly, the CE in the other language was NOT HIDDEN – despite the correctly set expiration-date I could still see it in the frontend.

Actions #3

Updated by Riccardo De Contardi over 8 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

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

SET 1

1) create a CE in default language
2) set an expiration date
3) translate it

RESULT: the expiration date works in both versions

SET 2

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 #4

Updated by Mona Muzaffar almost 7 years ago

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 #5

Updated by Mona Muzaffar almost 7 years ago

  • Project changed from 406 to TYPO3 Core
  • Category deleted (Technical)
  • Status changed from New to Closed
Actions

Also available in: Atom PDF