The error you're encountering is a common issue when trying to use Google OAuth2 libraries in AEM as a Cloud Service. The root cause is that the Google authentication libraries and their dependencies are not OSGi-compliant, which means they work during Maven compilation but fail at runtime in the OS...

hi @TraKill, If you are seeking a proven integration for AEM and Figma, the AEM Assets Connector is highly recommended and widely used; however, I could not find anything about pairing it with "Figma Buzz". References:AEM Assets and Figma integrationIntegrate AEM Assets with Figma  

hi @IainClucas,There is no default automatic link rewriting for internal URLs unless specified with custom mapping logic.You need to set up path mapping for internal paths to external site URLs in your configuration. Have a look at here. 

This is expected and not tweakable at the moment. For instance, all the features available under the context of Multi Site Manager for Sites would be very useful when managing both CF and XF.It may be helpful to create a post in the Ideas section where you describe your proposal, current situation w...

The log entries you’re seeing in your AEM Production environment are not necessarily harmful. Here’s a breakdown of what’s happening for each type of message.“resource has no content”This log message comes from the OOTB AEM libs/cq/Page/Page.jsp script and indicates that Sling attempted to resolve a...

I'm really excited about this! I can't wait to test it firsthand and see how it performs with some real use cases. Looking forward to exploring its capabilities and sharing my experience!

hi @niallr, This is expected and not configurable within the built-in filter framework. However, AEM provides two supported mechanisms to maintain persistent search criteria: Saved Searches and Smart Collections. It may be helpful to create a post in the Ideas section where you describe your proposa...

I believe the best course of action is to open a support ticket with Adobe regarding this issue. You can also inquire if my suggestion could serve as a temporary workaround until/if they will release a patch.

hi @VishnuRa5, Yes, you can absolutely keep common farm file code in a separate file and reference it in siteA_farm.any and siteB_farm.any.For Dispatcher farm files (.any files in conf.dispatcher.d), you should use the $include directive, which is the Dispatcher-specific syntax for including files.H...

Request for Feature Enhancement (RFE) Summary:Enhance the Content Fragment Models (CFM) console to support folder navigation and organization of models within nested folder structures.Use-case:Authors and developers often need to organize multiple Content Fragment Models logically (e.g., by business...