[ALGSRCHFDR-2] Handle I18N attributes in a better way Created: 27/Jun/22 Updated: 12/Dec/22 Resolved: 09/Dec/22 |
|
| Status: | Closed |
| Project: | Algolia Search Index Feeder - CLOSED |
| Component/s: | None |
| Affects Version/s: | 1.0.4 |
| Fix Version/s: | 1.1.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Raphael Falvo | Assignee: | Yen Lac Tue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| Template: | |
| Acceptance criteria: |
Empty
|
| Description |
|
Description The current version of the module allows the synchronization of magnolia attributes based on a list. If the site handles several languages, and if translated fields need to be sent in Algolia, the different attributes storing the other languages would also have to be listed within the configuration. It would be nice to define the attribute only once, do a check for every field if a translation exists in the defined other languages, and export the attribute if the translation exists.
Hints I118N node wrapper: https://www.tabnine.com/web/assistant/code/rs/5c65775d1095a5000153957e#L143 |