To be more precise there is no need to completely uninstall and remove the ACS AEM Commons 4.7.2 packages. The cause of the issue was narrowed down to conflict with the AEM Environment Indicator settings for the Browser Title (which is part of the ACS AEM Commons). The simple fix in our environment(...

Thanks to everyone that replied to my question in the post above.   Here is what we believe is the root cause for this issue in our environment. There is some type of incompatibility or regression issue between the last SP14 packages and ACS AEM Commons version 4.7.2. This is the version we have on ...

Hi @Pulkit_Jain_  Thanks for your reply and for trying to help with this issue. It is affecting all XDP forms in our case and we have not attached any forms to the ticket (Case ID: E-000744597). Case Title: XDP forms problem with render as HTML format We have installed the following packages in the ...

It does happens with all of the XDPs... FYI I was able to “trick” the AEM and to load and render a XDP form if I manually edit the URL and add this ‘?type=xdp’ at the end after the 'jcr:content' like in this example: http://devaem:8080/lc/content/dam/formsanddocuments/.../Forms/FormName.xdp/jcr:cont...

Hi @Mayank_Gandhi , We've tried uploading a new xdp via Forms and Documents. It still does not render. It shows the loading graphic spinning eternally. We have also tested with the default profile vs our own rendering profile and still XDP would not load/render. Checking the browser debugging consol...

Yes, this is what I'm told by the form developers testing the instances after the patching.

Has anyone having issues with rendering XDP forms as HTML after installing the latest SP14? We are using on-prem AEM Forms on JEE and after patching our lower env. instances we have this problem: XDP forms are not loading (spinning loading loop circle) or showing 404 errors in different browsers (FF...

Yes, we did open a support case for this issue and that's the only information we got back: This is a product bug and a JIRA CQ-4278157 has been logged to fix this. This should be fixed with the next product release hopefully.

Hello,Has anybody seen this happen after installing the latest patches from Adobe? We just went from 6.5.6 to 6.5.7 on our Stage system and the developers reported that the Verify Component is failing.I know that this is a known issue with some earlier versions but it was resolved and working fine f...