-1

I was wondering what would be the best solution to handle routes in a CMS system. Currently I am using an URI property on my documents that I convert (through a RouteProvider) to a symfony route object. This seems for me the most simple and elegant solution, but is it?

When should you choose an URI property on a document for routes and when should you use specific route nodes that map to documents? What are the benefits etc.

By default CMF uses seperate route nodes/documents to map a route to a content document.

Thanks!

Wouter J
  • 41,455
  • 15
  • 107
  • 112
Steffen Brem
  • 1,738
  • 18
  • 29
  • answered on the symfony-cmf-users mailinglist where this question was cross-posted: https://groups.google.com/forum/#!topic/symfony-cmf-users/qZSDkZzPvCc – dbu May 18 '14 at 15:38

1 Answers1

0

The Symfony CMF can use both ways. The CMF provides 2 seperate bundles, ContentBundle and RoutingBundle. This has some reasons, one of which is that you are able to use only the RoutingBundle or only the ContentBundle, they are no longer tied together.

The Symfony CMF also provides a SimpleCmsBundle. This bundle demostrates how you can make one document for both things. That's done by creating a Page document which extends both Content and Route documents.

The main advantage of using 2 documents is that you can have multiple routes pointing to the same content. For instance, this makes it very easy to have i18n routes on a multi-language site. You just create routes like /hello, /bonjour and /gütentag and point them to the same Content document (which, on his part, has multiple languages of the content).

Wouter J
  • 41,455
  • 15
  • 107
  • 112
  • Just to add to the original question: yes its also doable to create routes on the fly. If you have the information anyways, i would go with the default CMF approach of mapping Route objects, but for special situations its totally legit to write a custom route provider that creates routes on the fly (from a legacy system for example) – dbu May 18 '14 at 15:40