Hi Guys,I think the jsProcessor attribute is not working on AEM 6.4.I've tried lots of things and was not able to make it work.Also, in this thread there is a conclusion it is not working on 6.4: https://forums.adobe.com/thread/2569095I want a processor that transforms Typescript or ECMA6 into ECMA5...

Hi guys,I finally found the cause and a solution for the problem.I don't know why, but the guys here (programmers) have used the keyword "let" in some Javascript code ("let" was introduced in ECMAScript 6).It was working fine before SP4, but a simple change in our code to "var", making the code comp...

Looking up in the error logs, the only thing that I could see is this error:==> error.log <==25.09.2019 15:28:24.189 *WARN* [0:0:0:0:0:0:0:1 [1569436104123] GET /editor.html/conf/myproject/settings/wcm/segments/novo.html HTTP/1.1] org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResou...

Hi dhaliwal,You are right, the We.Retail uses the default ContextHub Path and Segments Path.If I change my project to use the default ones (like in We Retail) then the segmentation toolbar displays correctly while editing Audience (Segments) and also while authoring my Pages.But in our case, we are ...

Hi Guys, I am still not able to use ContextHub with AEM 6.4 SP4.I have tried to load various clientlibs, including the following:- granite.query- granite.utils- cq.jquery- cq.wcm.foundation- cq.wcm.foundation-mainIt works correctly under no-SP, SP1, SP2 and SP3.

I partially solved the problem. Now it is working well when I click to view the Published Page.What I had to do is to copy the "segmentation" folder from the original legacy folder to my custom cloudsettings folder.But I am still trying to make it work in Preview mode.

I am really working in a very restricted network environment, where we have a strong proxy with lots of blocked websites and strict monitoring of information. It may be that our proxy is slowing down the loading of some scripts. But I am not sure yet what is the root of the problem.

I don't see a way of doing what you want without creating a package in QA's Package Manager and scheduling a deploy to the Live server, but this can be catastrofic if you send all files from your `content` package. It could potentially overwrite content that is in production.You could create a packa...

It seems there is an Adobe fix for this, to use org.apache.sling.security-1.1.12.jar.I saw this information in this thread: SVG is not showing on Google Chrome

Thanks you NitroHazeDev. Your Renditions suggestion may be an alternative here.