The problem: when visitors first come to our site, with no cookie banner interaction, the initial page view and some other analytics data items are not getting captured or tracked. This seems to be because the GPLR happens on a “window loaded” event type which needs the adobedtm tag to load instantl...

Unfortunately there is no correct answer here as it seems the route I was attempting to take and the specific outcomes I needed are not possible. 

If I understand you correctly, this would only solve the issue temporarily for a selected span of time, and not a permanent solution moving forward when authors may need to move pages at any given date. Part of the "move" operation also includes the crx:replicate privilege that must exist as part of...

Thanks for the suggestion, but I am hoping for a solution that does not require additional assistance from an admin or another user. While this is a good suggestion, we have almost 40 authors and over 3500 pages, so not too feasible for our situation. I wasn't sure if there was some Access Control E...

I've created a situation where authors are running into permission issues when trying to move pages under certain conditions. To manage access, I set up group ACLs that limit author permissions to specific content paths, allowing them to only edit, publish, and perform similar actions within their d...

Sorry, I worded my previous comment strange. What you just explained is exactly how I had things structured, per the documentation, and the build was still failing. I had all .context.xml files defined, as well as all filter root paths defined. That's was what so confusing to me as why it kept faili...

Interesting. So even if I am defining all levels of filter roots within the ui.app.structure pom's filevault-package-maven-plugin file per documentation, like so:  <filter><root>/apps/cq</root></filter>  <filter><root>/apps/cq/core</root></filter>  <filter><root>/apps/cq/core/content</root></filter>...

Hi thanks for the reply,  But I am not sure it relates specifically to my case. My errors were showing as a result of trying to build the package with maven, prior to any type of installation. Within my code structure, I had specified each of the node types within each .content.xml file for the foll...

I discovered the issue, but the resolution does not make sense to me. In the filter.xml file I had:<filter root="/apps/cq/core/content/nav/tools/general"/>and changed to:<filter root="/apps/cq"/> Can someone explain how having the first filter path would through the errors mentioned above? Or were t...

I am attempting to add new content to the "tools" > "general" tab within aem. To get the node structure accurate, I have overlaid the node directory /libs/cq/core/content/nav/tools/general, then created the necessary node underneath general for my content.  The issue is when I try to recreate this s...