Hi Sandrateixeira,Currently, it is a known limitation that AEM SPA
Editor does not have the ability to perform URL shortening -- refer to
[1]. I did not find a timeline/roadmap for the implementation of this
feature, however, if it is released, the SPA documentation will be
updated accordingly.Regards,Lisa[1] SPA Editor Overview
Hi joaoantunescosta,Adobe team is aware of the openssl EOL details. We
are working internally to implement support in Dispatcher for openssl
1.1.x -- Adobe internal ID reference is : DISP-813.DISP-813 is still
being worked on, however, please do bookmark [1] -- this document will
be updated upon release.I could not find the way to subscribe to receive
Dispatcher newsletters/updates.Regards,Lisa[1] AEM Dispatcher Release
Notes
Hi edaem90,Please check out Adobe AEM documents [1] and [2] . Let us
know if these documents help.Regards,Lisa[1] Best Practices for Email
Templates [2] E-mail Marketing
Hi Matt-H-,Please see inline-answers to you questions:Is the system
using the parent entry or the child entry?> Not certain how to confirm
-- cannot guarantee if parent/child is picking in the environmentHow do
I change the top/parent entry (and not have a child entry)?> You should
be able to click the Apache Felix Jetty Based Http Service row within
/system/console/configMgr (the row with the checkmark on the left and
Edit,Unbind, and Trash buttons on the right of the row) and make changes
and ...
Hi gavyas,Use CRXDE Lite search to search for the name of your custom
log file name (e.g. file="logs/queries.log", I search for 'queries.log'
) and see if there are any results within /apps, or any other directory,
which has a node name similar to
below:/apps/system/config/org.apache.sling.commons.log.LogManager.factory.config.f0515b33-4f34-4b63-9e24-ac09ff72eae0.config
Check the resulting .config file (double click the .config node within
content tree to review the file -- ) and confirm if it's...
Hi aravindS,The particular code you are looking for is in the Adobe
Granite CRXDE Lite (com.adobe.granite.crxde-lite) bundle -- this is not
a file you will see in CRXDE Lite content tree.Please share your
use-case and requirements so we can help you out further -- I may have
misunderstood your ask/intent.Regards,Lisa
Hi basantrai,Please check the replication agent settings itself, there
is a 'Log Level' setting within the agent settings.For example:1.
Navigate to Tools>Deployment>Replication2. Click Agents on author3.
Click the Default Agent (publish) (this is the out of the box name for
the default Publish replication agent -- your instance may have a
different replication agent name)4. Within the replication agent UI,
click the 'Edit' button to open the Agent Settings editor5. Review the
Log Level [1] (sea...
Kishore,I am not certain if I understand your question, however, please
refer to document [1] which states the OOTB XSS config file.Your team
would overlay the item /libs/cq/xssprotection/config.xmlto
/apps/cq/xssprotection/config.xmlMake your changes to the overlaid
file.Please detail the intended use-case and requirements for us to be
able to assist further.Regards,Lisa[1] Security
Can you share details about what AEM version you are on ?I tested
creating a user via Tools>Security>User and cURL and both results in the
profile and profiles node creationTested on 6.5 GA and 6.6 L7 (Adobe
internal testing version)
Hi Cody,I briefly tried to find "mcvisid" but had no luck -- I then
reviewed my own cookies and saw AMCVS related cookies -- found document
[1] which is the 'Experience Cloud Cookies' -- I verified on my own
local AEM instance (localhost:4502) cookies and observed the related
AMCV Name value pairsPlease check the document and see if these are the
items that may help with your Marketo form requirementsRegards,Lisa[1]
Experience Cloud Cookies
Hi Tarrant County team,We are working internally (with your CSE) to
review the issue on your PROD environment -- we will be updating the
related Daycare ticket accordingly. We apologize for the lack of ticket
updates -- as detailed in the recent ticket update.Regards,Lisa
Hi Ashishr,Please have team expand and review the 6.4.4.0 release notes
[1] , in particular, search for CQ-4257440 details :Snippet:Rich Text
Editor in dialog is flickering when popover of a plugin is higher than
text area, hence, blocking any further authoring. NPR-27579: Hotfix for
CQ-4257440Regards,Lisa[1] AEM 6.4 Service Pack Release Notes
Hi Tharun,Please share some logs from the dispatcher.log so we can see
why redirect is happening.Also, if you suspect caching issue, please
also share the dispatcher.any details so we can review the
rules.Regards,Lisa
Hi Sumank,Based on this error.log snippet you shared and also the
httpd.conf file shared -- I found a forum [1] which may address why your
Dispatcher handler configurations are not picking.Please modify your
httpd.conf file --- use this below 'IfModule' tag based on your
LoadModule statement :LoadModule dispatcher_module
modules/disp_apache2.2.dll...Do NOT use this
(current httpd.conf referencing wrong module 😞Please try and let us know --Regards,Lisa[1] Problem
installing AEM Dispatcher on Max...
Hi swetap37476554,Can you share the scenario in which the JavaScript
error is thrown (share replication steps)? Particularly, can you
replicate this error thrown with the We.Retail sample content? I
referenced [1] to review the We.Retail sample content that has
ContextHub already configured.My vanilla 6.5 install showed me that
ContextHub.console is not a function -- it is an
object:ContextHub{Callbacks: {…}, version: "0.4.18-20190304-1526",
Paths: {…}, Constants: {…}, console: {…}, …}...console...
Hi Kartheek,Apologies for the delay, I was confirming if the information
is fine to release to public.The workaround instead of installing the
patch is to:Change the “Whitelist” value from
.*/api[0-9]*.omniture.com/.* to
https?:\/\/api(\d+)?\.omniture\.com(:\d+)?\/rs\/0\.5\/.* within
/system/console/configMgr/com.adobe.cq.contentinsight.impl.servlets.ReportingServicesProxyServlet
configuration.Please make sure to upgrade to latest official patch when
possible.Regards,Lisa
Hi kartheekd20304289The appropriate hotfix/patch package for AEM
Version 6.3.1.2
is:https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/cq630/hotfix/cq-6.3.0-hotfix-24657
Please note that the pre-requisite for this hotfix is SP2.Regards,Lisa
kartheekd20304289 , yes ,
http://localhost:4502/libs/cq/contentinsight/proxy/reportingservices.json.GET.servlet.a.23
.css is the same as ReportingServicesProxyServlet.java servlet .Here is
better description regarding the functionality of this servlet:The
servlet is proxying requests for browsers (older IE) that do not
properly support CORS XMLHttpRequests. The servlet is not used if
Content-Insight is used with modern browsers. Applying a Dispatcher
filter would indeed interfere with the Conte...
Hi Kartheek,The purpose of the ReportingServicesProxyServlet.java
servlet (found in the notes directly in the source code):/** * A servlet
that proxies requests to Reporting Services's API for browsers * not
supporting real CORS, i.e. IE 9 with XDomainRequest. * * The API's
response code and body are copied to the servlet response. */This SSRF
vulnerability is related to Adobe Security BulletinPlease note that the
immediate fix would be to install the corresponding hotfix for your AEM
version (...
