The reason why this happens:* Some customers are provided with some
hotfix for an issue, until the actual fix is released in any future
updates/releases. Since the overlay exists(/apps), the actual fix(/libs)
won't even show up as working, until that overlay is removed.Moreover,
the fixed file may have something more(e.g.: new feature/functionality
or some optimization) than what exists in the overlay. Due to this, that
new feature/functionality won't even work and thus, can result in other
issu...
What errors do you see in the browser's Console tab?What errors/messages
do you see in the error.log file when you do a Page Preview on the
affected content page/path?
* Try running dispatcher flush manually from the instance on which the
flush is configured.You can try running a curl command. The following
docs may be
helpful:https://experienceleague.adobe.com/docs/experience-manager-64/administering/operations/curl.html?lang=en#common-content-manipulation-aem-curl-commandshttps://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalidate.html?lang=en#manually-invalidating-the-dispatcher-cache
If it doesn't work, it means ...
You can refer to Content Fragment Core Component for
reference.Sample:https://aemcomponents.dev/content/core-components-examples/library/page-authoring/content-fragment.html
Github:https://github.com/adobe/aem-core-wcm-components CF Reference
Docs:https://docs.adobe.com/content/help/en/experience-manager-65/developing/extending-aem/customizing-content-fragments.html#using-content-fragments-in-pageshttps://docs.adobe.com/content/help/en/experience-manager-core-components/using/components/content-...
* Is your uber jar version compatible with the exact version of your AEM
6.5 that you are using?Example:AEM: 6.x.yUber Jar:
uber-jar-6.x.y-apis.jaroruber-jar-6.x.y-apis-with-deprecations.jar Found
another community article that might be
helpful:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-day-cq-dam-core-cannot-be-resolved-in-aem-6-4/qaq-p/322990
* Which exact/complete versions of AEM 6.3 & 6.4 did you try this on?
Were those the latest versions on both AEMs?* Can you also please share
the exact steps in detail? You can also log a ticket with AEM Support
team to get this issue resolved/attended to, at the earliest.
Package Share has been deprecated. Please use Software Distribution
portal:https://experience.adobe.com/#/downloads/content/software-distribution/en/general.html
You can download all AEM related packages from
here:https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html
If you are not able to access the Software Distribution portal, please
reach out to your Org Admin, who can grant you access to it. Hope it
helps !!
Cause:Inconsistencies in oak:index/references. This can be caused by
using external methods to modify content in the JCR Solution:Perform
reindex for the synchronous indexes of
/oak:index/referencehttps://helpx.adobe.com/experience-manager/kb/how-to-reindex-a-synchronous-AEM-index-AEM-Oak.html
When Multi Resource Support is enabled, it creates only one instance for
the full folder and the number of assets inside does not matter (the 15
asset limit doesn't apply here). However, if we select individual assets
and trigger the workflow on them, then irrespective of whether Multi Res
Support is enabled or not, individual instances are created for each
asset and the 15 max assets limit does apply here. * When Multi Resource
Support is enabled on Workflow, it doesn't consider the default lim...
The following post & the external link may be
helpful:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-content-migration-and-pages-creation/qaq-p/327587
https://gist.github.com/joemaffia/87f8328eed1810a93260
* Do you see the same behavior, when you close all currently opened tabs
& windows, clear browser cache & cookies, open a new browser in
Incognito mode?* Do you see any errors in the Console tab of Developer
Tools?* Did you install any custom/third-party bundle/package, after
which you started seeing this issue? Try uninstalling/disabling &
removing them, perform the below step and then verify whether the issue
still exists:Try recompiling JSPs, invalidating clientlibs cache &
rebuilding clientl...
The following web servers are supported for
Dispatcher:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.html#dispatcher-platforms-web-servers
You can refer to the Dispatcher docs
here:https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/dispatcher.html
The way you have configured dispatcher on your Microsoft IIS locally. Do
the same on a server(Cloud or VM which you would expose publicly) with
Microsoft IIS or Apache...
dispatcher-apache2.4-xxx isn't supported on Windows. The following web
servers are supported for
dispatcher:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.html#dispatcher-platforms-web-servers
You can download the specific dispatcher from
here:https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/getting-started/release-notes.html
I hope it helps !! 🙂
I am not able to reproduce the issue on 6.4.8.1.Are you using the same
user to unlock the page, that had actually locked the same page? If not,
then you would need the actual user who had locked the page, or OOTB
superuser named "admin" to unlock that page. I created a user named
"testUser" and added it to Administrators group:1) I unlocked
/content/we-retail/us/en page. 2) Then, I locked it back using the same
testUser. The following document may be
helpful:https://helpx.adobe.com/uk/experience...
Thank you for clarifying it. 🙂 You can use any HTML Parser library(eg:
JSoup HTML Parser) to do that. Include that dependency in pom.xml file
and then use it to read HTML content or even links on any internal page.
Sample Reference code can be found
here:https://mkyong.com/java/java-how-to-get-all-links-from-a-web-page/
You can include the similar code in your servlet to achieve your use
case. I hope it helps !! 🙂
Make the necessary change(s) in the template(s) that are used to create
those pages. That would fix the JS/CSS errors on all the pages that are
created using that template. I hope it helps !! 🙂
You can write a groovy script that crawls over your /content/
looking for strings that start with /content. Then, use ResourceResolver
to verify whether those paths exist. The following links may be
helpful:a) Sample Groovy Script =>
https://gist.github.com/trekawek/72b3515a6641ca5f4b29b) ResourceResolver
API =>
https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/org/apache/sling/api/resource/ResourceResolver.htmlc)
Community Article =>
https://exper...
I doubt there is any such group OOTB. But, it's really easy to create
one such group. You just have to create a group and give complete Read
Access in /useradmin console. Ex: http://localhost:6440/useradminSteps
to follow:1) Go to http://:/useradmin 2) Create a new group
by clicking Edit -> Create -> Create Group. Give any group id and group
name.3) Search for that newly created group. Go to Permissions tab of
that group. Select Read for all the nodes, or for the root node, and
click on Save.4) ...
Verify the CRUD permissions for those groups in /useradmin console.Also
check their ACLs in crx, if it's specific to any node.These might help
figure out the reason.
You can check how your request is being processed/forwarded in
/system/console/requests console. You can also check the incoming
requests in request.log, access.log and the reason for failure in
error.log. Also try enabling DEBUG logger for your custom servlet. That
may also help. Hope these help. 🙂
Yes, there is. 🙂 The following doc may be
helpful:https://docs.adobe.com/content/help/en/experience-manager-learn/assets/metadata/metadata-import-feature-video-use.html
On the publish server, are you able to reproduce the issue, when you
bypass the dispatcher(i.e., access the publish server using its host &
port directly)?a) If not, then enable DEBUG logging for dispatcher, and
see which filter is blocking the request. You can then allow this
request to go through dispatcher. b) If it's still reproducible,
invalidate cache & rebuild clientlibs via File System, as per [1], clear
all browser cache & cookies, close all browser tabs & windows, open a
new one in Inc...
In addition to it, since AEM 6.4 onwards, Repository Restructuring
occurred.The following doc may be helpful in finding the correct
locations/paths of nodes in AEM
6.5:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/restructuring/repository-restructuring.html
There are many clientlibs that are not just specific to authoring. They
are also related to how your content/components appear on the UI, lazy
loading of assets, etc. If you remove any clientlibs that might be
required, it would mess up your UI. You would have to replicate them
from author and even rebuilt clientlibs, if needed.Just do a thorough
testing when you perform the cleanup, such that you don't miss anything
that could lead to potential issues in the future.
@kartheekd203042 The count seems to be 0. It could be something to do
with cqPageLucene(/oak:index/cqPageLucene). Try re-indexing it and
verify whether the issue still exists. Try using OOTB cqPageLucene index
and then verify whether the issue still exists.
* Check for the existence of ensure-service-user on your AMS
environment.* Go to /system/console/configMgr, search for the service
mapping for this bundle and ensure that the service user is included
within [], and then save it.Ex: I don't have acs bundle, but I have the
following mapping configured for a service
user.com.adobe.cq.cq-experience-fragments:target=[targetservice] Hope it
helps !!
This issue isn't reproducible OOTB. * Do you see any Console errors in
Developer Tools of your browser?* Do you see the same issue using OOTB
admin user? If it's not related to permissions, try the following steps
as well:* Enable DEBUG log level on query class below in
/system/console/slinglogorg.apache.jackrabbit.oak.query * Reload the
http:////libs/wcm/core/content/sites/templates.html/conf on
your AEM environment.* You will see the logs showing some query. It
would be something like: SELECT ...
You can use the Asset Interface to achieve the same. // to create an
asset AssetManager assetManager = resolver.adaptTo(AssetManager.class);
Asset newAsset =
assetManager.createAsset("/path/to/asset/document.pdf");The following
docs may be
helpful:https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/com/adobe/granite/asset/api/Asset.htmlhttps://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/javadoc/com/day/cq/dam/api...
