It has to do with resolving context-aware configuration stuff. It's
using an underlying service user cloudconfig-scripttags with jcr:read
permissions to read the ScriptTagComponents from all cloud services.
The handles (highlighted in red) will only let you reorder if the
underlying folder is of type sling:OrderedFolder. Folders can be -
sling:folder- nt:folder- sling:OrderedFolder two of those three won't
re-order. much of /content/dam is sling:folders fyi -- so not
reorderable Open a Daycare ticket if you want to pursue this further.
I don't expect you will get an answer here on this public community
forum. The way this post is worded to me can be construed as a potential
social-engineering attack trying to extract account information.
Why step 3? You don't need to restart AEM after installing a
ServicePack. The main thing to be cognizant about for a Publish Service
Pack install is you don't want live web traffic hitting that instance so
a practical approach here is to remove each Publish one-by-one out of
your load balancer and upgrade each individually. Rotating instances in
and out of service while doing it as to not impact your production site.
what I'm saying is -- Adobe Customer Care has seen incidents with
organizations who use Mutual SSL (always seems to be banks) where they
encounter odd edge case scenarios where the Java JVM selects the wrong
alias during handshake and this is leads to failed SSL connections.
Lucene is case sensitive. You'd need to run the token through the
LowerCaseFilter Do you have a custom index for your queries? To
accomplish this you'll need to modify an index definition in CRX/DE. I'm
going to assume you're using a custom index 1) under
/oak:index/your-custom-index2) add an analyzers nt:unstructured node3)
add a default nt:unstructured node under analyzers 3) add a filters
nt:unstructured node under default4) add a LowerCase nt:unstructured
node under filters5) reindex the ind...
This is something to do with your local install of Node JS. Is this
actually where you installed Node JS?
version of NodeJS are you running? The Wknd site needs v10+