Apply exclude to child elements #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issue #45618
Issue #45618
Issue #45618
Issue #45618
This popped up due to a undeleted file reference where the parent element was deleted. Such file references should not exists in first place, but it should not prevent exports eighter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rows of the tables
pagesandtt_contentcan be excluded from export to specific languages (l10nmgr_language_restriction). This change applies those excludes to the child records. This prevents dangling elements (sys_file_reference, IRRE, ...) in export files. It also excludes elements of hidden parents if the setting noHidden is active. If forced source language is used, the exclude settings from the source are respected.Original MR: https://gitlab.com/coderscare/l10nmgr/-/merge_requests/65