hi team, After running Scheduled Page/Asset Activation workflow, I am
not able to see existing workflow inbox messages. It is empty. Go to
Tools -> Workflow -> Models -> Select Scheduled Page/Asset Activation
and click "Start Workflow" giving some Payload.Once done, hit
localhost:4502/inbox and check the inbox list is empty. But the list can
be in seen via localhost:4502/aem/inbox since it is handled differently
i guess. Could anyone please confirm on this.
you got it.. thanks.. Till 188.8.131.52 below condition was there It will
allow us to have placeholder if we have editconfig but either with
dropTarget or inplaceEditConfig or only having a edit config But in
184.108.40.206 Condition is like to allow a placeholder if we have a editconfig
either with dropTarget or inplaceEditingConfig. Edit Config without
dropTarget/inplaceEditing is not allowed to have a placeholder. So this
need to be fixed i guess, It should allow to have a placeholder only
with edit conf...
hi guys,We are using below div element and attribute to give some
placeholder values to touch ui components. It was working fine.But after upgrading to
220.127.116.11(18.104.22.168 SP + CFP 1), it is not working. Could anyone confirm on
this please. It is working fine in 22.214.171.124.126.96.36.199 Screenshot188.8.131.52
Hi Guys, In 184.108.40.206 (220.127.116.11 Service Pack + CFP 1) "Create User" and
"Create Groups" option are not working for touch ui. Could you guys
please check this and confirm. Go to Tools → Security → Users. Click on
"Create Users" option . Getting below error logs. An error occurred at
line: 48 in the jsp file:
cannot be resolved to a variable45:46: attrs.add("data-home",
hi guys, In AEM 18.104.22.168 Service Pack release notes, some of the key
highlight is mentioned as "Updated the jQuery version bundled in
ContextHub to 3.4.1." But i could see still it is pointed to 3.2.1 in
"/libs/granite/contexthub/dependencies/jquery". Could you guys please
confirm on this update. Thanks.AEM 64 SP release note:
hi team,Please let me know if we can install 6.4.8 Service Pack in a
instance which already has 6.4.7 SP installed. I tried to install with
force upload option, since SP is cumulative pack of previous fixes, i
thought it will work, But my instance is still pointing to 6.4.7 under
"/system/console/productinfo". Please let me know if it needs to be
installed only with 6.4.0 instance.
hi team, When we had try to purge the workflow (completed/aborted), we
got query limit exception issue, so we thought of fine tuning
/oak:index/workFlowDataLucene with includedPaths / excludedPaths. As per
our analysis we came to know that only from below three paths, it is
getting indexed./var/workflow/instances - Runtime Workflow
Model/etc/workflow/instances - Old workflow instances before repo
restructure/var/taskmanagement - OOTB task managementSo we thought of
adding the above three paths i...
As per Adobe doc, All the services are components but not vice versa.
But when i checked in http://localhost:4502/system/console/servicesIt is
showing as 6630 service(s) in total. and then i checked in
http://localhost:4502/system/console/componentsIt showing Number of
installed components: 3374.May I know how come the number of services is
greater than the number of installed components?
Both cq(com.adobe.granite.xss.xssapi) and
sling(org.apache.sling.xss.XSSAPI) xss filterHTML() methods allows the
events in style tag which causes security threat. May i know how to
restrict it ?Eg.xssAPI.filterHTML("test") - Instead of removing the onload
events, it's allowing the alert.
is not coming.For eg: In localhost:4502/editor.html/content/sample if i
use window.location.href or any other js methodsit is returning only
May i know the exact solution to avoid data-attributes getting filtered.
Each and every time we are adding manually in
xss-protection-config.xml.For Eg if we have data-src attribute in img
tag , In xss-protection we have added code like
belowIs there any permanent fix
to avoid data-* attributes getting filtered?