No Code Attached Yet Guided Tours
avatar brianteeman
brianteeman
19 Aug 2025

When you have a language string in the description of a Guided Tour or Step the value of the string is displayed in a second tinymce editor field.

The second field is set as read only in the xml but that doesnt result in the editor field being disabled. It is still marked as Editable

Image

Visually it is not clear that this second editor is readonly and disabled either.

There is also a js error because of the second instance of tinyMCE #43046

I'm wondering why this field is even an editor field. If it only exist to display the value of a language string then surely it would be better as a simple textarea field.

Image

Before I create a PR to fix this could the guided tours team please comment. Maybe there is a use case for the second editor field that I have not considered and we need a different solution.

@obuisard

avatar brianteeman brianteeman - open - 19 Aug 2025
avatar joomla-cms-bot joomla-cms-bot - change - 19 Aug 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 19 Aug 2025
avatar brianteeman brianteeman - change - 19 Aug 2025
Title
Guided Tours / Steps readonly description
Guided Tours / Steps readonly description [a11y]
avatar brianteeman brianteeman - edited - 19 Aug 2025
avatar obuisard
obuisard - comment - 19 Aug 2025

Hello Brian @brianteeman.

We agree that the second editor, since disabled, could just be a textarea, as long as we can see the resulting html output (sometimes we will have images like in the 'What's new tours').
We really don't need editor capabilities for the second editor.

That will eliminate the javascript error mentioned and be more clear to the user that the field is not editable.

So I think this solution is a win win.

avatar obuisard obuisard - change - 19 Aug 2025
Labels Added: Guided Tours
avatar obuisard obuisard - labeled - 19 Aug 2025
avatar brianteeman
brianteeman - comment - 19 Aug 2025

We agree that the second editor, since disabled, could just be a textarea, as long as we can see the resulting html output (sometimes we will have images like in the 'What's new tours').

See I knew there was a reason you did it this way. With a textarea field the html markup and images would be displayed as raw code so changing the field type in that way is not a solution.

Add a Comment

Login with GitHub to post a comment