One of our customer has migrated a lot of content (assets and pages)... they have about 1.5 million assets and about 4 million site pages. Part of the sites are generated by XML Add-on. Problem:With this much load obviously Author (AEM 6.4) is slow for authoring. And sometimes crashes. Solutions:The...

Thanks for the tips @Bharat1. This is happening on live .com site.. we're not seeing anything if we access the site other than the primary .com url2. To debug chrome.. after a few seconds, browser freezes making it unusable. So cannot see what's happening.3. Does not happen on Author4. Will check we...

What could be the issue when a certain page is loading.. midway the browser hangs/freezes, and making the browser unusable. It does not allow us to to right-click and inspect. This is happening on a page where we have a component that loads content from an experience-fragment.Setup:A page has a link...

Thanks Arun Patidar.For reference, i've added the code/fix to WKND here Enabling Users to build Experience Fragments - Added Empty XF Template Type and Sample Template and XFPage component by …

Thanks Vish.dhaliwal we were able to identify that XF needs that property from this post. Only We.Retail example had this and is not documented anywhere on the documentation pages. Or if it is, i'm missing it.

Yes, i agree and adding them did solve the problem. But this has to be done via Code or crx/de and not via AEM UI.When users/template-authors are building an Editable template on the AEM UI.. they cannot use them unless a "developer" is involved.So i see the process as..Build an editable template in...

Issue: On AEM 6.4.. When trying to refer an Experience Fragment inside an "Experience Fragment Component" on a sites/page, the "experience fragments without any "cq:xfVariantType" property do not show up. The Experience fragment functions normal.As of now we have added this via code but there is not...

Thanks for suggestions.1. Recompiling did not help.2. And i do not see any Errors in browser (tried Chrome & Firefox)Here's the issue/solution:An "Experience Fragment" needs to be built in a certain way only.. as follows:An Experience Fragment <-- Editable Template <-- Template Type that uses xfpage...

Version: AEM 6.4 - 6.4.4.0 Why does "Variation" option does not show up in a new Experience Fragment being built using default "HTML 5 Page" template that we're trying to create? While it shows if we use We.Retail's template? What are we missing?Steps -- Does not show upSettings > Configuration Brow...

Fundamentally Experience Fragments are consumable content which can be used "as-is" and "makes senses on its own". Also detailed here Adobe Experience Manager Help | Understanding Content Fragments and Experience Fragments in AEM                               If an Experience Fragment lives within a...