dotCMS / dotCMS/core

[DEFECT] Unhandled error when opening locked Menu Link.

Open
#33,930 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

When opening a locked menu link on a user that did not lock menu link provides the following error.

An unexpected system error occurred. com.dotcms.repackage.javax.portlet.PortletException

https://dotcms.freshdesk.com/a/tickets/34320

Steps to Reproduce

https://github.com/user-attachments/assets/ecd5bae1-b334-4d30-9546-bf4f7a7f574d

In an environment with demo data.

  1. Go to the Browser Portlet.
  2. Select the + button.
  3. Select Menu Link
  4. Generate a test Menu Link
  5. Click Save And Publish
  6. Edit the newly created Menu Link
  7. Go back to the Browser portlet using the menu instead of clicking Cancel, Save and Publish or Save.
  8. Sign in as a different user
  9. Try editting the locked Menu link.
Acceptance Criteria

Either of the two options.

  • Remove the lock when navigating away from the Menu link edit screen in any fashion.
  • Improve the error screen mentioning that the menu link is locked
dotCMS Version

25.11.20-01

Severity

Medium - Some functionality impacted

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Browser Portlet and reproduce the locked Menu Link flow using the listed steps, including navigating away and signing in as another user. Trace where the PortletException reaches the error screen. Done means either leaving the edit screen releases the lock or the error clearly tells users that the Menu Link is locked.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.