Joomfish + Flexicontent : and ...

So by naming the new CATEGORY parameter as 'filtercat', the merging of global and category parameters will work as i expected it (the global parameter will be overridden)

Thus the second step that i mentioned of adding some small modification to the model is not needed.

Thanks for replying this. I had not tested and forgotten to add this to as a feature enhancement.

This needs minor modification and is useful.

Regards

I am finishing a new feature in which everything is translated by joomfish, except the items (the items are in translation groups, thus ASSOCIATING together the translations)

-- I have integrated support in the backend items manager for the translation groups,
-- In frontend the flexicontent item id is changed to the id of the translation item for the current language via a system plugin.
-- Creating translation of items is done by a new button in the items manager tab, where you choose to massively create translation of items which will either
(a) import joomfish data
(b) auto translate the new items via google
(c) just copy original text

-- It is mostly done, but then we must consider the drawbacks !!!:

-- The items are different, this how we can have FULL item translation all fields !!!

This means that hits/comments/votes etc are not shared

SO WHAT IS REALLY missing is:

1. adding an ability to get/update some fields from THE MASTER item instead of the ASSOCIATED translated item.
2. marking some fields as untranslated so that they will be always retrieved by the master item.

Will try to include this in v1.5.7, not sure yet ...

ggppdk wrote: I am finishing a new feature in which everything is translated by joomfish, except the items (the items are in translation groups, thus ASSOCIATING together the translations)

-- I have integrated support in the backend items manager for the translation groups,
-- In frontend the flexicontent item id is changed to the id of the translation item for the current language via a system plugin.
-- Creating translation of items is done by a new button in the items manager tab, where you choose to massively create translation of items which will either
(a) import joomfish data
(b) auto translate the new items via google
(c) just copy original text

-- It is mostly done, but then we must consider the drawbacks !!!:

-- The items are different, this how we can have FULL item translation all fields !!!

This means that hits/comments/votes etc are not shared

SO WHAT IS REALLY missing is:

1. adding an ability to get/update some fields from THE MASTER item instead of the ASSOCIATED translated item.
2. marking some fields as untranslated so that they will be always retrieved by the master item.

Will try to include this in v1.5.7, not sure yet ...

Well this sounds great!
When will you release it?

Please it a free componant ... We try to finishe 1.5.6 and 2.0
No time for future sorry ....

micker wrote: Please it a free componant ... We try to finishe 1.5.6 and 2.0
No time for future sorry ....

what ?

I have it working now on a couple of sites, but i need to decide a couple of things, so it will not be in v1.5.6

Also read this for more information:
www.flexicontent.org/documentati ... ntent.html