HelloGot a problem after upgrading ai from 6.5.14 to 6.5.15. Prior to this, the component worked without problems, but after the upgrade, it began to work incorrectly. The component does not work correctly only on the publish node.   As I understand it, different types of resources are returned, but...

This message appears due to the fact that the entered data is created under /etc/tags and not in the image metadata under /jcr:content. With the rights everything is fine, I'm as an administrator.

We use several environments and on some, we encountered this error and on others, we didn't. But on all these environments the same code is used.

Yes. Its assets properties. I use extra tag property.

Hello. I ran into a problem that after accepting the 6.5.13 service pack, I encounter an error when saving changes to the tags in the image properties.   After research, I found that a change was made to the render for the field tag. In AEM SP 6.5.12 for (String value : values) { com.da...

We are using Nginx + varnish. Configuration didn't change after upgrade.

HelloCould you please help with a question? There is a component with tag <esi:include src="${model.url}"> and it stopped working in the new version of AEM (6.5.6). After updating from 6.3 to 6.5.6, I began to receive an error 500. Dispatcher configuration files didn't change. Could you tell me what...

Yes, it works, but one point - it works if you use JUnit 5 (io.wcm.testing.aem-mock.junit5). I have a lot of tests on JUnit 4 and I can not migrate from JUnit 4 to JUnit 5. 

I use AemContext and load JSON with content fragment template and I use resource resolver from AemContext this.context.resourceResolver()

Hello.Could you please tell me how to properly adapt the Resource to the ContentFragment in the tests. Since I do, I get null all the time, but the resource content fragment is not null. And in the class for which the test is written, adaptation works correctly.