Hi Team -We have 200+ sub-sites along with the main site in our AEM
platform. We are yet to go to production. To strip the content path we
are depending on the configurations in JcrResourceResolverFactoryImpl,
and adding the path that needs to be stripped under the property config
"URL Mappings" (resource.resolver.mapping) as /content/mysite/en/:/,
/content/sub-site/home/:/, /content/sub-site02/home/:/.....so on till
200 (so far tried with few not added 200 yet). And at the dispatcher
level we a...
Say i have a app that uses components whose super resource type is a
core component - look: For this component to render on PUB - the Core
Components need to be available on PUB to satisfy this resource super
My cross question would be why are we going the VLT route coz versions
won't be migrated for Pages and Assets if you migrate content from one
instance to the other. Also, product implementation has changed in
accordance to Oak so things like LDAP, SAML might break if you rely on
content migration using VLT or crx2oak.Just use these tools as a means
of delta migration when the final cutover happens to new systems else
rely on inplace upgrade as directed in Adobe documentation.
When upgrading - the best advice we can offer is ensure that you are
following all of the AEM Offical upgrade docs -- Upgrading to AEM 6.3
Also test all of your apps and content. If you moved a site that has
components, templates, etc - test them all.
Hello Team -I have an issue with xpath query in 6.3, while upgrading
from 6.0.Issue -Using below query we are trying to fetch the list of
pages that has the string "searchword" with in the page title, tags
related to page, description of the page and within a component (a
textarea component which has the prop as htmldump). As highlighted in
the query we are doing a search for the keywork with the field name of
the component. This all works good in 6.0 but not in 6.3.
Hi Harish,is there a replacement step for scene7 process step in the OOB
workflow in 6.3?i know scene7 has been deprecated and need to use
dynamic media for the same. I wonder this could be discontinued and pls
do reach out to day care for the same.
are you working with locally built HTML or are you uploading HTML from
AEM or another CMS? I ask because many times if you are uploading from
AEM you may not have uploaded the shared resources, which includes the
CSS and fonts etc.