Content deleted from authoring instance even when deletion from public
instance(s) fails
----------------------------------------------------------------------------------------
Key: MAGNOLIA-3250
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3250
Project: Magnolia
Issue Type: Bug
Components: activation
Affects Versions: 4.3.2
Reporter: Arjan van Bentem
Assignee: Philipp Bärfuss
Deletion (and deactivation) seems to rely on the user credentials on the
authoring instance and the public instance(s) to be the same. If authentication
on the public instance(s) fails, then deletion will fail with an HTTP 401. The
editor is shown an error message.
However: even when deletion has actually failed, the content is still deleted
from the authoring instance. One needs to log in to each public instance to fix
this.
Example error message (same message for normal deactivation, and for
deactivation triggered by deletion):
Can't deactivate: : 2 errors detected:
Not able to send the deactivation request
[http://<primary-server>:8080/.magnolia/activation]: Server returned HTTP
response code: 401 for URL: http://<primary-server>:8080/.magnolia/activation
on <primary node name>
Not able to send the deactivation request
[http://<secondary-server>:8080/.magnolia/activation]: Server returned HTTP
response code: 401 for URL: http://<secondary-server>:8080/.magnolia/activation
on <secondary node name>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
