utilisation de Translation group

haaaaa... i've found the bug... I think..

I suppose that joomla (or flexicontent) use where $row is the result of something like that:
.

en-GB is default site language.

So .. if I've 3language : en-GB and en-US and fr-ca.

The traduction works properly now between fr-ca and en-GB items.
Inside fr-ca i can select my en-GB items.

But when I'm inside the en-US the template said:

"Current content item is the Original Content of the Translation Group"

So my theory is realistic?

and this is a problem of Flexicontent, Joomla or in my head?

after many test,
I've see on the:
/administrator/components/com_flexicontent/views/item/tmpl/default.php

some code like:

and

i can modify this to


also modify parentclassitem.php on model :
to
So, I should be modify others models and view but i don't know them.

Please do not make these changes, these code should not be modified.

I missed the forum post above that you mention WHY you are doing this?

ALSO note the item Language ALL cannot be associated with any other language, because it is meant for ALL languages, this is standard J2.5 behavior too, for e.g. menu items, modules, etc

So if you have a content that you want to associate with other items then set it not to have language ALL, but set it the correct language e.g. English, then you can associate it with other items

humm..

for example my website have many english language:

english canada
english usa
english UK

And many french language:

french canada
french France

And each of country have many differente content, price, features.

Associated menu works with any language(country).
but not flexicontent..

this is why we need get the "language", not only with 2 first value but all of them.

mmm,
i have thought of exactly this need before, now it has appeared in your site,
just this was not supported in J1.5 100% , plus one or two other reason, i decided not to support it yet

if you want to make tests with this,
go ahead,
but to support this, many files must be changed

at least, recent versions has unified retrieving the language code, and other language data,
inside file
components/com_flexicontent/classes/flexicontent.helper.php,

so it will be easier to support this in the future

if it is not important maybe avoid/postponing do this?

This may be of interest:

IN r1469:
+ Added 2 new ACL privileges:

(a) Edit field value ACL permission e.g. for subscription sites, where specific fields are editable by some user groups only

(b) Associate any translation ACL permission, for site that have different
authors per language