Hi, Glad it worked. 1. Legacy UI (JSP-based)renditions.jsp has hardcoded checks for common MIME types (image/jpeg, image/png, etc.)WebP/AVIF are not included in those checks by default.2. Browser Support LagAt the time AEM 6.5 and earlier were released:WebP: Not supported in all enterprise browsers....

Hey, I think the problem is occurring because of useFixedInIn AEM, when using useFixedInlineToolbar=true, the RTE toolbar config is cached and reused across fields, unless additional isolation is enforced. Try this -Use Distinct uiSettings to Isolate ToolbarsEmbed explicit toolbar configurations und...

Thanks for the information - I wasn’t aware it was deprecated. I’ll check that.

Hi @PovEim ,I think AEM’s standard Metadata Schemas only apply to folders and assets, not to collections. To apply metadata to collections, use Metadata Profiles -  a feature designed for assets and collections. Steps to Apply a Metadata Profile to a Collection: Go to AEM - Tools - Assets - Metadata...

Hi @GarfieldKlon222 , I think this is happening because AEM does not natively preview WebP or AVIF renditions in the Assets UI, even though it supports generating and storing them with correct MIME types. When you click on these renditions, you see the message Preview is not supported for the select...

Hi @有哉半田 , I think there may be a problem of dispatcher not forwarding the header. Follow below steps for it -  1. Make sure your CDN/app server passes X‑Forwarded‑Host and that Dispatcher is configured to forward it. In your dispatcher.any, under /clientheaders/clientheaders { "X-Forwarded-Host" ...

Hi @vhochsteinTef ,I think this is behavior in AEM as a Cloud Service with Dispatcher: it intercepts 404 status codes and redirects to the AEM error handler (like /content/404.html), instead of returning your custom JSON response. You can try to follow these steps -  1. Update Dispatcher Config to A...

Hi @burhanuddinj ,AEM reuses RTE config globally. When RTE fields have the same node name (like text) or lack unique config scopes, the toolbar leaks across components.You can try following solutions - Use different RTE field names in dialogse.g., ./overview, ./details (not both ./text)Use unique di...

Hi @Nitesh-Chavan ,Yes, you can control execution of HTL code based on the AEM environment (Dev, Stage, Prod) by making use of run modes and exposing them via a Sling Model or Use-API class to your HTL. public class EnvironmentCheck extends WCMUsePojo { private boolean isDevOrStage; @Overr...

Hi @veerareddyc1015 You can try these points:- Use the AEM Style System – Enable it in your component (cq:styleGroups).Create separate editable templates for each project under /conf/project1 and /conf/project2.Define different policies in each template:Project1: Styles = White, GreyProject2: Styles...