Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Probleme with translation of an article built up with content elements #742

Closed
WillyRM opened this issue Sep 25, 2018 · 5 comments
Closed

Comments

@WillyRM
Copy link

WillyRM commented Sep 25, 2018

Bug Report

Hello,

I have built up my news articles using "content elements". When I try to translate this article, the first content element within the article is replaced and linked to any content element on the page.

When I delete this content element, the linked content element is also deleted.

How can I solve the problem? If you need further information, please let me know.

Environment

  • TYPO3 version(s): 8.7.19
  • news version: 7.0.5
  • Is your TYPO3 installation set up with Composer (Composer Mode): no
  • OS: Windows 10
@friggingee
Copy link

Can confirm that this issue exists on T3 8.7.27, tx_news 6.3.0 in composer mode on Linux.
Debugging shows that the DataHandler replaces one of the related content elements with a random ID when translating.
I wasn't able to figure out yet, when and why exactly that happens but right now I'd assume that the issue is most likely related to a core issue with inline elements rather than a tx_news problem.

@friggingee
Copy link

Adding

$GLOBALS['TCA']['tx_news_domain_model_news']['columns']['content_elements']['config']['behaviour'] = [
    'localizeChildrenAtParentLocalization' => true,
];

seems to resolve the issue.

This might actually be a tx_news issue then, after all.

@mindpilot
Copy link

Same here: TYPO3 8.7.29 width tx_news 6.3.0 or tx_news 7.3.1
Adding 'localizeChildrenAtParentLocalization' => true, as suggested by @friggingee solves the problem.

@friggingee
Copy link

Seems to be closely related to https://forge.typo3.org/issues/57272.

In accordance with the discussion and conclusions from that ticket, I'd say that this is not an EXT:news bug after all because fixing this might break working workarounds in other installations.
Also this core bug seems to be solved in v9.

@georgringer
Copy link
Owner

code changed a couple of times, closing issue therefore. feel free to reopen a new one if still relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants