Feature proposal #3751
closed
Add language specific viewing support in CB
100%
Description
As Joomla 2.5+ supports language specific content, I think its a great idea to add such support in CB also.
E.g., A tab can be published for All languages or a specific language and will be rendered based on the current language of the site.
Relevant thread here:
https://www.joomlapolis.com/forum/154-advanced-members-support/207368-language-specific-tabs?limit=6&start=6
Updated by nant over 13 years ago
- Subject changed from Add language specific support in CB to Add language specific viewing support in CB
Updated by beat over 13 years ago
When implementing this feature, we could also implement it this way:
1) add language to CB substitutions, so they are usable everywhere (This could be a field-type plugin)
2) add possibility to have a visibility condition based on cb substitutions (This could be a conditional-fields-tabs plugin)
Which opens doors to unlimited conditions for tabs. I think, given the not often request of language-specific tabs, this would be much more broad-reaching.
Updated by krileon almost 13 years ago
- Target version set to CB 2.1
Updated by krileon almost 10 years ago
- Status changed from New to Feedback
This is doable with CB Conditional. Don't see much need for this to be implemented into core CB.
Updated by nant almost 10 years ago
krileon wrote:
This is doable with CB Conditional. Don't see much need for this to be implemented into core CB.
I disagree - this is a core feature in Joomla and it should be in CB
Updated by krileon over 9 years ago
- Target version changed from CB 2.1 to CB 3.0
Don't see how we could do this without a significant rewrite to field and tab queries. I have no idea what this would break in addition to slowing those queries for a vast majority that'd never use this. I'd say it needs to wait for when we rewrite the fieldClass and put it into a new CBLib class instead of extending the already ancient codebase for fields. So it'd need to be done on a major release like 3.0.
For now the workaround can be to use CB Conditional until then.