This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
lookupTable and languagField / transOrigPointerField does not work correctly #28
Comments
Please add information on scenario, configuration, expectation and actual behavior |
This configuration doesn't translate the news title to non-default language although languageField and transOrigPointerField are configured. What is required is to modify the lookupTable configuration to add
Which doesn't make sense as the languageGetVar is already specified in the pagePath section and it is also not mentioned in the realurl manual I mean maybe that is the expected behaviour but I would expect the languageGetVar to be the one defined in pagePath to be used for lookupTable entries too. Maybe with the possibility to override it but definitely not as requirement. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The check in regards to the languageField is:
languageGetVar is wrong here because it is not part of the lookUpTable configuration but of the general pagePath setting. Simplest check is probably if $this->detectedLanguage >= 0
Might be used somewhere else in the method too.
The text was updated successfully, but these errors were encountered: