Hi @icegoffy!It's a bit hard to give advice without additional
background and being able to analyze the issue.My suggestion would
be:Have you checked the AC Tools UI to see if your YML definition files
are actually picked up and if there is any additional information?Are
your AC definitions covering immutable/read-only areas in the
repository? In that case, you might have to convert them to RepoInit
statements (see this thread).You are mentioning the module structure of
your project. Maybe the i...
Hi @veerapandianm20!I'm not sure about your approach here. Are you
trying to squeeze the Asset Selector into your path field dialog entry?
I have some doubts if this will work out.Also, referring to the
following statement:When I try to pick the asset picker from publisher,
I get some errors related to the picker.Are you trying to pick assets
from a publish instance? Again, I'm unsure if this works as expected.
Usually, you would pick your assets from an AEM Assets author instance
(which also ha...
Hi @Umesh_Thakur!It's a bit hard to tell where the HTTP Age Header
originates without any knowledge of your setup.I would recommend to
perform an analysis to identify the origin (first step: is it set by AEM
or the dispatcher?). As a short term solution, you could use mod_headers
in the Apache HTTPD (dispatcher) level to remove the unwanted header
from your responses:Header always unset AgeThe AEMaCS documentation on
caching provides some additional details on response headers. You may
Hi @shehjadk07!As @Kishore_Kumar_ and @Bimmi_Soi have already mentioned,
the official recommended way for this is either content packages or via
oak-upgrade tool as outlined in this documentation. Personally, I would
prefer the content package based approach. Another thing that you should
think about is: What kind of content are you talking about?Usually, the
most common classifications would be:Sample content for development
purposesThis is created by the developers and provided, e. g. to
Hi @Marjia_Yeasmin_TL!There is some activity around this topic on the
Core Components GitHub page:RFC #509 on Modal Experience Fragments
(open)PR #570 to create a Modal component (merged)The PR has been merged
to the according feature branch but it's not yet released. It seems that
there has not been a lot of activity lately. You may want to ping one of
the involved colleagues over at GitHub to see if there are any plans or
a timeline for it. Hope that helps!
Hi @akatsuki07!For your use case, there is no need to establish a
connection between Nexus and AEM.What you need to do is:Tell Maven to
deploy your bundle to your Nexus repositoryTell Maven to use your Nexus
repository for dependency resolution For 1, there is a good tutorial
from Sonatype. The most important part should be to add the following to
your Maven settings.xml file (either at /conf in your Maven installation
or at your ~/.m2 directory): nexus-snapshots
Hi @seemak19887037!There are two things to look at: You should do a
cleanup of your packages in Package Manager of all "dcep" packages. If
you think you might need them at a later point in time, download and
archive them to some external storage. Afterwards delete all packages
that are not actively used on that instance.If there are multiple
version of a package installed (see "Other versions" option of the
"More" button when the package is selected), you can start with a
cleanup up of older ver...
Hi @akatsuki07!Option 2 will embed the bundle into package, resulting in
a single deployment package that deploys both parts together.Option 3
will tell the bundle that there is a dependency, but the other bundle
has to be deployed separately. So you will have to separate
deployments.Hope that clarifies it at bit!