CMS Made Simple Forums

I'm reconsidering the return of GlobalContentBlock to multilanguage but with a fallback to DEFAULT LANG if is empty (ie is not ready), pre 1.5.4b method

Look here for info

but I want to know your opinions with a poll

Option 1 is current method of 1.5.4b
Option 4 was current method of pre 1.5.4b

Option 2 is same of Option 4 but without fallback
Option 3 is same of Option 4 BUT fallback always if GCB of that language is not ready


[CLEANING TOPIC]

Best regards
Alby

Sorry guys,
I ask to people (6) that voting for option 3 if reconfirm again own vote or if want change in option 4

Alby

sleiron wrote: I'd like to vote on this poll, but don't quite understand the difference between options 3 and 4.

Could you explain that with an example?

In option 3, if GCB of current language is empty then display same GCB of DEFAULT LANGUAGE (I suppose that is ALWAYS not empty because is your primary language). This means that is always the case independently of your settings.

In option 4, if GCB of current language is empty then display empty. You display relative GCB of DEFAULT LANGUAGE if you set "Show from DEFAULT_LANG if current lang is not ready" option in General Settings. This is same behaviour of Content page, if your language pages are not ready (empty) you FORCE system to display content/title/menu of DEFAULT LANGUAGE page. This means that you must set this option that affects the whole system and not GCB only.
This was the behaviour pre 1.5.4b

I hope to be clear
Alby

I will stay with my vote. All contents should show the default language content as long as the specific content is empty. This avoids empty pages and disturbing visitors. May be a specific phrase like "This content will be translated" or so is added as long as the content is not edited. If such a page should not be shown in the menu, it can be selected from the options

this is all very, but I thought you mentioned in a previous post that the non-multilang of version 1.5.4b had been decided for futeure compatibility with v 2... so now we're back to multilang 1.5.6 and then ? what will happen with v2 ? will we have to undo the multilang GCB feature again ?

maxime wrote: this is all very, but I thought you mentioned in a previous post that the non-multilang of version 1.5.4b had been decided for futeure compatibility with v 2... so now we're back to multilang 1.5.6 and then ? what will happen with v2 ? will we have to undo the multilang GCB feature again ?

2.0 is still far and specifications are not all defined.
That is why I asked Ted what "could be" and his answer is 3 but I wanted to hear you also because many feedback from MLE could be included in 2.0 (for example extended that now is default).

Alby