James Raynor created SLING-10739:
------------------------------------
Summary: Unable to uninstall or upgrade Composum bundle
Key: SLING-10739
URL: https://issues.apache.org/jira/browse/SLING-10739
Project: Sling
Issue Type: Bug
Components: App CMS
Affects Versions: App CMS 1.0.4
Reporter: James Raynor
Attachments: 1.png
Updated to Composum latest version 2.6.6 today, solved the problem SLING-10703:
Unable to adjust the order of permissions
https://issues.apache.org/jira/browse/SLING-10703
Perhaps this is caused by an upgrade of the Sling framework and incompatibility
with older versions of Composum.
Removed and installed:
composum-nodes-commons-2.6.6.jar
composum-nodes-console-2.6.6.jar
composum-nodes-jslibs-2.6.6.jar
composum-nodes-pckgmgr-2.6.6.jar
However, the Composum tools website recommends rebooting after the update, and
once rebooted all system settings ( Apache Sling Login Admin Whitelist
Configuration Fragment ) and bundles revert back, so perhaps the developer
needs to change the startup configuration in the source code.
Currently there is a different method, which is to click the update button to
the left of the uninstall button to update one bundle at a time.
However, the "Apache Sling Login Admin Whitelist Configuration Fragment"
settings are still overwritten after a reboot, so it doesn't work properly.
The uninstallation of Composum bundles in old SlingCMS 0.16.0 worked fine and
solved the problem of not being able to adjust the order of permissions in
version 0.16.0 without any problems.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
