Skip to content
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

Closed
x0rsw1tch opened this issue Feb 27, 2024 · 5 comments · Fixed by #30664 or #30746
Closed

Category fields generating JavaScript error in browser console #27749

x0rsw1tch opened this issue Feb 27, 2024 · 5 comments · Fixed by #30664 or #30746

Comments

@x0rsw1tch
Copy link

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.

image

Cheers!

Steps to Reproduce

  1. Create a content type
  2. Add a category field to the content type
  3. Create a new contentlet of the new content type
  4. Open browser console, see error(s)

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

Copy link

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.

@github-actions github-actions bot added the stale label May 28, 2024
@erickgonzalez
Copy link
Contributor

Still reproducible in version 24.05.20.

Copy link

@erickgonzalez
Copy link
Contributor

Needs work, still getting the error in the console:

Screenshot 2024-11-20 at 3 23 41 PM

@erickgonzalez erickgonzalez reopened this Nov 20, 2024
@github-project-automation 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 github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Nov 26, 2024
@erickgonzalez
Copy link
Contributor

Working as it should now we're not getting any error on the console.

Tested Adding/Deleting categories to content.

@erickgonzalez erickgonzalez moved this from Internal QA to Done in dotCMS - Product Planning Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment