Hi @martinkastler    Editors/Authors should make it a practice that while making a complex or a large content change create a version of that page. This helps in having a backup of content page. Although yes having an indicator to notify user that multiple users are working on the same page would be...

Hi @samihan  1. Check if all the bundles are running.2. When you click on the search icon do you see any console errors?  Thanks

Hi @mrtestermanitest  Please do the below checks :1. See if the relevant code is deployed. Check if the component is present in CRXDE under /apps.2. Cross check the componentGroup. 3. On template level check if that componentGroup is allowed. If yes see if the other components from that group are vi...

Hi @shail860510  To the best of my knowledge there is no Out of the box way to do so.  One way that I can think of is that you create a custom workflow for deactivation of Page.  Steps : If page is deactivated check if the path is of Root note.If YES -> Only allow user with admin privileges to deact...

Create a custom component that extends the RTE component: You can create a new component that extends the existing RTE component. This custom component will include your video plugin. Define a video plugin: Create a new plugin to add to your custom component. You can define the plugin using the Co...

Hi,   I have a Custom component that includes a custom Rich Text Editor component using granite/ui/components/coral/foundation/include.   The RTE has a property required=true(Boolean) which is inherited in my Custom component on include.   But in custom component the RTE is not an required field.   ...

#chatgpt3 #adobeexperiencemanager #chatbot #aichatbots   Video Demo : https://drive.google.com/file/d/1bvuI03FlXSXdUY1gncI3u1uFZR22_Uz_/view?usp=sharing   As ChatGPT continues to be a buzz word around the internet, an idea intrigued me in how ChatGPT's potential can be leveraged in Adobe Experience ...

Hi @smahesh    Can you provide more details on the issue?   Thanks,

Hi @Mayank_Gandhi any response on this from the Product team.

Hi @anika_agarwal    You can rollout the language copies to "/content/website/us/en" and "/content/website/us/fr". That's a valid scenario.    Thanks