[sonata] Cannot associate menu node with route document

[dantleech]

Currently you can only specify a URL, Route Name, or Content Document (or rather all three at the same time if you like - would be neat to have a radio selector there, but thats another issue) and you cannot select a document from the route subtree.

[dbu]

is this just a sonata issue or also a model issue? anyways, having a reference to a route instead a content should not be too hard. with DynamicRouter we don't care, it can create the route from content or a route object.

anyways, don't think its critical but it should be easy to do.

[dantleech]

Its just a missing feature in Sonata Admin. Referencing the Route in the model works OK.

[sjopet]

we need to find a way to to select either a content document or a route document from the same form component.
Treebrowser or selectbox are possible options.

[dbu]

is this not just a question of setting a different base path for the selection widget? do we need an additional config option to allow to overwrite this? i think most of the time it makes more sense to select the content than the route document. for multilang, the route generator is going via the content anyways to find all route alternatives and pick the one with the matching locale if possible

[dbu]

ping

[lsmith77]

ping once more

[sjopet]

I'll have a look at this while working on the sonata bundle form types

[kminh]

Would like to have this as well, since not all menu items link to an actual content document (it can be an internal redirect route for tracking purpose for example).