FEATURE: Support for glossaries #63
Merged
Conversation
This file contains hidden or 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
Glossaries are created and uploaded to DeepL via the Lost in Translation Backend Module.
When node-translations are created the matching glossary for the language combination at hand
is chosen automatically.
Glossary names are internally prefixed with a configurable identifier that ensures that different Neos instances
that share a DeepL account will not interfere by cleaning up each others glossaries.
By default the prefix is the `FLOW_CONTEXT` as this is already configured in all Neos Instances and is often used to
seperate multiple environments.
**:warning: If you use multiple environments with the same FLOW_CONTEXT and DeepL Account you should ensure that the
glossaryLabelPrefix is configured differently for each environment.**
```yaml
Sitegeist:
LostInTranslation:
DeepLApi:
#
# The label prefix can be used to prevent different instances overwriting or deleting each others
# glossaries. The default value is the FLOW_CONTEXT but this may need adjustment based on your use case
#
glossaryLabelPrefix: '%env:FLOW_CONTEXT%'
```
The commands `./flow glossary:uploadall` and `./flow glossary:cleanupall` allow to automate those tasks and may
be integrated in backup and restore or synchronization scripts.
This was referenced Jun 27, 2025
mficzel
force-pushed
the
feature/glossarySupport
branch
from
4863b25 to
5e2ae39
Compare
mficzel
force-pushed
the
feature/glossarySupport
branch
from
80a0079 to
3a76337
Compare
| /** | ||
| * @phpstan-var Collection<int, GlossaryEntry> | ||
| * @var Collection<GlossaryEntry> | ||
| * @ORM\OneToMany(targetEntity="Sitegeist\LostInTranslation\Domain\Model\GlossaryEntry", mappedBy="glossary", cascade={"persist"}) |
There was a problem hiding this comment.
I think we are missing cascade={"all"} here. This is why, after updating a glossary entry, it would still show the old content.
There was a problem hiding this comment.
hmmm ... i would expect cascade=persist to have this effect. Is that wrong?
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.
Glossaries are created and uploaded to DeepL via the Lost in Translation Backend Module. When node-translations are created the matching glossary for the language combination at hand is chosen automatically.
Glossary names are internally prefixed with a configurable identifier that ensures that different Neos instances that share a DeepL account will not interfere by cleaning up each others glossaries.
By default the prefix is the
FLOW_CONTEXTas this is already configured in all Neos Instances and is often used to seperate multiple environments.The commands
./flow glossary:uploadalland./flow glossary:cleanupallallow to automate those tasks and may be integrated in backup and restore or synchronization scripts.resolves: #5