You need to modify the search logic to create query with exclude path also, something like   1_property=property-name 1_property.value=property-value path=/content/mysite/en group.1_group.p.not=true group.1_group.path=/content/mysite/en/testfolder1 group.1_group.path.self=true

You have to use LogLevel Directive [1] to track logs at apache level, setting logs at debug level will allow you to track request processing.   [1] https://httpd.apache.org/docs/2.4/mod/core.html#loglevel 

Firstly, I do not see any relation b/w asset visibility in the side panel and its published status. Ideally, assets should be visible inside panel as soon as you upload them in Author instance, if not, try the following: Check if your bundles are in an active stateCheck if the indexing of assets is ...

I have used the below approach for one of my clients: Set a variable at CDN "Akamai-Viewer-Country", CDN will set this variable with country code like "au", "us", "de"Add apache rewrite rule file to set a variable COUNTRY like SetEnvIfNoCase ^Akamai-Viewer-Country$ (AU) COUNTRY=auSetEnvIfNoCase ^Aka...

Design dialogs in static templates are used to enable editors to set Template level configurations for a component, which get saved under the design folder for the site.   The same concept is carried in the Editable template, where design dialogs are used to enable editors to set template-level conf...

@olsalas711 What is the exact problem you faced?

I recommend overlaying the tab core component and updating its HTL file to add additional parsys on top also and control it by CSS. Regarding the code, you have to duplicate code "which is rendering bottom part".

Have you checked the emulator on the demo site, if it's giving same error there?

One option you can consider is to use tags. Assign a tag to each xFragment disclaimer. Now on your page, you can select the disclaimer tag which needs to be rendered on this page. Benefits you will see with this approach are: Editors can control which disclaimer to be placed on the pageEditors can a...

So BPA tool is used for both purposes, it evaluates your code against standards, and/or prepares your code to be cloud-ready. So feel free to use BPA.   Alternatively, you can set up and use Sonar Rules [1] to check code against standards.   [1] https://github.com/wttech/AEM-Rules-for-SonarQube