Given that the screenshot is showing your own custom metadata schema I'd
start by understanding what field your title maps to and ensure it's
updating what you think it's updating.
Sling will have no idea how to resolve */ But what you're seeing is a
non-issue, the asterisk is used as some selector in the front end and
try adding a trailing / to any path it will also 403. How are you
impacted by this specifically?
There's always the release notes ---> Adobe Experience Manager 6.5.5.0
Assets provides fixes to the following issues: Start option on Create
Workflow dialog for assets in a collection is disabled, thereby
preventing workflow from getting triggered (NPR-32471).
Step 2 is not recommended. The CSRF Filter essentially has 5 bits of
logic it will filter on 1 - request.getAuthType() != null <-- this one
is super common for organizations that have their own custom servlets
that omit setting the authType on the request 2 -
this.isFilteredMethod(request) <-- this one is based on the OSGI Config
for the CSRF framework, eg what methods POST / GET / DELETE etc (this is
what you deleted in Step2 -- not recommended)3 -
doFilterBasedOnUserAgent(request) <-- checks t...
Long story short : Today in 2020 AEM is available as SaaS offering. To
transform AEM from a monolithic Java application to something that runs
inside orchestration containers required a series of repository
restructurings that started in AEM 6.4 and furthered in 6.5. Within this
containered-AEM-world there is a concept of immutable and mutable nodes.
Eg /etc is considered immutable, thus required forcing customers to
migrate their stuff out of these paths to /apps (mutable). Hope that
helps your...
What happens when NNNNN needs to be greater than 99999?Better run
Compaction before the World comes to an end if that is the case. 99,999
TAR files at 256 MB per TAR is an utterly ridiculous 25 TB segmentstore
size.
Re : 403 legacy api access denied. This is coming from Target. Probably
better suited to field that question with them than AEM. Just going a
quick skim it looks like in Nov 2017 these Target Classic legacy api's
were blocked as part of TNT-27260
The SAML response from whatever Idp you're integrating with should set
what groups the user is to be added to. The default group is just a
group that you may want all users to belong to. Having a default group
set is subjective to whatever the requirements are. It may not be
necessary. NOTE -- the groups must pre-exist in AEM, AEM won't
automatically create the group if it doesn't exist. It will create the
users, but not the group.
RE : I am unable to compare the minified file from local js file to see
any difference. What do you mean? just drop the .min off the node name
and it will render the full non-minfied version of that. ORGo into the
HTML Library Manager OSGI config and temporarily turn off minify while
you debug.
Direct Binary Access is how AEM moves blobs/binaries into the datastore
https://jackrabbit.apache.org/oak/docs/features/direct-binary-access.html
Can't answer your question specifically though since you've
truncated/obfuscated much of the error. ~Marc
Search is built on Lucene. So this isn't so much an omni-search issue
rather than the index definitions are not tokenizing the characters.For
example, ootb AEM will not tokenize Chinese. You need to look at adding
an analyzer to your index definition to handle your Swedish word
https://lucene.apache.org/core/4_7_0/analyzers-common/overview-summary.html
You can probably get away with the StandardAnalyzer. There's some rough
steps on how you can do this if you scroll most the way down this
article...
"However, you would need to wait for the compaction cycle to happen for
that." <--- Key distinction. This is the important part to understand.
The repository is essentially append-only. Version purge is going to
"purge" versions by touching nodes under /jcr:system/jcr:versionStorage.
This action is effectively going to add entries to the segmentstore by
marking versions for future-deletion, which will add to the size.
Revision cleanup is going to compact the repository and clean up all
those 'to...
There is something wrong with your package and how it was constructed.
OakConstraint0022 implies that some mandatory property is omitted from
the package. From the specific error you are seeing the jcr:data
property is seemingly missing from a nt:resource node from that path
under /etc/designs
If you aren't, please ensure AEM is running with at least these 4 JVM
flags : -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps Which will have Java write
some GC information to disk :gc.log, gc.log.1, gc.log.8.current etc
Provide those logs if you have them to the case you raised.
If you aren't, please ensure AEM is running with at least these 4 JVM
flags : -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps Which will have Java write
some GC information to disk :gc.log, gc.log.1, gc.log.8.current etc
Provide those logs if you have them to the case you raised.
From some light-testing on a local instance installing the Hotfix won't
break 6.4.It brings the minor version up from 1.2.60 to 1.2.100.There's
virtually zero active development within the CRX space of AEM. It's a
very mature part of the product. So changes across AEM versions is
generally minimal. You should be okay with this fix. Test on a local
first. The fix won't be available in a service pack until :AEM 6.5.6AEM
6.4.8.2
Hotfix-GRANITE-30226-1.0-1.0.1.ziphttps://documentcloud.adobe.com/link/track?uri=urn:aaid:scds:US:de812fad-c373-4c67-bd34-a6f0b2506434
NOTE -- you will need to use Firefox or some other non-Chrome browser to
install. NOTE -- this was built for AEM 6.5
I made the post before I fully realized where the change needed to be
made. I saw the GIT commit in a JS file and incorrectly assumed we could
manually patch it. But unfortunately, the change is within the bundle
itself so a new JAR will be needed. The fix is within build -
com.adobe.granite.crx-packagemgr.-1.2.100.jar.
May want to log a ticket. DISP-818 removed the Cache-Control header from
requests with query parameters BUT -- this introduced some unintended
things which are currently being handled under the open JIRA
GRANITE-29891
