Hello Team, We have a requirement where we there are few product detail
pages which needs to secured for some sensitive authoring which
shouldn't be know to many till go-live. Step wise details below: Suppose
standard we -retail MSM structure is followed and we have a product
detail page like /content/xyz/language-masters/en/products/product1 .
There also exists a published livecopy of the same as
/content/xyz/us/en/product1.htmlNow there is some sensitive content to
be added on the page which o...
We are programmatically trying to create/update assets . Code looks like
below: Asset asset = assetManager.createOrUpdateAsset(path, assetBinary,
documentMimeType, true); Now the first time asset gets created. If the
asset is updated using the same method it is adding jcr:isCheckedOut =
true. As per
https://docs.adobe.com/docs/en/spec/jcr/1.0/8.2.6_Check_Out.html
documentation this property states that the node is checkedOut while its
versions are created/updated. Can we get clarity if this prop...
This is happening in AEM 6.5.2 . Due to this request combined with ACS
Commons we noticed that The call that AEM is getting, that call in
itself is 404 always, checked it on vanilla server. Since the call is
404, it would invoke your error handler JSP.. and the vanity check code
is throwing some code error, when the incoming URL pattern is:
/libs/granite/operations/config/maintenance/granite:daily.infinity.json
So we had to wrap the 404.jsp to catch the exception.
Yes these are frequently in our logs. And due to this request combined
with ACS Commons we noticed that The call that AEM is getting, that call
in itself is 404 always, checked it on vanilla server. Since the call is
404, it would invoke your error handler JSP.. and the vanity check code
is throwing some code error, when the incoming URL pattern is:
/libs/granite/operations/config/maintenance/granite:daily.infinity.json
So we had to wrap the 404.jsp to catch the exception.
Yes these are frequently in our logs. And due to this request combined
with ACS Commons we noticed that The call that AEM is getting, that call
in itself is 404 always, checked it on vanilla server. Since the call is
404, it would invoke your error handler JSP.. and the vanity check code
is throwing some code error, when the incoming URL pattern is:
/libs/granite/operations/config/maintenance/granite:daily.infinity.json
So we had to wrap the 404.jsp to catch the exception.
We have two AEM Publishers and the below exception is continuously
thrown on both the publishers. 29.04.2020 16:50:21.804 *INFO*
[qtp279028224-11690] log.request 29/Apr/2020:16:50:21 +0000 [130007] ->
GET
/libs/granite/operations/config/maintenance/granite:daily.infinity.json
HTTP/1.1 The maintenance jobs for daily and weekly is configured and
working fine. Any other reason why this might be happening?
Hello All,Are there any recorded steps to enable xmp extraction and
write-back on ubuntu as there are steps for Red-Hat Linux server (Enable
XMP extraction and write-back on 64-bit Linux ) ?XMP extraction &
write-back is not working on ubuntu.Thanks in AdvanceAshish Ranjan
Hello All,We have a requirement where we have to expose a permanent link
for every DAM Asset which should not change even on Asset Update or
Asset Move ? This link will be used for integration with external CMS
for e.g. Wordpress and Adobe DAM is used as Digital Asset Management
System.Is there something available OOTB? One possible solution what we
have thought is generating a unique id for each asset on asset upload,
store it as metadata and construct the Asset Url using the same and upon
each...
Hello,Please use Sling Resource Merger to achieve this.Some useful links
below:-Using the Sling Resource Merger in AEM
http://www.aemcq5tutorials.com/tutorials/sling-resource-merger-in-aem/
Using this you can achieve something like belowThanks & RegardsAshish
Ranjan
Hello Tuhin,Thanks for the answer but I found the cause and solution to
the above issue. Basically Asset Update Workflow is running and the
metadata writeback step has the code to create versions and the
configuration is maintained via the Ncomm XMP Handler.So if we add the
video format to com.day.cq.dam.core.impl.handler.xmp.NCommXMPHandler
versions start getting created. Also this issue is not only with Videos
but also xlsx, pptx etc, basically any format not mentioned in the
supported formats...
Hello All,OOTB whenever we upload/modify metadata for images, pdf etc
version gets created but it doesn't happen in case of video. Can anyone
help us understand why?Moreover if I create a workflow with the step
Create Version it works fine but if I add it to the DAM Update Asset
(ffmpeg configured) it doesn't work fine. I have also checked that there
is launcher as below :-However even if I satisfy the condition
dam:scene7FileStatus==NeedsReupload , versions are not creating , rest
everything is...
A working session on best practices to integrate Adobe Recommendation
using Adobe I/O API to consume recommendation data through backend.
Information to track DAM workflows progress/steps through DTM to capture
information.
Hello Experts,Is there a GLOBALLINK-TRANSLATION-CONNECTOR package
available for AEM 6.4? I could only find connector the latest package
(Package Id: translations:GLOBALLINK-TRANSLATION-CONNECTOR:2.2.0) which
is for AEM 6.2 & AEM 6.3 ?If not can I use this for even AEM 6.4?Thanks
& RegardsAshish Ranjan
Hello All,I am using Shared Component in my site but have few questions
which are as follows:-The site hierarchy of my site is
/content/moduleName/en and the same is specified as the root page for
Shared Component too. Hence the shared properties are stored on the node
/content/moduleName/en/jcr:content/shared-component-properties and
global properties on the node
/content/moduleName/en/jcr:content/global-component-properties . Now if
I edit the shared component on a page under /content/moduleNa...
