To make use of the standard aio endpoint authentication you would likely need to implement the full oauth token generation process in your codebase, taking your client key etc and using the token API to convert this into a token.  You could potentially cache this for a period of time to avoid every ...

I would recommend ensuring this is logged as a support case via https://adminconsole.adobe.com/ - if you don't  have access or you don't see the "support" option at the top, you may need to talk to an administrator of your account to find someone with the "Support Admin" role who would be able to ac...

It sounds like you have quite a complex use case, so it's hard to give a definitive recommendation.  It seems unlikely that the event handlers themselves would get modified to trigger post DOM update. One potential work around might be to have the afteredit event listener add a mutation observer on ...

I've done a quick test of triggering an alert in an afteredit listener and it's visible that the event fires before the DOM is modified. In the below the Experience Fragment was previously the full width and I resized it smaller - the alert from the listener fires and only after you click ok does th...

Are you able to share the full stack trace of the error in the logs? Does the same happen if you pre-create the destination folder before installing the package? from the above it appears to relate to the import creating the folders to enable it to place content deeper in the tree.  Can you check in...

oops - posted the above from the wrong account. Martin

Are you able to compare the properties you see on your page and a we.retail page after creation based on the editable template?  wondering if you template is adding some properties which are causing the inheritance to to work differently.

is the content also missing from the repo structure if you look at the page in crx/de?are you running the latest service pack, and does the same happen with 6.5.0 with no SPs installed?