Is there a preferred method for subscribing to AEM version and service pack releases notifications Particularly I'm hoping to be notified when the dispatcher has new releases available.

Since this issue began we have started the upgrade process to 6.5.1. After many weeks of verifying, we have yet to come across the issue with that version.So this is resolved with an upgrade to the latest AEM release.

We are hoping to address CVE -CVE-2019-11358 in the jQuery library provided with AEM.In versions prior to 6.4, we would overlay /libs/clientlibs/granite/jquery and apply security patches based on recommendations from the jQuery team.However, starting with 6.4, the /libs/clientlibs/granite nt:folder ...

I'm coming across a strange issue with AEM Assets in 6.4.Whether I use the Create --> Files option in the ui or drag and drop an image from the local machine into Assets I am seeing the following error:However this is for only 1 asset, if I click Ok, I'm then given:If I select Upload, it presents an...

I figured out the issue,The problem was caused by this line in the XSS policy:<directive name="useXHTML" value="true" /> Per the OSASP documentation, this will output the sanitized data in XHTML format as opposed to just regular HTML:https://www.owasp.org/index.php/AntiSamy_Directives Changing the v...

Hi. Thank you for responding.I'm already overlaying the xss policy configuration, as we have some custom attributes that need to be allowed in certain tags.Note, this does not expose an instance to XSS attacks as the policy is still enforced.When I view the error.log file while loading the page with...

We use the source edit options (misctools) in an overlaid Rich Text Editor component.It works well for the most part, however empty div tags are getting shortened, so:<div class="some-data-class"></div>becomes:<div class="some-data-class" />This is breaking inclusion of dynamic markup via our javasc...

Thank you Guarav!With that in mind we will look into upgrading to 6.4.3.

Hi Anubha and Guarav.According to our Adobe Technical Account Manager, it turns out this issue was supposedly fixed in 6.3.3.0 but it is still a present issue in 6.3.3.1. Perhaps the fix was removed or reverted in SP3 Cumulative Fix Pack 1? He also mentions it is fixed in internal builds of 6.5 but ...

Hi Anubha.May I have an update on this issue?