You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently created a new Strapi application using the following command:
npx create-strapi@latest
After setting up the application, I added the tagsinput plugin. While the field functionality works perfectly, I noticed that the label for the field does not appear in the admin interface. This makes it unclear to users what the field represents.
Steps to Reproduce:
Create a new Strapi project using npx create-strapi@latest.
Install the tagsinput plugin as per the documentation.
Add a tagsinput field to a collection.
Navigate to the Content Manager to view or edit the collection with the tagsinput field.
Expected Behavior: The label for the tagsinput field should appear above or beside the field in the admin interface, making it clear to the user what the field is for.
Actual Behavior: The field itself works correctly (tags can be added and managed), but the label is missing.
I recently created a new Strapi application using the following command:
npx create-strapi@latest
After setting up the application, I added the tagsinput plugin. While the field functionality works perfectly, I noticed that the label for the field does not appear in the admin interface. This makes it unclear to users what the field represents.
Steps to Reproduce:
Expected Behavior: The label for the tagsinput field should appear above or beside the field in the admin interface, making it clear to the user what the field is for.
Actual Behavior: The field itself works correctly (tags can be added and managed), but the label is missing.
Additional Information:
Strapi version: 5.7.0
Tagsinput plugin version: strapi-plugin-tagsinput@^2.0.2
Environment: Node.js v20.11.0, Google Chrome
Please let me know if additional information or reproduction steps are needed!
The text was updated successfully, but these errors were encountered: