I believe the solution is to simply get the underlying DOM element from
the JQuery object. For example, the code below is to interact with a
checkbox created within a div with class
"rte-dialog-columnContainer";var jqueryCheckbox =
$(".rte-dialog-columnContainer coral-checkbox");// then getting the
underlying element (assuming there's just one) from the JQuery
collection:var coralCheckbox = jqueryCheckbox.get(0);// calling various
API methods/attributes:coralCheckbox.checked =
Hi,Are the two authoring instances in the same geographical region? if
using AWS, same region, same DC YesShould digital assets from Author A
be read only in Author B?No it should be bi-directionalIs there any
requirement to be able to edit assets created in the other author
instance?No I think editing should only be possible on the source
systemYou could use a shared datastore between the two instances if they
were co-locatedWould this allow us to have seperate customisations for
things like si...
@Sutty, have you considered restricting author access, so that no
content author could login to AEM(this would fix your problem straight
away!)?Alternatively, you could try to use
in most cases your user/content author would win(unless you really,
restrict your content author functions to bare minimum and aggressively
parse all request...
if you are using a boilerplate approach to maintain all your content for
reference component, then here is what you can do;bind activation event
listener to activation of just that boiler plate.Refer following article
for more details around replication listener -
pages that contains reference component pointing to boiler plate
content.programmatically issue dispatcher flush for all those
pages.Reference code for programm...
A shared S3 datastore can make all the binaries to sit in the S3 rather
than the instances. By setting the S3 configurations to make the
nodestore to keep minimal data, you can make almost all coming from S3.