Projects frequently encounter stack overflow errors which are caused by cyclic view inclusions due to particular constellations of content and template structures, like self targeting teasers. Now, the CAE checks for such cycles and breaks them with a detailed ViewException .

Unfortunately, the check is not absolutely reliable, but may produce false positives. (A reliable check would require View objects to support equals. We did not want to go that far.) Known patterns for false positives are:

There are no known false positives in the standard Blueprint, therefore the check is active by default. If you encounter such cases in your project, you can switch off the check by setting view.cyclecheck=false in the CAE's application properties. With the check being disabled, the CAE behaves backward compatible.

(CMS-6450)