Skip to content

Conversation

@leonhelmus
Copy link

By moving the columns overview_page_id / overview_page_image we can define this on store level which allows multi store language support.

By moving the columns overview_page_id / overview_page_image we can define this on store level which allows multi store language support.
@ahuininga-orisha
Copy link
Collaborator

@leonhelmus So instead of making the overview pages itself multi language. This pull requests makes it possible to make multiple overview pages and select an different overview page per storeview for an landingpage. Do i understand it correctly?

I'll discuss this internally to see if this is the solution we want, or if we want to make the overview pages itself multi language.

@leonhelmus
Copy link
Author

leonhelmus commented Jun 17, 2025

@ah-net the other solution would also be nice, but this one costed me the lowest effort.

And yes you are understanding me correctly 😁

@ahuininga-orisha
Copy link
Collaborator

@leonhelmus We would prefer the another solution which makes the overview pages itself multilanguage. We've added this to our backlog. But feel free to make an pull request of this if you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants