?
avatar JoeJoomla
JoeJoomla
17 Nov 2016

Steps to reproduce the issue

Create tags in Tag Component in multiple languages
Create Articles with tags on a multilingual site
Create Tags - Popular modules for each language and assign to appropriate menu items

Expected result

In the case of a multilingual site, English & French, when you switch between the languages the module should display English tags for the English language and French tags for the French language.

Actual result

In the multilingual site both English and French modules are displaying all tags regardless of the language ignoring the language assignments.

System information (as much as possible)

Joomla 3.6.4
DB version 5.6.33
PHP 5.6.27

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
5.00

avatar JoeJoomla JoeJoomla - open - 17 Nov 2016
avatar infograf768
infograf768 - comment - 17 Nov 2016

com_tags has a specific parameter for that. You have to set it to Current for filtering to work.
screen shot 2016-11-17 at 06 54 27

avatar JoeJoomla
JoeJoomla - comment - 17 Nov 2016

Thank you infograf768,
You are correct, I didn't know about that parameter setting.
Switching to 'Current' does make the tag menu links switch correctly in the module now.
I have an issue with the links, they all give me a 404 but I suppose this is a different issue.

avatar Bakual Bakual - close - 17 Nov 2016
avatar Bakual
Bakual - comment - 17 Nov 2016

Closing as the issue is solved.

avatar Bakual Bakual - close - 17 Nov 2016
avatar Bakual Bakual - change - 17 Nov 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-11-17 15:08:21
Closed_By Bakual
avatar jatitoam
jatitoam - comment - 17 Nov 2016

Hi guys and sorry for insisting on a closed issue.

Joe asked me about this a couple days ago and I really thought it was a bug, and even if there's a way to make it work I still think it's a usability bug since it doesn't work just as the other modules where language filter works out of the box.

Would it be acceptable of I send a PR to make it work like that? Only talking about the language parameter.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12919.

avatar Bakual
Bakual - comment - 17 Nov 2016

It would have to be backward compatible, meaning the behavior has to be the same as today and only optionally do the new behavior.
Since you already can do that optionally, there is probably no point doing a PR.
You cna do one for 4.0 to change behavior.

avatar jatitoam
jatitoam - comment - 17 Nov 2016

I definitely understand backwards behavior, however I need to insist about usability, and I have one last proposal for considering both:

  1. Adding a "Enable language filter" (separate) option
  2. Make it default "no" for current Joomla installations that are just being updated
  3. Make it default "yes" for new Joomla installations
    This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12919.
avatar andrepereiradasilva
andrepereiradasilva - comment - 17 Nov 2016

as @Bakual said PR are welcomed.

  • For 3.x branch (staging) you MUST respect B/C
  • For 4.x branch (4.0-dev) you should try to respect B/C (as possible), but not mandatory
avatar infograf768
infograf768 - comment - 18 Nov 2016

Make it default "no" for current Joomla installations that are just being updated

That would not be B/C

avatar Bakual
Bakual - comment - 18 Nov 2016

Why adding a separate parameter that does exactly the same thing as the "Current" option in the existing parameter?
If you want to make it more intuitive for users, just remove the current parameter for 4.0 and let it always filter by the current language.

avatar jatitoam
jatitoam - comment - 18 Nov 2016

You are right, on a second thought a second parameter will be misleading, I was just assuming that the current one did more than just language filtering.

My point here is that the parameter is very hidden and it's causing a UX issue for the whole com_tags because it behaves totally the opposite way as the other Joomla components and modules.

So if we left the current selection for current installs ("All") - to avoid breaking B/C, and set a new selection for new installs ("Current") at least we could fix the component without having to wait until 4.0.

avatar brianteeman
brianteeman - comment - 18 Nov 2016

Maybe it can be solved by modifying and clarifying the text?

avatar jatitoam
jatitoam - comment - 18 Nov 2016

The text is not so confusing, but the default behavior is (in combination with a very hidden option).
It's not a critical issue I admit, but just a point where we could improve.

Add a Comment

Login with GitHub to post a comment