Thanks to @Harwinder-singh, we will implement a custom rollout config to handle nl_be, and zh_cn links rewriting. Regarding second issue that I mentioned above (rewriting fragmentVariationPath), I found that Adobe released a fix in Release 13665 (2023.09):SITES-14773: Experience Fragments: Link Refe...

Thank you for your answer. I understood your idea. You described how XF is localized in the template. The XF Sling model has conditions for localizing the XF link.This makes the XF MSM concept unusable for XF, which is not in the template. For example, we have an XF teaser that can be reused across ...

Let me describe our content management flow. We have a 3rd-party translation provider. It's responsible for creating language copies.If we want to introduce new language (to create a language copy), we will add /content/site/language-masters/de as content source, and all XF source paths (e.g. /conte...

Hi, community, On your project (AEM Release 2023.9.13665.20230927T063259Z), we follow a well-known content structure to manage pages and XFs. Content: /content/site/language-masters | |__de |__en - language copy of /content/site/language-masters/de ...

We noticed, that re-indexing by AEM has a very low speed on traversing nodes - up to 100-200 nodes per second. Offline re-indexing - thousands of nodes per second. We managed to fix this issue by the next plan:Create checkpointStop AEMRun oak-run in console mode:  sudo java -jar compaction/oak-run-1...

Hi everyone, We have an AEM project where the repository size is ~ 90 GB (recently it started to grow rapidly to 190GB).AEM version - 6.5.15Apache Jackrabbit Oak - 1.22.13On the project, we faced issues with very long re-indexing of indexes after the deployment. This process took ~ 4 hours and consu...