Fixed. The reason was that 2 identical services were registered. After turning off (deleting) everything worked fine. Thanks to all.

Sorry, I missed in the message. I have annotation in class @component(service = CustomErrorHandlerService.class, immediate = true)

Hello, community. I'm trying to change the standard error handler along the path /libs/sling/servlet/errorhandler. I also created a service and an implementation for it to use the configuration. In default.jsp I added import com.custom.aem.common.errorhandler.CustomErrorHandlerService <%@page sessio...

Thanks all for your help. I fixed this issue. The problem was that in our class we were receiving an invalid resource from a request to delete a component.It was enough to change fromResource resource = request.getResource();toResource resource = context.getRequest().getResource();in extended Conten...

No I didn't. But this issue triggired on all custom components.

One note. I see 500 request error in the POST delete request. 

 

HelloCould you please tell me with such an error that appeared after applying the service package +6.5.4?When deleting a component in author we're getting an error message (see attached image). The component also stays on the page until we do a manual refresh of the page. Deleting a component delete...

I am performing a component removal on a web server on the author. Steps to reproduce:Add a component to the pageDelete itNotice the error message at the top of the pageNotice the component isn't deletedRefresh the pageNotice the component is deleted.But in the CRX can see that the component has bee...

No, nothing like that. This message appears for any component and appeared after the version update from 6.5.6 to 6.5.8.