We have custom implementation to find the pages / assets which do not have jcr:content. It was working fine AEM 6.0 version but we are migrating to AEM 6,3 now and we are facing the below error when we open the pageError during include of component '/apps/misc-tools/components/missingNode'Error Mess...

When I cheked with one of my collegue who is also using AEM 6.3 CFP2 he doesn't see index value added at the end of node name. My instance is AEM 6.3 SP1 CFP1.

We are using the above line of code to add an index dynamically to the names for tabs, for example, written_by0, written_by1, and written_by2 in order to avoid duplication of the same node and so on. This did not work in our 6.1 environments so we just had dialog validation restricting authors to av...

Yes the above code doesn't add index values to node in 6.3 but nor in 6.1

Hi,We have a component where for creating multiple tabs on the page which has code snippet as below.<div data-sly-resource="${tab.token @ format=[itemList.index], resourceType='foundation/components/parsys'}"></div>The "tab.token" will be a value that we give in the component dialog as tab name, for...

Hey Kiran,We also have installed SP1 in our AEM 6.3 instance and not facing any issue accessing the URL: <<HOST>>/mnt/overlay/dam/gui/content/assetsrouter.html it redirects to this URL:<<HOST>>/assets.html/content/dam.Try it on a fresh instance and if its reproducible.Thanks,Prem

Can you add the screenshot of complete node structure of the launch you are trying to delete?

Yes, I raised a support ticket. This is acknowledged as product bug and fix is included in AEM 6.3 SP1 CFP1 which might release in late November.Adobe provided a workaround for this :- Go to http://host:port/system/console/components- Look for com.adobe.granite.comments.internal.CommentReplicationCo...

You can install SP1 not an issue. But anyway try on your local dev environments first and if it works fine you do the same on your main servers.

Hi Jeroen,I think this issue is resolved in AEM 6.3 SP 1. Can you install SP1 and see if this solves the issue. Please have a glance at the release notes for AEM 6.3 SP1  6.3 Service Pack 1 Release Notes.Thanks,Prem