Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Components not getting removed after giving delete in authoring mode

Avatar

Level 2

I have a page created from an editable template. The editable template does not contain anything apart from an empty parsys.

 

During authoring this page, I have added several components to it. In this, I have a similar component used multiple times on the page.

 

However, one or two components among the list of similar components are not getting removed even after clicking the delete component button in authoring page.

 

This kind of issue is occurring intermittently/randomly across few pages in our project. I couldn't find any specific reason that is causing this issue. 

 

Appreciate ur help on this.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @parthibanselvam ,

 

Do you have any Sling Servlet (bind through resource type) with these components that you are not able to delete? If yes, then just check if you have configured sling servlet extension also in your servlet. because what happens if we just create a resource type servlet without giving extension then it will be invoked on all operations for that component (GET, DELETE, POST, etc).

 

In case of above holds true or false, check error logs, and browser network tab. You must see a non 200 response in network tab for the delete call and something should be logged in logs too.

 

 

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @parthibanselvam ,

 

Do you have any Sling Servlet (bind through resource type) with these components that you are not able to delete? If yes, then just check if you have configured sling servlet extension also in your servlet. because what happens if we just create a resource type servlet without giving extension then it will be invoked on all operations for that component (GET, DELETE, POST, etc).

 

In case of above holds true or false, check error logs, and browser network tab. You must see a non 200 response in network tab for the delete call and something should be logged in logs too.

 

 

Avatar

Community Advisor

Hi,

 

On deletion are there any console errors or unsuccessful network calls? 

Error logs can also indicate if something dependent is stopping the deletion. 

 

Also to be sure you can try to delete the component via component viewer on LHS of the authoring view.

Avatar

Community Advisor

@parthibanselvam  - As you are using Editable templates, so you might have authored in the component in structure page. Can you share the logs while deleting the components. For a workaround you can update the changes from crx/de to avoid any blocker.