David Buchmann

as far as i know, nobody is working on this at the moment. @dantleech would you happen to know anything more?

Interesting discussion you have going here! I lean towards the role solution. Some thoughts: - Multisite can be handled by a loader knowing about the site context base path in...

oh, but for the "base paths" that we use, structural nodes would be a good thing to have. like the routing will so stop to work if you move /cms/routing...

i re-labled this from "bug" to "UX" and will edit the title to not confuse ourselves or people looking at the issue tracker.

the problem is that all bundles that provide documents have those documents implement ChildInterface coming from CoreBundle, as well as the publish workflow interfaces. ContentBundle (and BlogBundle) do RouteReferrersInterface and...

not really. the extensions use the interface to detect what is supported. but the document works fine without the workflow or the admin extension.

i am tending towards saying we release with the current state and try to figure out how to best do this with enough time. a compromise that makes nobody really...

No, the chain Router can be used with the bundle, allowing you to tag routers to be in the chain. Btw none of the cmf bundles declares a dep on...

with that definition the RoutingBundle does not depend on core bundle: https://github.com/symfony-cmf/RoutingBundle/blob/master/Model/Route.php does not have any dependency. what does have dependencies is the Doctrine\Phpcr\Route document, and the doctrine specific classes...

there actually was already an issue #174 about this. i will close that issue as this discussion is more current.