User tests: Successful: Unsuccessful:
Display the params correctly
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Category | ⇒ | Front End Plugins |
Status | New | ⇒ | Pending |
There is actually a reason why no = green, it's the better state but I understand that it is confusing.
In which case I would suggest that yes/no are the wrong terms to use
hmm, what would be a better suggestion?
active / disabled?
or a selectbox?
There are two different things. What is the state and what is the recommendation.
I would probably go for enabled/disabled for the label and update the description string to explain the recommended state. Of course when you could actually see the descriptions without the stupid button it was much easier.
From what I understand you were using the color green to indicate the recommendation? That was an accessibility failure as you shouldnt use color alone
I'm happy for any improvement.
Description could (always) be something like:
If you use extensions which are not using the latest Joomla Coding standard they might need this setting to work.
or
If the website uses extensions which needs the legacy layer to work they might need this settings to work.
don't know if any of this is good or bad. But Explaining to the end user where the problem is is pretty useless I think since he or she can't fix it anyway. But can the developer "Hey your extension needs this b/c plugin can you bring it uptodate?"
Category | Front End Plugins | ⇒ | Administration Language & Strings Front End Plugins |
Labels |
Added:
PR-5.0-dev
|
Labels |
Added:
Language Change
|
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-07-24 19:03:11 |
Closed_By | ⇒ | HLeithner |
thanks
thank you
There is actually a reason why no = green, it's the better state but I understand that it is confusing.