On Oct 19, 2009, at 6:19 PM, Eno wrote:
> > On Mon, 19 Oct 2009, Jacob Coby wrote: > >> I've been working on a symfony 1.2 app that includes a CMS. >> Unfortunately, the CMS system generates approximately 3000 routes >> programmatically across 4 different module/actions. Unfortunately >> there is no sort of pattern to the routes and the cms uses the >> routing >> system to generate the final url. For example, cms/index?id=23 would >> get translated to /about_us. And cms/subpage?id=56 would get >> translated to /another_page. > > Sounds like a bad design. Using slugs would be a good way to > refactor that > stuff to use just a couple (one?) routing rule. There are a plenty of > examples of this in the docs. It is a bad design, no doubt about it. I had no part of the design or implementation, nor do I know the history of why it was been implemented this way. I've only been tasked with deploying it and making sure it can stand up to the projected load. I'm quite familiar with how symfony routing works. I've been using symfony professionally since 0.63. I'm trying to find any solution other than going through and redoing all of the url_for and link_to calls to support slugs. > > > > -- > > > > > -- Jacob Coby --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
