No Code Attached Yet
avatar grantg182
grantg182
11 May 2020

Steps to reproduce the issue

Create a custom tag field, with params as per the documentation.

Here's mine:

<field name="tag" mode="ajax" multiple="false" custom="allow" type="tag" label="My Custom Tag" description="Description of My Custom Tag" hint="Hint of My Custom Tag"/>

Expected result

Admin user can select existing tag, or create a new tag.

Actual result

Admin user can only select an existing tag, there is no option to enter a new tag. If set to multiple="true" then the user can type in the field, which appears to only be doing a search for a matching tag, but of course this is a new tag, so nothing is returned and alas, nothing is saved.

System information (as much as possible)

Joomla 3.9.8.

Additional comments

As per the document linked above, I would expect an admin user to be able to create a new custom tag, but this appears not to be the case. Also same issue mentioned in #28298.

avatar grantg182 grantg182 - open - 11 May 2020
avatar joomla-cms-bot joomla-cms-bot - change - 11 May 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 11 May 2020
avatar grantg182 grantg182 - change - 11 May 2020
The description was changed
avatar grantg182 grantg182 - edited - 11 May 2020
avatar ReLater
ReLater - comment - 11 May 2020

Do I understand correctly?
You have created a custom component and then you integrated the tag features for one or more views like described in the docs.
Then you cannot create a new tag in one of the edit views of this custom component?

Or is your expectation to create a new tag somewhere? See #29015 (comment)

avatar grantg182
grantg182 - comment - 11 May 2020

@ReLater Correct; the tag field has been added into a custom component form XML, just as described in the docs. The tag field appears as an option list, therefore I can select existing tags, save, and the tag selected is saved as expected, but the issue is I cannot create a new tag from here, which the documentation clearly states I should be able to as per here under "Ajax Mode".


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

avatar ReLater
ReLater - comment - 11 May 2020

the tag field has been added into a custom component form XML

And you followed all the other steps, i.e. table fields mapping, new content types in database and so on?

avatar grantg182 grantg182 - change - 11 May 2020
The description was changed
avatar grantg182 grantg182 - edited - 11 May 2020
avatar grantg182
grantg182 - comment - 11 May 2020

@ReLater yes, I believe so. Literally every other form field, custom or not, works...except this tag field. I also updated the Actual result in the OP to make it a bit clearer, I hope.

avatar Quy
Quy - comment - 13 May 2020

Please test PR #29051.

avatar alikon
alikon - comment - 13 May 2020

closing as we have a pr

avatar alikon alikon - close - 13 May 2020
avatar alikon alikon - change - 13 May 2020
Status New Closed
Closed_Date 0000-00-00 00:00:00 2020-05-13 17:01:56
Closed_By alikon
avatar SharkyKZ
SharkyKZ - comment - 13 May 2020

#29051 is not related.

avatar SharkyKZ SharkyKZ - change - 13 May 2020
Status Closed New
Closed_Date 2020-05-13 17:01:56
Closed_By alikon
avatar SharkyKZ SharkyKZ - reopen - 13 May 2020
avatar grantg182
grantg182 - comment - 13 May 2020

#29051 did not look related; and can confirm it made no difference to this issue.

avatar grantg182
grantg182 - comment - 19 May 2020

Another update to this one. It appears custom fields do get added to the field and do get saved if the user physically hits the Enter key. Clicking outside of the tag field does not retain the custom tag, hence it is not saved. Same behaviour experienced on J 3.6.5 and 3.9.8.

avatar Hackwar Hackwar - change - 6 Nov 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-11-06 19:47:53
Closed_By Hackwar
Labels Added: No Code Attached Yet
Removed: ?
avatar Hackwar Hackwar - close - 6 Nov 2022
avatar Hackwar
Hackwar - comment - 6 Nov 2022

I can understand that the behavior is not 100% intuitive, however this is intended behavior, mainly because a tag can consist out of more than one word. Without confirming by hitting the enter key, we wouldn't know if a string with x words is one single tag or x separate ones. So I'm closing this one as expected behavior.

Add a Comment

Login with GitHub to post a comment