Project

General

Profile

Actions
Copy link

Bug #79968

closed

Publish Dates does not work in translated content elements

Added by Bernd Fallert over 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2017-02-23
Due date:
% Done:

0%

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

Description

In TYPO3 7.6.15 Publish Date / Expiration Date for translated content elements will no working.

If i insert an content element on the default language page "Publish Date / Expiration Date" will work.

If i insert a translation of this object i can see the same time for "Publish Date / Expiration Date" but the element is shown on the webside as well if the "Publish Date" is in the future.

It works on the default language page, but not on the translated page

Thanks
Bernd Fallert

Actions
Copy link
 #1

Updated by Bernd Fallert over 7 years ago

  • Category changed from Backend API to Content Rendering

Its posible more Content Rendering then Backend API

Sorry for that

Actions
Copy link
 #2

Updated by Riccardo De Contardi over 7 years ago

I performed the following test with 7.6.18, 8.7.1 and 9.0.0-dev (latest master)

1) create a page in default language (ITA) and translate it (ENG)
2) Create a content element and set its publishing date in the future (a couple of days)
3) Translate the content element in english (translate mode)
3.1) the publish date of the translated content is not editable but it is the same as the original one (correct).
4) Preview the translated page

Results:

7.6

the translated element is visible (wrong)

N.b. I repeated the same test with "Copy mode"; in this case the "publish date" of the translated element is empty and can be set (and works)

8.7.1 and Master (9.0.0-dev)

the translated element is not visible - the issue is absent

Actions
Copy link
 #3

Updated by Mona Muzaffar over 7 years ago

  • Category changed from Content Rendering to Localization
Actions
Copy link
 #4

Updated by Riccardo De Contardi about 5 years ago

  • Status changed from New to Closed

I think that this issue can be safely closed for the following reasons:

  • No feedback since very long time
  • The issue seems to affect only version 7.6 which has been discontinued since December, 2018

Of course if you think that this is the wrong decision or that my test is not comprehensive and experience the issue again (on version 8.7 or 9.5 or 10), please reopen it or ping me.

Thank you and best regards.

Actions
Copy link

Also available in: Atom PDF