Glossary ID has to be added in typoscript

[tw-wolfgang]

We discovered that glossaries only work if the ID is added in typoscript (like described in https://docs.typo3.org/p/dmitryd/dd-deepl/12.7/en-us/Configuration/TypoScriptReference/Setup.html). The solution works fine, but makes it very uncomfortable to "edit" glossaries. As deepl allows no editing of glossaries, every "editing" means to remove the existing glossary and upload a new one. This leads to an new ID which then forces you to edit the typoscript. While editing glossaries is a task that every editor should be able to do, editing typoscript is definitly not. So in the current state there is no effective way for editors to update glossaries.

Deepl suggest to use the name as identifier for "editing" glossaries (https://developers.deepl.com/docs/api-reference/glossaries). Could this also be an option here? Would be nice if you could also use the name as an identifier, as it can stay the same after every upload.

[kauz56]

@tw-wolfgang Check these: https://github.com/kauz56/dd_deepl/commit/76ebd90e55b9255e6067a3f22f708921a02048b7 https://github.com/kauz56/dd_deepl/commit/e576ac9d312520f338b7d376d02e622e007d22fa

I believe these solve your issue, without introducing a breaking change.

Firstly we autodetect the first matching glossary (by lang pair) directly from the API, circumventing the need to define glossaries in typoscript. Secondly we add a "Replace glossary" button. The ID will still change, but the autodetection makes this a non issue. The only case where this doesn't work is when you have multiple page trees with differing glossaries, which I would say is likely an edge case.

[tw-wolfgang]

@kauz56 thank you, works just fine! This makes using the glossaries much smoother. Only thing we had to do to make it work was to rewrite

$glossary = $this->glossaries[$key] to $glossary = $this->glossaries[$key] ?? null;

in order to avoid following error: