I think there might be a bug in
that is preventing the normal node-based configuration that relies on
loading data-config-path during the ._start() method, because it sets
$editable.data('config') with the default rte plugins during the
.start() method before delegating to the ._start() method.
/libs/clientlibs/granite/richtext/js/rte/ConfigUtils.js defines a
loadConfigAndStartEditing() method that follows this...
Request for Feature Enhancement (RFE) Summary: The existing
aem-event-proxy-skyline source code distribution enforces assumptions
that are incompatible with many potential use cases, and future
development in this direction should relax these constraints on AEM's
role as an Adobe I/O event producer. Use-case: * Developers should be
empowered to fire custom Adobe I/O events from publishers, directly from
custom servlet code. For example, POST requests from customers
containing PII that must be se...
Request for Feature Enhancement (RFE) Summary: One-click support ticket
with attached telemetry for CM pipelines that fail after maven and code
check stages Use-case: AEM Customers in the support admin role should be
able to provide full context including transient environment state for
CM and Cloud Service product engineering when a pipeline failure occurs,
independent of CSE intervention/ticket triage.When non-deterministic
pipeline failures occur, the chain of escalation is Customer -> CSE ->...