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

XLIFF Export/Import Support #31

Closed
valentin- opened this issue Jun 30, 2022 · 5 comments
Closed

XLIFF Export/Import Support #31

valentin- opened this issue Jun 30, 2022 · 5 comments
Milestone

Comments

@valentin-
Copy link

Q A
Bug report? yes
Feature request? yes
BC Break report? no
RFC? no

I'm not sure to report this as bug report/feature request or it it's out of scope or even possible.

When exporting data objects using the pimcore XLIFF export, the seo data won't get exported as they are stored in a separate table. A solution would be handy to add the maintained data to the XLIFF export and save them back to the table on import.

@solverat
Copy link
Member

This is currently not possible due to import/export restrictions of pimcore.

I've created an PR for PIMCORE to allow adding custom values to the XLIFF import/export process.

pimcore/pimcore#13604

@solverat solverat added this to the 3.0.0 milestone Nov 21, 2022
@solverat
Copy link
Member

Since the PR has been accepted for 11.x only, this will be available in 3.0.

@valentin-
Copy link
Author

Hi @solverat, do you have plans yet to make the extension Pimcore 11 ready?

Thanks!

@solverat
Copy link
Member

solverat commented Jul 7, 2023

Yes, see #49

@solverat solverat changed the title SEO data for data objects not included at XLIFF export/import XLIFF Export/Import Support Aug 9, 2023
@solverat
Copy link
Member

done with #53

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

No branches or pull requests

2 participants