Hello @Arun_Patidar , Thanks for the pointer, it seems that the
reference-search-service is a subservice which is bounded by service
user
content-reader-service.com.day.cq.wcm.cq-command:reference-search-service=[content-reader-service]",
When checked from system/console/configMgr and compared this against a
standalone AEM 6.5 instance, the below mapper was missing:Mapping:
com.day.cq.dam.cq-scene7-core:ips-jobs-journal-service=[workflow-process-service,dynamicmedia-config-service],
com.day.cq.w...
Thanks Arun,I have had a look in my local standalone 6.5 instance and my
staging in-place upgrade instance of AEM 6.5. I compared the
content-reader-service user accesss/permissions and found them to be
exactly same. Error logs just spit out one line when I try to paste the
page -07.10.2020 14:06:59.765 *DEBUG* [10.60.195.117 [1602040019764]
POST /bin/wcmcommand HTTP/1.1] com.myob.core.filters.LoggingFilter
request for /bin/wcmcommand, with selector null Thanks again 🙏
Thanks, yeah, I agree with @aemmarc.AEM 6.3 still allows moving pages
across from one location to another even if we have launches associated
and AEM 6.5 rightfully doesn't allow the same. My question is if we
could override this default page move validation in AEM 6.5 as well till
we have the old launches sorted OR this is strongly NOT recommended. And
if it's okay to override then how could I override this (the preferred
way)? Thanks again
Thanks, yeah, I agree.AEM 6.3 still allows moving pages across from one
location to another even if we have launches associated and AEM 6.5
rightfully doesn't allow the same.My question is if we could override
this default page move validation in AEM 6.5 as well till we have the
old launches sorted OR this is strongly NOT recommended. And if it's
okay to override then how could I override this (the preferred way)?
Thanks again
Hi ArunSorry for the other comment, I didn't mean to say just 'Hi' it
just submitted the comment when I pressed enter 🙂 So the
reference-service-user or reference-search-service users don't exist in
my local AEM 6.5 setup either but the copy/paste page works well. This
copy/paste issue is only happening in the in-place upgrade staging
environment.I only have below reference related service users in both
the local and in-place upgrade environment and these both have similar
access permissions in...
Hello peeps AEM 6.5.6 doesn't let me move/rename a page from one
location to another location if that page has any associated launches. I
get this below error when I try to move such a page While the message
makes complete sense and I see a reason why is this not allowed out of
the box. AEM 6.5 also gives author an option(checkbox) to delete the
launch after the promotion and this will help with the accumulation of
launches along with the purge task. My question is, can I override this
functiona...
Hello peepsWe have been doing an in-place upgrade from AEM 6.3.3.7 to
AEM 6.5.6, during testing I have found an issue when I copy/paste a page
from one location to another. I get this below error when I try to paste
a pageThe logs have not been really helpful even in debug mode. The same
issue happens when I try copy/paste assets from one location to another
When I start up a standalone AEM 6.5.6 instance and upload all my
content to it, then copy/paste page/asset works well.I have seen all the
...
Dear homies, We have been migrating AEM 6.3.3.8 to AEM 6.5.6.0. I am
following all the restructuring documentation as per the below link
-https://docs.adobe.com/content/help/en/experience-manager-65/deploying/restructuring/all-repository-restructuring-in-aem-6-5.html#workflow-modelsI
have restructured the models and scripts from /etc/workflow path to
their new respective paths as per the documentation above. The issue I
am facing is - After restructuring workflow models from
/etc/workflow/models...
Thanks you guys for your help!I have figured out what the issue was, the
documentation here is missing some details for on-premise AEM solutions
-I am using archetype 23 that is used for both AEM as a cloud service
and on-premise AEM 6.5. The documentation is only referring to the
updates for the cloud service.This is how I got it fixed for ui.apps
project and got the ACS AEM Commons bundle was available -
ui.apps/pom.xmlAdd a dependency for the acs aem commons content package
- com.adobe.acs
a...
I have been following the documentation on
https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.htmlWe
are upgrading AEM from 6.3.3.7 to 6.5.5. The acs-aem-commons package
works sweet in AEM 6.3 through code POM dependencies and we are using
shared component properties as an example. I have used Archetype 23 to
migrate code to new structure however I am not planning on using
ui.content package as I have pretty much all I need in /core, /ui.apps,
/ui.frontend(.react) project.Am...
