Hi, Can you try creating a component extending core download component
(core/wcm/components/download/v1/download) and observe the behavior.
(HTL code looks similar though)If it is still not happening, can you
check for the "docx" asset which has filename without space (%20)
@anthonyt2853861,You can take a look at the implementation of the ACS
Common Site Map Servlet, and use it as inspiration to build your own
Site Map servlet. Cloning
"com.adobe.acs.commons.wcm.impl.SiteMapServlet" directly into your
project will work without much configuration. Read the implementation of
the SiteMapServlet and understand what it is doing. With this example
code, it should be able to steer you to the right direction on how to
implement and build your own Site Map Servlet. Also, ne...
Hi Jorg, I am interested in the second option, I want to import a single
project maven and in that project to have my 2 projects AEM. Why want I
that? Because I have a site in production with the cloud services AEM.
They gave me a repository AEM. Within that repository I want to push my
new site AEM. Each project will have its own artifact.
As @jbrar already mentioned it's all about the maven structure. You just
have to create multiple sub-modules, which contain the bundle, the
templats/components/dialogs for a single site. You need to ensure that
both are not deploying to the same repo location and do not have
clashing bundle names. But besides that it's pretty straight-foward.
Hi Frank, that error may be because your publish instance is not exactly
synchronized with your author instance.I recommend that you verify if
the bundle both in your author instance and publish are the same.You can
validate in the following url:Author instance: http:
http://localhost:4503/system/console/status-slingmodelsIf they are not
the same, go to your core project and run the following command by
console: mvn clean install ...