-
Notifications
You must be signed in to change notification settings - Fork 9
Respect multiple languages #25
Comments
@martinhummer is currently implementing multi language support. The only thing we need to change is to provide the field We should remove this part and put this logic to configuration with The language implementation can be found at: https://github.com/martinhummer/search_algolia/blob/master/Classes/Service/RelationResolver.php As each record has a different In addition |
Fetch sys_language_uid from database. Relates: #25
Fetch sys_language_uid from database. Relates: #25
Fetch sys_language_uid from database. Relates: #25
Fetch sys_language_uid from database. Until now we did not fetch system related fields from database. As there is now a RemoveProcessor, integrators are able to remove fields. Also providing this field enables basic multi language support. Relates: #25
Fetch sys_language_uid from database. Until now we did not fetch system related fields from database. As there is now a RemoveProcessor, integrators are able to remove fields. Also providing this field enables basic multi language support. Relates: #25
Fetch sys_language_uid from database. Until now we did not fetch system related fields from database. As there is now a RemoveProcessor, integrators are able to remove fields. Also providing this field enables basic multi language support. Relates: #25
Currently it's not tested. We have to add necessary tests and adjust the code to respect multiple languages for pages #24 and everything else.
Pages are special as they have a different language handling. Perhaps there is already a way provided by the TYPO3 Core to handle everything the same way.
The text was updated successfully, but these errors were encountered: