Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

Unable to move components inherited from core components after latest sdk update

Avatar

Level 2

Greetings,

We have a few custom components that inherit directly from aem core components, and recently in on of the latest sdk updates "aem-sdk-2025.3.20133.20250325T063357Z-250300", this components have become unable to be clicked and dragged, in order to move them around in the page.

 

We are not sure on how to fix this issue, here is the content.xml of a couple of this components

DanielMa63_0-1744620846228.png

DanielMa63_1-1744620918667.png

Any guidance you can provide on how to solve this will be appreciated it

Thanks in Advance

 

Best Regards,

Daniel

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Your problem is not with .content.xml. When you click and drag, there is browser / server error thrown. Please provide the HAR and error.log when issue happens. General checklist

  1. In your parent pom.xml, did you update aem.sdk.api version to match to your server?
  2. <aem.sdk.api>2025.3.20133.20250325T063357Z-250300</aem.sdk.api>

     

  3. Expecting build to fail or buildlog to hint incase your custom proxy component is using any deprecated features. 

  4.  Make sure to update core.wcm.components.version to latest 

    <core.wcm.components.version>2.23.4</core.wcm.components.version>

Providing some error logs can help to troubleshoot. 

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Your problem is not with .content.xml. When you click and drag, there is browser / server error thrown. Please provide the HAR and error.log when issue happens. General checklist

  1. In your parent pom.xml, did you update aem.sdk.api version to match to your server?
  2. <aem.sdk.api>2025.3.20133.20250325T063357Z-250300</aem.sdk.api>

     

  3. Expecting build to fail or buildlog to hint incase your custom proxy component is using any deprecated features. 

  4.  Make sure to update core.wcm.components.version to latest 

    <core.wcm.components.version>2.23.4</core.wcm.components.version>

Providing some error logs can help to troubleshoot. 

Avatar

Level 2

I have tried updating what you mention in the project pom, but no luck
Here is the error is giving in browser

DanielMa63_1-1744645563748.png

Unsure on how to get the HAR file since it is not a network error, no related error seems to be appearing in the error log from AEM

Avatar

Level 2

Here is the aem error log, just in case there is something im missing

Avatar

Level 2

The issue seems resolved after the latest sdk update.

Thanks anyway for taking the time to look at our issue and try to help.

Best Regards.

Daniel