It won't be recognized correctly as a page if you create an nt:unstructured.Why would you need to be concerned about this? If you create a page within AEM it automatically creates the correct node types - if you do it using code, then using the PageManager to create the page will also take care of ...
I ran into the same issue. I added the below code in the first line of my application and it worked correctly.org.apache.log4j.BasicConfigurator.configure();
I highly recommend using the Groovy Console (https://github.com/Citytechinc/cq-groovy-console) for this.You can write a script like below:getNode('/content/path/en').recurse { node -> rename node to node.name.toLowerCase() save() }And that'll take care of it for you.
You're posting to the author instance so make sure you are supplying a valid username and password to generate an authorization header. You can choose the authorization type of "Basic Auth" and once you supply the username/password, you can press "Update Request" to generate the header that's neede...
Maybe look at something that's already built and works: https://adobe-consulting-services.github.io/acs-aem-commons/features/widgets.html (the Multi Field Panel). It works great in both UI's.
You certainly can, you just need to add context. Try one of these.window.setTimeout(closePopup, ${comp.timeout @ context='number'});orwindow.setTimeout(closePopup, ${comp.timeout @ context='scriptString'});
kunal23 wrote... If you are on version greater than 6.1 then ConfigurationManagerImpl does not work and has been disabled. You should be using the ConfigurationManagerFactory interface to read the configurations in 6.1 instead of ConfigurationManagerImpl. https://docs.adobe.com/docs/en/aem/6-1/ref/...
I'm pretty sure you can achieve this by switching your parsys to be an iparsys - that will inherit the content down to the child pages, then on the pages you don't want a component, remove it, and the pages you do, keep it.