So you're talking about doing it outside of AEM, and then manually adding the property to a component instance? If that's the approach that's best for you and your business requirements, good luck to you, hopefully you don't take a vacation and someone needs these updated.
darren.hoffman wrote... Thank you for your quick reply. Could you please describe the reasoning behind your opinion? I think it will be time consuming to create 6 * 230 = 1380 entries in Generic Lists, and the benefit of Author modifications seem irrelevant when these will change very infrequently. ...
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'});
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.