Hi,    This is a known issue in acs-commons: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2146. this is apparently solved, so please try a newer version of acs that include the fix mentioned in the thread.   Hope this helps

Hi, I don't think there is an official approach on how to do this, but in reality, it is not that complicated. You just need to keep in mind that you simply need to invoke a correctly formatted URL and/or load the proper JS (if you are using one of the viewers). With that in mind, you can check how ...

Hi, If this is local and you don't have anything new, it is easier to start a new instance, just delete the crx-quickstart folder. If you cannot delete the instance, you could try checking the bundles and ensure everything is in "active" state, go to /system/bundles. Also check this thread as well: ...

Right, the attribute will tell which resource to look in a specific path, but you need to load such resource in the path, so the AEMcontext can get it

You should create the page and load its properties as part of the aemContext so below line actually can retrieve the page's properties: pageManager.getPage(productModelPage); Try something like this https://wcm.io/testing/aem-mock/usage-content-loader-builder.html:   Hope this helps 

Hi, How are you mocking the page? Can you post some code to see what is going on?

Hi, Did you check this is not ACL's related issue? I guess you are using queryBuilder UI with the admin user   

Hi,Your code seems ok, it sounds to me that the issue is because of Mockito and Java incompatibility versions, can you check this thread: https://stackoverflow.com/questions/41050029/mockito-cannot-mock-this-class Also share which dependencies you are using.   Hope this helps.

Hi, I think you can ask directly adobe support about utility, please open a support ticket and ask for this.

@roberto_eff Please clarify your question for the community, and kindly post everything in English for this community.