The richt-text editor of the AEM Content Fragment tool is very limited. What a lot of us are looking for, is how to add standard plugins, like e.g. "link", "image", "source" (to add e.g. SPAN) tag.Reading other posts, it seems we need to write JavaScript plugins for each feature ("links", "image", "source").Can anyone please share how to add the "links", "image" and "source" buttons? Is it configurable like when we use the RTE widget in a dialog? Or do we have to write a JS plugin for each of th...

Thanks, arunp99088702​. Yes, correct. The challenge however is the link provided in the workflow step (payload). If you work on an AEM Content Fragment and want to review the content fragment via workflow, then the payload link does not show the content fragment. It actually does nothing...I could of course add a "sling:resourceType" pointing to some GET.jsp to read the content fragment and display it, but that is quite cumbersome for an author creating content fragments with the AEM tool.I coul...

Yes, the link shows how to create an AEM Content Fragment. However, how do you review the content fragment in a workflow step? The payload has the link to the content fragment and will never have a link to another page containing the fragment.It's similar to an asset in the workflow step: clicking on the payload link will display the asset.If you look at the screenshot, you see that the payload link is not resolved propertly.

Another observation:If the folder exists in Assets, replication of that folder does nothingIf the folder is new and has not been replicated yet, the replication process only replicates the folder, not it's content.This is an indication that the "Publish" feature within the context menu of a folder in Assets has a bug, since the replication of a new folder actually works.

To summarize:Don't get confused with the deprecation of the Apache Sling JSON implementation. This was due to licensing issues.The org.json library is used in the CSRF servlet, and (not sure though) seems to not be wrapped.You can test if you have an org.json library overload issue with http://localhost:4502/libs/granite/csrf/token.json. If you get an error message, you must be loading an incompatible org.json library. In my case this happened by using org.json dependency.Best is to remove all o...

Thanks, Scott and once I have their answer, we can either recommend not to use org.json or do a write-up how to use org.json properly.

Yes, Apache encountered licensing issues with the standard org.json libraries and deprecated their "light JSON" implementation org.apache.commons.json. However, in this case the issue is that (according to the error message) the CSRF servlet seems to use the standard org.json libraries and if we use the same libraries, but a different version, we run into a conflict that has a huge impact on the behavior of AEM 6.2 and AEM 6.3In my case the solution was to replace all org.json libraries with an ...

Yes, but at the moment it seems more like defining a workaround for a major issue. Perhaps there is something I am missing like e.g. a statement somewhere saying I should not use org.json or so.The weird thing is that removing the dependency on org.json fixed the problem. But it also fixed other Touch UI problems like components not showing in the component list or drop-downs not opening. Maybe Adobe can take a look and share if it is indeed a bug or if there is something I am missing.