Project

General

Profile

Actions

Bug #22555

closed

Can't translate draft version of element in custom draft workspace

Added by Robert Heel over 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2010-04-30
Due date:
% Done:

0%

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

Description

I've tried the following in T3 4.2.12, 4.3.3 and 4.4.0b1:

1) Create a custom workspace, a Website Language, and in live workspace a Page with an Alternative Page Language
2) Create a content element in live workspace in the default language
3) Change to workspace
4) Edit the element in default language to create a workspace version of it. Only save it or edit element again after save&close.
5) Create translation of the element using the dropdown box on top of page (Language [NEW]).
The translated element has "INVALID VALUE" in Transl.Orig

(issue imported from #M14263)


Files

0014263_translate_draft.diff (1.33 KB) 0014263_translate_draft.diff Administrator Admin, 2010-05-05 12:08
0014263_translate_draft_v2.diff (1.14 KB) 0014263_translate_draft_v2.diff Administrator Admin, 2010-05-26 14:15

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #20173: in Draft workspace: changed tt_content-element looses relation to translated element in edit viewClosedBenni Mack2009-03-12

Actions
Related to TYPO3 Core - Bug #17610: wrong references between translated content in Workspace and its parentClosedBenni Mack2007-09-17

Actions
Actions #1

Updated by Chris topher over 14 years ago

Related to #6357.

Actions #2

Updated by Robert Heel over 14 years ago

Attached Patch. Fetch the original record if no language original is available.

Actions #3

Updated by Chris topher over 14 years ago

Hi Robert,

thanks for the patch!

To get this fixed in future releases, send your patch to the TYPO3-core-list!
Check out http://typo3.org/teams/core/core-mailinglist-rules/

Actions #4

Updated by Robert Heel over 14 years ago

What is the difference between t3ver_oid and t3_origuid ?
- t3ver_oid isn't configured in TCA.
- t3_origuid isn't deleted when publishing an element.

Created another patch (0014263_translate_draft_v2.diff) using the t3ver_oid field in a different way. Seems that work in more cases.

Actions #5

Updated by Benni Mack about 14 years ago

Could not reproduct this issue in trunk.

Please check if this issue still exists with trunk or 4.4.2, should be fixed since 4.4.1.
I will close this issue if there won't be any feedback soon.

Actions #6

Updated by Robert Heel about 14 years ago

Hi Benjamin,

yes, works here with 4.4.2, too.

Actions

Also available in: Atom PDF