I found the issue, the alias on about-us (.../about-us/shopping-with-us) was the same as the node name. Apparently the AliasesPreprocessor.mergeExistingMappings cannot handle this because it will cause a stackOverflow error caused by the recursive call of mergeExistingMappings.

Unchecking 'Optimize alias resolution' did not have any effect, I still get the same error as before. The weird thing is that the error does not happen on all pages, for some pages of the same site (that also include aliases) and pages of other sites in our setup it seems to work.

I am experiencing issues when publishing some pages that have an alias on them, I am publishing the following path .../about-us/shopping-with-usThe json looks like this:about-us:{     "jcr:primaryType":"cq:PageContent",   "jcr:mixinTypes":[        "cq:LiveRelationship"   ],   "jcr:createdBy":"admin"...

Yea that is what we are doing now, creating live copy variations and referring to the LiveCopy pages in those variations. This solution works but is still not really that great, I hope Adobe can fix this.

I deleted the page in the LiveCopy and triggered a rollout to the LiveCopy again. It did not work, the 'founder-link-component' is still linking to the blueprint page.

bump

I am having trouble wrapping my head around an issue concerning experience fragments and linking. Let my simplify our setup.- A blueprint page called 'team' @ '/content/platform-blueprints/company/en/team'     - Page contains a simple link component that refers to '/content/platform-blueprints/compa...

Thank you, it works now

If I use @optitional instead of the strategy it works yes. I want it to work with the strategy

I've written my own custom annotation to find a property on the current resource and to return it. This annotation works fine when the property is available on the resource, things go wrong when it is not found:Annotation:@Target({ElementType.FIELD})@Retention(RetentionPolicy.RUNTIME)@InjectAnnotati...