-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Category fields generating JavaScript error in browser console #27749
Labels
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Still reproducible in version 24.05.20. |
erickgonzalez
moved this from New
to Current Sprint Backlog
in dotCMS - Product Planning
Oct 28, 2024
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Nov 15, 2024
github-project-automation
bot
moved this from Internal QA
to Current Sprint Backlog
in dotCMS - Product Planning
Nov 20, 2024
gortiz-dotcms
added a commit
that referenced
this issue
Nov 21, 2024
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Nov 26, 2024
Working as it should now we're not getting any error on the console. Tested Adding/Deleting categories to content. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
No response
Problem Statement
Hello!
Looks like simply having a category field generates some JavaScript errors in the browser console. Not sure of the nature of the issue, but very annoying when debugging custom fields or other related problems in the contentlet editor. The number of errors produced is commensurate with the number of category fields.
I was unable to reproduce the error in the editor with any content types that have no category field.
Cheers!
Steps to Reproduce
Acceptance Criteria
No JS errors produced in the browser console when opening the contentlet editor with one or more category fields.
dotCMS Version
Both latest LTS and agile versions are affected, not sure about older LTS versions.
LTS: 23.10.24v4
Agile: 24.02.20
Proposed Objective
Technical User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: