"How about rewriting the link_to() and url_for() helpers to extract the ID," Bad ideea, 2 reasons. 1) you have to remove the url helper from your symfony lib. (if you have frozen the project ignor this step and check the 2nd step) 2) you would still have problems with this issue. I remember you that the link_to and url_for is using the allready generated routes.
Alecs On Tue, Oct 20, 2009 at 5:41 AM, Eno <[email protected]> wrote: > > On Mon, 19 Oct 2009, Jacob Coby wrote: > > > 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. > > How about rewriting the link_to() and url_for() helpers to extract the ID, > get the slug and rewrite the URL the right way? > > (Though I think fixing the templates would be quicker). > > > > -- > > > > > > > -- As programmers create bigger & better idiot proof programs, so the universe creates bigger & better idiots! I am on web: http://www.alecslupu.ro/ I am on twitter: http://twitter.com/alecslupu I am on linkedIn: http://www.linkedin.com/in/alecslupu Tel: (+4)0748.543.798 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
