Hi @watopin,
Try to use this:
private Optional<ContentFragment> contentFragment;
@PostConstruct
public void init() {
contentFragment = Optional.ofNullable(resource.adaptTo(ContentFragment.class));
}
And if this does not work too, define to refresh your bundles, as suggested he...
Hi @MarkECis,
I don't think so there is any limit to the number of redirects in a site, however there are factors and solutions that you should consider before implementing this.
These can be configured in AEM Publisher, Dispatcher or at CDN.
Please go through this page to consider your options ...
Hi @Ronnie09 ,
You can use Granite Validator for this purpose.
Please refer to the similar reply here - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/text-field-content-limits/td-p/366507
Here, instead of checking word limit, you can match the word with your require...
Hi @benbakos,
We did similar validation to match the path and resource type of content fragments and returned the error, if not found. Please see the steps below, may be you can just replace path with id:
Create a clientLib with category=dam.cfm.authoring.v2
with below js
(function(document, $...
Hi @Magicr ,
If I have understood your problem correctly, if the ldap provider is the same and under the same provider you have different users from different user groups, then this should not be a problem, as long as you have the same groups created in AEM too, users will be synced to those diffe...
Hi @Mel-11 ,
You can enable in-line references to other Content Fragments by checking the Allow Fragment Reference and configuring the Allowed Content Fragment Models in Multi-line text data type as shown below:
Can you please check if this option is available when you're rendering it as "mult...
Hi @Gunjan881 ,
Please go through all the details here - https://experienceleague.adobe.com/docs/experience-manager-64/assets/administer/xmp-writeback.html?lang=en
Hi @akhilraj ,
There are no restrictions on the content of the payload, but it's important to know that a JWT is not encrypted. So any information that we put in the token is still readable to anyone who intercepts the token.
Therefore it's important not to put in the Payload any user information ...