The point of identifying a primary publisher is to have a single Publisher handler things like sending notifications to users or analytics info to Adobe Analytics (if used).For example : if you leave all publish instances as primary and a community member sends another community member an inbox noti...

Direct Link :https://downloads.experiencecloud.adobe.com/content/software-distribution/en/aem.html#package=/content/software-distribu…

The dialog will try and use the 319x319 thumbnail rendition within the Dialog.If you're not seeing it, then I'm assuming you don't have that thumbnail.Check the DAM Update Asset workflow model and ensure that you're creating thumbnails for that asset typeCheers.

You should be able to use the Apache 2.4 x86 build on Windows so long as you own that Apache 2.4 is not supported on Windows from a Customer Care standpointPull latest 4.3.3 build from here : AEM Dispatcher Release Notes

https://downloads.experiencecloud.adobe.com/content/software-distribution/en/aem.html

It's a limitation with MS Word itself.This has been reported a number of times in regards to pasting into an RTE from Word. This has been documented on the Rich Text Editor Helpx documentation since AEM 6.2Using the Rich Text Editor to Author Content

Check the Namespace is defined in AEM. The XMP Metadata Writeback process will skip namespaces that aren't defined and not write that metadata to the file.

Actually I'm going to correct myself as I believe you can have Java classes that extend WCMUsePojo within the content repository.

Just checking.  Feel free to log a Daycare ticket to troubleshoot this further.

Did you just rename the JAR file, or did you increment the build in the POM files and re-compile?