-
Notifications
You must be signed in to change notification settings - Fork 466
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
Issues/invalid characters in the exported packages list causes system bundles to no longer load #29899
Labels
Comments
I know may be out of the gardening day scope, but will take advance I have a day to concentrate on this |
jdotcms
added a commit
that referenced
this issue
Sep 6, 2024
jdotcms
added a commit
that referenced
this issue
Sep 6, 2024
jdotcms
added a commit
that referenced
this issue
Sep 6, 2024
jdotcms
added a commit
that referenced
this issue
Sep 6, 2024
jdotcms
added a commit
that referenced
this issue
Sep 7, 2024
jdotcms
added a commit
that referenced
this issue
Sep 7, 2024
jdotcms
added a commit
that referenced
this issue
Sep 9, 2024
jdotcms
added a commit
that referenced
this issue
Sep 9, 2024
erickgonzalez
added
the
Next LTS Release
Shortlisted of issues that will be included in the upcoming LTS
label
Oct 1, 2024
erickgonzalez
removed
LTS : Next
Ticket that will be added to LTS
Next LTS Release
Shortlisted of issues that will be included in the upcoming LTS
labels
Oct 21, 2024
It can't be backported because OSGIResource doesn't exist in LTSs. |
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
When there are invalid characters/issues with the exported packages listed in the Plugins portlet, system bundles stop loading as well as any uploaded plugins
Steps to Reproduce
It will look like this:
Many of the System bundles are in an 'Installed' state
Acceptance Criteria
Invalid exported packages should not cause system bundles to stop populating
Invalid exported packages list should be able to self resolve by resetting when encountering an error and reprocessing exported packages on deployed bundles
dotCMS Version
Current, all LTS versions
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
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: