As Gábor Fási pointed out, the issue could be related to the BOM (byte-order mark).
Copy your source code into a new file and choose UTF-8 (without BOM) as the file's encoding. The byte-order mark is only necessary for UTF-16 or UTF-24 encoded files. This should solve your problem. Regards, Chris 2009/9/11 MrGlass <[email protected]> > > I'm sorry garakkio, I was mixing up the job examples. Still, as I > stated in the first post, the variable being passed in this case is in > fact an object. I am relatively certain the url_for command is being > done correctly, as it works 90% of the time. these encoding issues > sound like they could be the problem. > > Simply changing the format in notepad++ did not help. I am going to > retype some of these in VI this afternoon, hopefully that will remove > any chance of encoding issues occurring. > > Just a thought: could the encoding issue be with my database/data, as > opposed to the templates? > > On Sep 11, 4:59 am, Garakkio <[email protected]> wrote: > > Please read tutorial again: the second argument is supposed to be an > > OBJECT, not an array. > > > > On Sep 10, 3:10 pm, MrGlass <[email protected]> wrote: > > > > > 'post_pretty_url' is the name for my URI, yes. and the second > > > parameter (according to the jobeet tutorial) is supposed to be an > > > array of values needed for the url. See > > > herehttp://www.symfony-project.org/jobeet/1_2/Doctrine/en/05#chapter_05_o... > > > for the section of tutorial I got this from. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
