If have a (reasonably 🙂) finite number of inputs producing a
(reasonably) finite number of permutations of JSON - you could also look
at using HTTP Cache [1] to cache the entire JSON output in AEM memory
and serve it from there. [1]
https://adobe-consulting-services.github.io/acs-aem-commons/features/http-cache/
Hi @Mounikasri If you are trying to include some metadata HTL script
across all the pages for any website, please overlay your page template
(head.html) file where all the matadata for a page are defined.Now you
can create another HTL file with the required HTL script and include the
file in the path at the desired location, preferrably after the
metatags.${page.title}${page.brandSlug ? '
| ' : ''}${page.brandSlug}<-- Your file/custom meta
script should go here -->This will ensure all the pages ...
@Adilmo i dont recommend trying to surface anything other dam:Asset
nodes with Asset Share Commons. There is *alot* of plumbing of that
assumes results themselves as well as the "target" of results (when you
click on a result, what you're taken to) is a dam:Asset. Many, many,
many things will break if you try to adjust this paradigm - and you'll
have to rip out the guts of Asset Share Commons to get it even close to
working. This is also covered here:
https://adobe-marketing-cloud.github.io/asse...
@Mariia_Lukianet, Thank you for posting the solution with AEM Community.
This helps in posterity. Keep the wonderful contribution going (both as
learner and contributor).
Hi Arun_Patidar, So you meant that instead of executing at path
/content/projectpath. I must execute a lower level that
/content/projectpath/us/en/projectapplications Thanks
Have you tried using AEM Mock's AemContext to create mock sling request
context? I highly, highly recommend using AEM Mocks when possible rather
than mocking out everything yourself. These sorts of problems should go
away, and also lets you write more natural tests.
https://wcm.io/testing/aem-mock/usage.html
Yes - the wcmmode code will work when you deploy it to your live site on
whatever domain. The wcmmode on AEM Publish is always "disabled". Think
of it this way, AEM uses "wcmmode = disabled" when the page should be
rendered without all the WCM (Web Content Management) bells and whistles
that are used by authors to author the content.
The way to do this (especially when talking about DAM Assets, which need
to have a canonical source in AEM) is to simply put a CDN in front of
Dispatcher/AEM. If youre talking about AEM Author, you can cache
Clientlibs on the CDN, but you must expire them after ANY code
deployment. Never cache DAM Assets on AEM Author as this will result in
content mis-matches, and result in a broken experience. If youre talking
about AEM Publish, you can cache both Clientlibs and Assets on the CDN.
You would se...
TL;DR - there really isnt a magic number. I assume Android has something
similar (Im sure google can help you), but I expect it's close to what
Apple recommends:
https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/image-size-and-resolution/https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
I'd take a look at what mobile device families your targeting and then
look up the recommendations from iOS/Android and do wha...
In edge version 44 and below i am not seeing any issue with POST calls
i.e. 204 error code. In chrome am seeing the issue 204 error code and
with all the updated versions of the browsers. @davidjgonzalezzzz
@bmccurdy1 Please suggest
I think @BrianKasingli hit this one on the head.If youre dead set on
automating this through custom code, two approaches to look at are:
First approach, Update Activate WF Model 1. Remove replication ACLs on
the content so the Activate Workflow Model is invoked when a user tries
to Publish2. Augment this Workflow Model to include a new Custom WF
Process Step3. This Custom WF Process Step would have available to it
the path of the Asset being activated, at which point you'd have to be
able to wri...
@Keerthi97 there is no magic bullet for this, since there are any number
of ways the HTTP POST endpoints maybe have been defined in AEM. In the
best case, all your HTTP POST endpoints are bound with well-known Sling
selectors -- so like, HTTP POST
/content/site-1/page.my-custom-submisssion.json, where
`my-custom-submission` is the identifying selector. If you have a set of
well-known selectors, you can allow POST whose URLs contain that
Selector or Path pattern .. some examples are here [1] If y...
The best practice to secure AEM Publish endpoints via Dispatcher is to:
1. First Deny EVERYTHING2. Then Allow only what you need to This is why
the first rule in the OOTB AEM Publish Dispatcher is "DENY *" [1] In
terms of identifying what URL end-points need to be ALLOWED in
Dispatcher for POST'ing depends on your application's design. Hopefully
custom POST end-points are bound to servlets registered to Servlets by
Resource Type and Selector/Extension, and the resource that has the
respective sl...
An asset's Tags and Keywords *ARE* Metadata. Both are data about the
asset. Generally, it's best to align to industry-standard
namespaces/properties. You'll see AEM even does this OOTB; instead of
inventing its own custom "dam:title" metadata property, it uses the
Dublin Core's "dc:title". Using industry-standard namespaces/properties
certainly makes your metadata more portable across applications that
might use your assets (these apps might be able to reason about industry
standard fields that ...
@Jai1122-1) if you are creating the JCR Session in your code (ie.
calling repository.login(..)) then you are responsible for closing that
JCR Session (preferably in a finally block). Your JCR Session used to
create a cq:User and/or its Token has nothing to do with the security
context the user gets when they login with the token. 2) Yes, again,
since your code is creating the resource resolver that calls your
RepoUtil, you need to also close that resourceResolver when you are
finished with it (i...
Can you share an example github project where this problem occurs? It's
easier to reproduce and help you. My second best guess is that you have
a mix of OSGI and SCR annotations, but not the proper maven-plugins
active to the generate the SCR metadata files.
Hi, Unfortunately, this looks like a regression. Please log an issue
with Adobe Support so AEM Engineering team can resolve. You could look
at injecting some CSS that resolves this issue in the interim. 1. Make a
new cq:ClientLibraryFolder under /apps to hold your temp fix. Assign
this ClientLibrary the following category:
cq.listview.coral.columns.personalization2. Add a new CSS file (ex.
fix.css) to this folder with the CSS rule:.coral-Table-wrapper.is-sorted
.coral-Table-row button[icon="drag...
I assume by "sonar properties" you mean setting blanket exclusions at
the POM level? It's typically unwise to blanket exclude entire
packages/classes from code quality checks. What you should do is:1.
Review violations reported by Cloud Manager, and fix the ones you can1.
There may be reported issues that aren't for whatever reason you do not
want to/cannot change, for these, it is better to explicitly suppress
that exact warning for just that method/class similar to [1]. This way
if you evolve ...
Another interesting solution could be the following: 1. For each
role/path combo - create a Hidden predicate on the Assets Search Form
1. Use the excludespaths QueryBuilder predicate to exclude a specific
path/path-pattern -- test this out as excludepaths seems like it might
be a little slower, you might be able to figure out how to do the
inverse using the paths predicate as well.1. Permission those hidden
predicates nodes in the JCR to be only read-able by members in the role
that shouldn't b...
This data is not persisted OOTB anywhere. If I were to attempt this I
would probably start by trying to inject Analytics code (by way of
Launch) into the ClientLibrary used for Search. This custom JS would
send the searched terms to Adobe Analytics (or whatever web analytics
system you have) which would hopefully provide you very easy reporting.
If the only place to store this data is in AEM Author, then I might
explore a Sling Filter that quickly accepts requests that match a
search, and also q...
You're supposed to be directly referencing anything in the
com.google.gson.internal package... that's why it's called "internal".
See the big warning on the GSON JavaDocs site for these internal
packages [1] that reads: Do NOT use any class in this package as they
are meant for internal use in Gson. Infact, this package is no longer
exported at all in later versions of GSON. The fix is to update your
code to depend on Gson's public API space. [1]
https://javadoc.io/doc/com.google.code.gson/gson/...
You can overlay the menu node and add a rendition condition to it.
Overlay:
/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata
at
/apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata
Add a rendition condition at:
/apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/metadata/granite:renderconditionYou
can do something like:sling:resourceType:
granite/ui/components/coral/foundation/renderconditions/privilegeprivileges:
jc...
