okay, please upgrade your Java version to 11. That should resolve your problem.Thank you.

Hi @ForrestLi, May I know if this is a recent change after installing a service pack or something?Also, try changing the JAVA version (sometime back this helped me).Thank you.

Hi @PCFrog, I am sorry If I couldn't understand the problem statement here but Is this question regarding Adobe Experience Manager Sites?.If you are mentioning about the properties field of a JCR Node, I don't think that you would be able to wrap the value of the filed.If it is regarding a field on ...

The pages are loading fine. If you are using any VPN, please check the settings.

I observed these warnings today while starting my instance and I am curious to know what are these, can someone throw some light?Thank you.

Same issue was discussed on this thread and seems like there is a solution. Please refer this if it helps :https://githubmemory.com/repo/Netcentric/accesscontroltool/issues/529 

Hi @Art_Bird , Firstly, Take backup of your spanish copy.Secondly, Create a proper language copy of English(en) and now replace the child pages of your new language copy with your backedup pages. Make sure that you maintain the necessary jcr properties.After doing this, you can check the content ref...

Hi @sergio7 , This community group is exclusively for Adobe Experience Manager Sites.you can post this query on https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/ct-p/adobe-experience-platform-community?profile.language=en for a better reach and replies. Thank you. 

Add the dependency to your core bundle and that should clean this error.<dependency> <groupId>com.fasterxml.jackson.dataformat</groupId> <artifactId>jackson-dataformat-csv</artifactId></dependency>I tried it too and the build is successful. 

you can do one thing, instead of addind style policies for each component, you can have one categorie name of all your component specific clientlibs. For example say "myapp.components". Embed this to your site client lib. That way, you can you use one single policy at page/template level.