I am actually trying to figure what AEM uses internally when "Move"
option is used from Assets UI. When the author Move an asset from Assets
UI to a new destination, then all the pages where that asset was
referenced, are automatically updated by AEM with the new destination
path of the Asset. I need to do this Move from through a script, so
thought of confirming if any API is there, which does update the
references automatically or will I have to run queries to find all
references and then upda...
smacdonald2008 Do AssetManager.moveAsset() method update the asset
references as well in all the content or do we need to specifically
handle it by writing custom code? When using "Move" option from author
instance in Assets, it does update the content references of that
particular asset which is moved, so wanted to confirm does API handle it
automatically as well?
smacdonald2008 Yes, the warning clearly says consider creating an index.
But this warning is appearing only in Author instance when accessing a
particular folder in Assets and the query being printed in the warning
seems to be internally fired by AEM. Ideally damAssetLucene index should
take of all these index requirements where no custom
development/customization has been done. What do you think?
We have an images folder for our project in ASSETS section, which has
more than 1000 images in it. Whenever the authors access that images
folder through Assets section
following warning is printed in the logs, which warns about the missing
index for the query that is fired when that images folder is accessed.
*WARN* GET /assets.html/content/dam/abc/content-images HTTP/1.1]
Usually, the client libs(CSS) have been managed by creating Client
libraries under /etc/designs and adding the CSS code using one or more
CSS files in that client lib. However, we can also keep component
specific client libraries, having CSS only for that component, which
will make sure that not every page on the website will have to load the
whole CSS. In AEM 6.3 as well, sample 'we-retail website' and
'we-unlimited-app', the Client Libs have been kept at component level
Hi @Jörg,I have one clarification to make for this strategy. How will
the flushing of files other than "/content" path be handled? For
example, we have "/etc", "/etc.clientlibs" folders in the cache which
have css, js, json, image(maybe) files. The content serving farm will
serve the files as -
when the css is activated, the flush agent will try to flush at the
following path - /opt/cache/etc/abcompany/clientlibs/style.css,...
The questions in itself is not very clear, could you please elaborate
about the problem? I assume that you are using same data set for testing
the search, on AEM 6.2 as well as AEM 6.3 with Solr. When you say, AEM
6.3 doesn't give expected results, does it throw any exceptions or does
it return empty results or does it return wrong results? Also, please
post any relevant log errors, if any.
Thanks leeasling for the reply. I would like discuss more on this
topic.Suppose, an author wants to create an Article Page - 1. In the
traditional way, the author would drag the article component on the page
and would be asked to fill fields such as author, date, title, short
desc and for the article body, the dialog will have a rich text editor
field where author can create the article. Now using the content
fragments, our Article component will have just one field for selecting
the relevant Co...
Hello,I was studying the new feature of AEM, "Content Fragments",
introduced in AEM 6.2 and further enhanced in 6.3, however I am not very
clear about the actual use-cases of the Content Fragments and need more
insight. 1. The Content Fragments are suitable for long article pages or
news pages, but I don't think it can be used for all types of authoring
right?2. Suppose, we have Article Pages and News Pages in our website,
both of which are created everyday, so authors can create those as
Hi Debal,The commerce jar version 5.14.102 is not available in any of
the public repositories, however you can get it if you extract AEM jar
on your local machine. Then just install the commerce core jar in your
local maven repository and it will start working. Let me know in case
you still face issues.In AEM 6.3, there is no need to explicitly add
this dependency as it is already managed by uber-jar, however it AEM
6.2, I had to explicitly add the dependency as well as jar to my local