[BUGFIX] Determine glossary correct on current page #271
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
Until TYPO3 v10, the page ID in requests is given as `pageId` instead of `id`. This bugfix respects the given request and detects correct page ID in DeeplBackendUtility for determining glossary. Backport to v4 not necessary, as since TYPO3 v11 the ID is given as `id`
NarkNiro
approved these changes
May 26, 2023
NarkNiro
approved these changes
May 26, 2023
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.
Until TYPO3 v10, the page ID in requests is given as
pageIdinstead ofid. This bugfix respects the given request and detects correct page IDin DeeplBackendUtility for determining glossary.
Backport to v4 not necessary, as since TYPO3 v11 the ID is given as
idcloses #238