I created another page using the template and managed publication in the future worked for this page.

I am getting the following error when a managed publication of a certain page is executed:16.10.2017 09:18:00.573 *ERROR* [JobHandler: /etc/workflow/instances/server1/2017-10-12/scheduled_activation_274:/etc/workflow/packages/generated-package8] com.day.cq.replication.Agent.publish-a Error while bui...

Here is the dialog for our 'call-to-action' component (simple button that has linking functionality):So you would just add the extra brand textfield and concatenate both in final rendering (sightly)?

I was thinking about that approach but that would mean that we have to extend each components dialog with this extra field. Isn't there a way to extend/modify the resource resolver (or factory?) logic?

HeyWe already saw this being using internally by AEM, for example: http://localhost:4502/editor.html/content/platform-blueprints/site/nl.html  but we did not like this way of url structuring for our live site.GreetingsJeroen

I have a very specific use case and I am having a hard time implementing it, maybe someone here can help me out. Let me explain my setup first:We have a type of page called a brand-as-category, this url can look like this: Category pages are real pages that live in the node structureA brand-as-categ...

It was caused by the QueryEngineSettings, .../system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQuery… The limits can be set at runtime using JMX, domain org.apache.jackrabbit.oak type QueryEngineSettings, attribute names LimitInMemory and LimitReads.

We've updated our AEM from 6.1 to 6.3, everything is up and running except our alias resolving.Things I've noticed:- /content/site/shoe (sling:alias=foot) --> /content/site/foot does NOT work if 'resource.resolver.optimize.alias.resolution' is enabled in the apache sling resource resolver factory co...

I am looking for an option to replace an asset rendition, this is available in the classic UI but not in the new one. Am I missing something?

I am not trying to create a custom grid component really :S I am just trying to get my custom parsys to work on page level:My example - General page:....<sly data-sly-resource="${'content' @ resourceType='/apps/company/components/layout/grid-row'}" data-sly-unwrap></sly>...It seems that the above is...