Tag assignment does not allow to enter a tag name in frontend

kondrich

Hi,

we are facing an annoying issue in article editor when we want to assign tags to articles (in German, tags are "Schlagwörter"). It does not allow to enter a tag name. It just presents a scrollable list of tags.

As a consequence, users in the Publisher role (no backend access) can't assign tags. This can be done in backend only.

I compared the frontend article editor with another site running the default Cassiopeia template. It's possible to enter tag names there:

I also verified this on our test site without active JCH Optimize to see if it's some kind of CSS or JS optimization issue, but it's the same as on the production site: Tag names can't be entered.

Do you have any ideas if this is a T4 Framework issue? Or a JA Flix template isue? Or what else?

Kind regards,
Klaus

saguaros

Hi Klaus,

It relates to the style for T4 frontend edit layout.

I copied the based file from T4 core folder and paste into the local folder in template: \templates\ja_flix\local\css\frontend-edit.css

Updated:

.t4-edit-layout joomla-field-fancy-select .choices__inner .choices__input--cloned {
  display: block !important;
}

/*
.t4-edit-layout joomla-field-fancy-select {
  display: block;
  max-width: 300px;
}
*/

Kindly check.

kondrich

Hi,

Thank you very much.

Is this considered to be a bug in T4? I am wondering if we are the only ones noticing this.

Do we have to care about this local file during T4 and/or template updates? Will it create update problems or additional efforts?

saguaros

I will forward to T4 team for further consideration to update.

And all the files added into this local folder will not be affected when you update new version of template or T4 plugin 🙂

kondrich

Thank you for forwarding this.
Then I am really surprised that nobody else noticed it until now (however my people pushed this too me very late. I am always using the backend where everything is working).

Yes, I understand that this local folder is not affected by updates. But I meant the other way round: Those local files will never get an update and might conflict/override new good versions.

saguaros

kondrich Hi

I understand your concern, but such conflicts typically arise with layout or PHP files rather than CSS rules like this. I believe it should be fine. 🙂