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.https://forums.adobe.com/thread/2569095
What are the options that I have if I want to use SASS (SCSS) and
Ecmascript 6 (or even Typescript) in my projects? Is there a tool to
transpile SASS, Ecmascript6 or Typescript that I can use with Adobe
AEM?Thanks,Fernando
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 complaint with old Javascript versions, solved the
problem.The code was in a custom implementation of a Store, inside the
following JS
file:/apps/myproject/components/contexthub/stores/mycustomstore/store...
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.DefaultConfigurationResourceResolvingStrategy
Ignoring reference to /conf/myproject/settings from
/conf/myproject/settings - Probably misconfigured as it ends with
'/settings'I don't know if it relates to the Contexthub probl...
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 using custom Ui Modes. We need to change those paths
in page/audience configuration.
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.
Hello,We have just installed Service Pack 4 in our servers and
ContextHub is now failing to show Ui Modes.We are getting this error in
the Chrome console, while trying to edit a Segment (Audience):Uncaught
TypeError: window.injectContextHubUI is not a functionThe segmentation
is not working at all within our pages, and the segmentation toolbar is
also not being displayed while previewing content.Anyone knows a
solution for this?(Edited: by the way, I am migrating from 6.4 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.
Hi,I've followed lots of tutorials and was able to configure the
Contexthub.I've created a Store, Ui Modes, then created Audiences
(segments), Activities.I've configured the Personalisation tab on Page
Properties, pointing to my customized context hub configuration folder.I
am able to see the "Targeting" mode while editing a page and have
successfully configured different layout configuration depending on the
selected audience (segment).But when I click the Preview Mode or when I
click to view t...
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 package containing only the individual
pages you want, but it would give you some headache because you also
need to send policies, images, templates, styles (and not only
pages).The way we do here is that ...
Hi, we are trying to use ContextHub to implement personalisation
(segmentation) on our website.We were able to implement it correctly.
Everything is OK, but in some computers, we don't know why, the screen
flickers before displaying the final content.In some computers:a) First,
it displays the Default content (without segmentation applied).b) Then,
after 1 second, the screen changes completely to match the
segmentation.Anyones knows why this is happening? We want to see the
final content with se...
Hi guys,I Know that Adobe Managed Services may already be doing it
behing the scenes, but I have a requirement here in my company that I
have to intercept all log entries (from AEM instances) and send it to
our private AWS CloudWatch account.Can anyone give me the general idea
in how I can do that?Thanks
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
Hi there.I have the same problem.We’ve created a page in Adobe AEM using
DAM to serve image files. PNG image files are being served OK, but SVG
image files are not being displayed correctly in Chrome (Firefox
actually displays it).The problem is: AEM http response should be
returning “Content-Type:image/svg+xml” but it is actually returning
“Content-Disposition: attachment; filename="yt.svg"”.If I try to open
the URL directly, Chrome doesn’t display the image (instead, it tries to
download it), ...
Hi there, I got the same problem.When using SVG files in AEM 6.4, the
image is not displayed in Chrome. In Firefox it displays
correctly.Chrome actually thinks it is a downloadable file instead of an
image.AEM should be returning “Content-Type:image/svg+xml” but it is
actually returning “Content-Disposition: attachment;
filename="yt.svg"”.Is there any solution to this?I know I can use PNG
but it is an annoying problem. It is a very basic thing.
