Dynamic Content Not Fully Multilingual (Index Page, Details Page And Custom Fields) - Question | JoomShaper
Back to the questions

Dynamic Content Not Fully Multilingual (Index Page, Details Page And Custom Fields)

R

Remco

SP Page Builder 5 days ago

Hello,

I’m currently working with Dynamic Content in SP Page Builder on a multilingual Joomla website and I’m running into some limitations.

It seems that Dynamic Content is not fully multilingual yet. Could you confirm whether this is expected behaviour?

Specifically:

  1. I cannot create separate Dynamic Content Index Pages per language.
  2. I cannot create separate Dynamic Content Details Pages per language.
  3. Custom Field names within Dynamic Content collections cannot be translated.

Because of this, the index layout, detail layout and filters (based on custom fields) can currently only be configured for one language.

Am I overlooking a setting or workflow that allows Dynamic Content to work properly with Joomla’s multilingual system?

If this is currently not supported, is multilingual support for Dynamic Content planned in a future update?

Kind regards, Remco

0
Website
https://www.idws.nl
1 Answers
Order by
Oldest Newest Votes
Mehtaz Afsana Borsha
Mehtaz Afsana Borsha
Accepted Answer
Support Agent 4 days ago #219520

Hi, thanks for the detailed explanation.

Yes, what you’re experiencing is expected behavior at the moment. The Dynamic Content feature in SP Page Builder does not yet provide full multilingual support within Joomla’s multilingual system. Because of this, it is currently not possible to:

  • Create separate Dynamic Content Index pages per language

  • Create separate Dynamic Content Detail pages per language

  • Translate custom field names within Dynamic Content collections

As a result, the layouts, filters, and field labels are shared and can only be configured in one language.

At this time there isn’t a built-in workflow to manage Dynamic Content fully per language. For multilingual projects, some users work around this by creating separate collections or structures per language, but this depends on the project setup.

We understand that full multilingual support would be a valuable improvement. I will submitting this as a feature request so it can be reviewed by the product management team and considered for a future update.

Thanks again for your feedback.

-Regards.

0