Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007sUdm&sfdc.override=1 project_key: JBEPP When there is an AccessControlException, a stacktrace is logged, however there is no useful information to help identify the root cause of the problem. Proposed change is in attached UIDocumentForm.java : In the java file, the change is marked by comments. The proposed fix is: // RECOMMENDED CHANGE HERE //LOG.error("Unexpected error", e); LOG.error("User Access Error, user [" + userName + "] does not have access to the template for content type [" + contentType + "] in repository + [" + repositoryName + "]"); // END RECOMMENDED CHANGE Exception log also attached.
Attachment: Added: UIDocumentForm.java
Attachment: Added: UIDocumentFormException.log
Related ECMS issue on eXo side: https://jira.exoplatform.org/browse/ECMS-2730
Set Release Notes Not Yet Documented because this issue is a Customer-initiated issue. When the issue is fixed, all issues with Helpdesk ticket references *must* have a release note provided, and included in the Release Notes document.
Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: CAUSE: CONSEQUENCE: FIX: RESULT:
Closing, at this issue was resolved in WCM 2.3.3 through https://jira.exoplatform.org/browse/ECMS-2730. Verified that this is making it into EPP 5.2.0 SitePublisher.
Release Notes Text: Removed: CAUSE: CONSEQUENCE: FIX: RESULT: Added: CAUSE: When an AccessControlException occurred, a stacktrace was logged, however there was no useful information to help identify the root cause of the problem. CONSEQUENCE: It was not possible from the exception to identify the root cause of the problem. FIX: The error message of the thrown AccessControlException was improved to contain detais about the cause of the problem. RESULT:
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Removed: CAUSE: When an AccessControlException occurred, a stacktrace was logged, however there was no useful information to help identify the root cause of the problem. CONSEQUENCE: It was not possible from the exception to identify the root cause of the problem. FIX: The error message of the thrown AccessControlException was improved to contain detais about the cause of the problem. RESULT: Added: When an AccessControlException occurred, a stacktrace was logged, however there was no useful information to help identify the root cause of the problem. It was not possible to identify the root cause of the problem from the exception. The AccessControlException now contains details about the cause of the problem.