[MGNLCTS-167] Export Page with no longer existing components Created: 17/Aug/22  Updated: 26/Aug/22

Status: Open
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.5.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Björn Eschle Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File logs.txt    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: AuthorX Support
Team: AuthorX

 Description   

Export translation fails if the definition of the component is removed, but the component still exists on the same page in the website repository.

2022-08-17 08:19:30,739 ERROR tion.ui.action.TranslationFileDownloadDialogAction: An error occurred when executing the command downloadTranslationFile from catalog translation
info.magnolia.config.registry.Registry$NoSuchDefinitionException: gardena-web-core:components/ImageSequence
    at info.magnolia.config.registry.AbstractRegistry.getProvider(AbstractRegistry.java:127) ~[magnolia-configuration-6.2.19.jar:?]
    at info.magnolia.translation.finder.DialogBasedPropertiesToTranslateFinder.determineDialogNames(DialogBasedPropertiesToTranslateFinder.java:117) ~[magnolia-content-translation-2.5.6.jar:?]
    at info.magnolia.translation.finder.BlossomDialogBasedPropertiesToTranslateFinder.determineDialogNames(BlossomDialogBasedPropertiesToTranslateFinder.java:57) ~[magnolia-content-translation-2.5.6.jar:?]
    at info.magnolia.translation.finder.DialogBasedPropertiesToTranslateFinder.getPropertiesToTranslate(DialogBasedPropertiesToTranslateFinder.java:212) ~[magnolia-content-translation-2.5.6.jar:?]
    at info.magnolia.translation.finder.BlossomDialogBasedPropertiesToTranslateFinder.getPropertiesToTranslate(BlossomDialogBasedPropertiesToTranslateFinder.java:69) ~[magnolia-content-translation-2.5.6.jar:?]
    at info.magnolia.translation.finder.AdaptivePropertiesToTranslateFinder.getPropertiesToTranslate(AdaptivePropertiesToTranslateFinder.java:55) ~[magnolia-content-translation-2.5.6.jar:?]
    at info.magnolia.translation.io.ExportVisitor.visit(ExportVisitor.java:95) ~[magnolia-content-translation-2.5.6.jar:?]

 

Steps to reproduce

  1. Create a page and add a component
  2. Either remove the definition of component or export the page and rename the mgnl:template to something else
  3. Try to export the translation

Expected results

If the component doesn't exist the download should proceed and ignore the deleted component.

Actual results

If the component doesn't exist the download of the translation file fails.

Workaround

Run queries to find non existing components and remove them manually in the JCR.

Development notes


Generated at Mon Feb 12 00:33:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.