Tags should go through JTEXT

I noticed that the tags do not go through JTEXT. Would it be possible to add this?

Hello,

yes very much possible and easy to modify tags cloud module and field display

but what about item form ?
(we do autocomplete text search)

"autocomplete text search" is also very disputable in respects to usability. With "autocomplete" an author needs to know which tags are available to use them, which is impossible if multiple authors work on the site with 100+ tags in the pot. So he needs to go to the tags table each time he wants to know if a tag or a similar(!) one already exists. An alphabetically ordered dropdown would be a lot easier to use.

And of course the dropdown must contain the translation of the tags for the language the site or admin currently runs in.

Hello

let's discuss this

-- our approach since J1.5 was to use Joomfish to translate tags, and in J2.5/J3.1 we use Falang
(just care must be taken to add tags only in the default language and then translate the tags with falang)

... this makes possible the text autocomplete to display appropriately translated tags to the frontend authors,
because the SQL query will return translated text due to being altered by Falang (/Joomfish in J1.5)

if we do what you ask you(/we will loose this capability for autocomplete searching of tags)

-- also your tags planning may involve that only admin adds tags, and the author only use it and cannot create (use FLEXIcontent component ACL rule to control this)

just, i am thinking that backend indexer may not be inserting translated tag text in the index, so it needs to be updated to query falang table

Regards

I use the Joomla/FLEXIcontent native Item Translations. So I dont know how Falang would be affected.

I still think a drop down containing all available tags is way more user friendly then making the user guess if a tag already exists or not, e.g. the user wants to add "big" but the admin had "high" in mind ... so the user will never be able to add this tag because he will never find this tag. I would rather loose this "capability for autocomplete searching of tags" (because I favor a drop down) but have the option to use the Joomla native translation via language strings.

"-- also your tags planning may involve that only admin adds tags, and the author only use it and cannot create (use FLEXIcontent component ACL rule to control this)" - that would be very useful!

cheers

hede wrote: "-- also your tags planning may involve that only admin adds tags, and the author only use it and cannot create (use FLEXIcontent component ACL rule to control this)" - that would be very useful!

Hello,

i meant this ALREADY exists in component permission per User group