I have to agree with @pix3l, this is an incredibly annoying default. The security and performance reasons pointed to by @roelbeerens are true but you shouldn’t have to rewrite a controller to get such basically functionality. We built out website from one of your templates using dynamic zones and as pointed out by @Georg this breaks those without either putting in a redundant populate=* in every page query or rewriting the controller. Surely having some property on a relation field that allows users to choose from within the content type whether that relation populates by default would be much more user friendly and intuitive, though I can’t speak for the difficulty of implementing it. I really hope you alter this and at the very least make it clear in the migration guide that this is a change from v3
6 Likes