I have tried the same thing in OOTB RTE and cannot replicate this issue. COuld be due to some customisation done to your RTE component. Please try the same in OOTB RTE, and check your custom code once.

For this you would need to write an outbound rewrite rule in dispatcher and/or publisher. In publisher it will be done by adding rule in /etc/mapping or in ResourceResolver Map Entries. https://techcookies.in/2017/03/27/basic-url-rewrite-rules-hiding-the-content-root-from-url/  For dispatcher , http...

For removing the <p> tag we have to create a node named htmlRules having jcr:primary type nt:unstructured. This node will have to create under the widget node which xtype is richtext. jcr:primaryType = “nt:unstructured” removeSingleParagraphContainer = “{Boolean}true”.

Hi @stiegjo22 , This is because AEM provides OOTB functionality for certain MIME types, in which thumbnail will get generated automatically. For the rest of the MIME types we would need to write custom logic to generate thumbnails for the assets.  

orderby=@jcr:path works for me. Gives results according to the order in the tree. Same as node.getNodes().

From the logs, I think the problem is with the template policy.I think the component you are trying to include is not allowed within the template policies. Try adding that component to the list of allowed components for the template.

The requirement is to get all pages with either jcr:content/category_id  or jcr:content/category_parent_id =54ceab56-c3b6-44c7-ae3f-08fc87af9045  As you stated, the requirement is to have OR. But what your query does is apply the AND function.You need to use the group.p.or=true in your query.Somethi...

Hi @Nandujee , Are you using OOTB form container without any customizations?Are you using any external URL in the action/ custom URL in your form action?Also, please check the core components version in your local and the environment which has this issue? Are they the same? 

Hi @ashish_mishra1 , These are the steps involved in DAM update Assets Workflow:If you want to see the details of each step, you can go to :https://<server>/editor.html/conf/global/settings/workflow/models/dam/update_asset.html  If there are a large number of assets involved, the workflow becomes a ...

Try adding the jcr:propertyselected = {Boolean}true