Can you please check the logs and post back what are you seeing? Additionally, you could explore the usage of the Checkbox group which have already the functionality you are looking for, see more here: https://www.aemcomponents.dev/content/core-components-examples/library/adaptive-form/checkboxgroup...

Hi,    There is a reason for that. Integrating React into an Adobe Experience Manager (AEM) project can be tricky for several reasons, primarily due to the fundamental differences between how AEM traditionally works and how React applications operate. Here are some of the challenges you might encoun...

You need to use the Resource Mapper to achieve such behavior. Below, you can find excellent articles with examples explaining how to use it, and once you configure the mapping you can verify this is working as expected using this URLhttps://<*host*>:<*port*>/system/console/jcrresolver:   Hope this h...

Hi,    It looks like the JS (clientlibs) are not properly constructed/minified.   I would suggest narrowing down the issue to determine if it was caused by the ServicePack, which I assume you applied (based on the title of this thread). You can do this by installing your code into a fresh AEM instan...

Yeah correct, it looks like you have a metadata attribute already for unpublish assets, so you could take advantage of that field (prism:expirationDate).

Hi @Adilos-Cantuerk, Unfortunately, when an asset is scheduled for activation, there is no record stored in the metadata. The way this works is that a Sling job (an asynchronous operation) takes care of that activity in the future. The references are stored under dynamic paths generated based on the...

Hi,    I assume you are talking about the Sling model exporter, if so, yes, you can actually configure the extension and selector(s) @Model(adaptables = Resource.class, resourceType="/apps/myApps/components/myComponent", defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL) @Exporter(name =...

Hi,    I think you could use the cq:template node, where you can pre-defined default properties, That way, if your user does not input anything, the property will be already there by default, the drawback with this is that this will work only if you drop the component for the first time, if this is ...

Hi,    I think you could potentially explore the "integrated SPA" option from this article: https://www.albinsblog.com/2021/11/single-page-applicationspa-design-patterns-in-aem.html. Here you have several design patterns and options available when working with SPA.

Correct, as I mentioned earlier, in such scenarios, you will need to write a custom function that detects whether the link is external, a document, or internal, and appends the extension accordingly. Something like the example below. Please note that the example below is illustrative and must be upd...