OK. So I know the orderlist controls the order that the config appears in the dropdown. But are you saying it also controls the order the configs are executed on a rollout trigger?

But if the order is simply the order it appears, does that mean that all rollout configs in /apps will always run before the ones in /libs? What if we need one in /libs to run prior to on in /apps? For instance the default standard rollout config used to be first in our order always.

Thanks for the reply, Sundeep. Unfortunately, I don't think the information you have provided is accurate. The /apps area is for any custom config that doesn't come as part of the core AEM install, whether that is blueprint or rollout configs. See https://experienceleague.adobe.com/docs/experience-m...

Since the 6.4 upgrade, rollout configs moved from /etc to various locations (/libs, /apps).  Before, we could set the order by reordering them in the miscadmin tools interface in Classic.  This would control the order that the rollout configs applied to a rollout, when multiple configs were added to...

I think the answer to this depends largely on your definition of "mobile".  On the sites I support, we define mobile based on a screen size. Our primary reason for targeting a screen size is to A) make sure that the user experience at that size is optimal and B) make sure we don't send unnecessary a...

I don't think that will work, because the override patterns match the URL in question.  It doesn't mean that it doesn't scan that content.

In the Day CQ Link Service OSGi configuration, there is an option to input Link Check Override Patterns.You can put in the URL patterns that match your non-AEM content and it would be preserved.  This is for the external link checker.You can leave the internal link checker active and it will flag th...

You have to create an MSM blueprint configuration in the Blueprint control center for the page in order for AEM to recognize it as a Blueprint.

Your LiveCopy content needs the Page Move rollout config on it.  It appears you have only the default config and you need to add page Move (moveAction) and have it trigger on rollout.

My organization uses the Coresecure-developed Brightcove AEM connector for several years now.  Brightcove apparently partnered with Coresecure to develop the connector, which is now maintained as "open source".  I use the quotes, because really Coresecure is the developer and posts it on git hub. Bu...