Jordi Sala Morales

it was already moved to PageBundle, here we just need deprecate + removal

Maybe we don't have to deprecate this block indeed... We tried to deprecate because the edit form is using a collection type for children. That collection type is coming from...

Well we might have to do something like: ``` $form->remove('collection') $form->add('collection')... ``` and redefine all the options...

Changing the default options for collectionType looks like a bc break to me.

We want to revert the page bundle to start using this class, and not deprecate it. Question is: can we do better to avoid removing and re adding a field...

Can you provide a PR?

I dont think it belongs to this bundle. IMHO Gtm and seo are different topics.

It also happens for hybrid pages right? I mean hybrid and dynamic are almost the same, just dynamic have also parameters on the route.

Better as a feature, it is not a bug.

Thank you @eerison