SOLVED!!!!
Sorry, I've been at this for awhile, this is def the most annoying
debug I have ever done (what with the invisible characters and all).
The link has a slug at the end. The slugify function is part of a
different class, which has a different file and location. I had missed
this file when I went through things fixing the encoding. I just
Switched it to utf8 without bom, and I no longer get random chars.
I have no idea why it was only showing for the first link, or why it
was appearing at the front of the link instead of before the slug.
Regardless, my bug is gone.
Thanks to everyone who helped.
-MrGlass
On Sep 13, 2:57 pm, MrGlass <[email protected]> wrote:
> I set notepad++ to use utf-8 without BOM by default, and went through
> copying the code for all the relevant template files and the
> routing.yml file. This has gotten rid of the characters that were
> popping up throughoutt the code, but unfortunately my original problem
> remains: the first url_for() generated link still has that same
> character, causing a broken link. see this for an
> example:http://pastebin.com/m678f0a96
>
> Are there other files I should do this to?
>
> Thanks for all the help so far
>
> -MrGlass
>
> On Sep 11, 2:27 pm, Christoph Häckel <[email protected]> wrote:
>
> > 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
-~----------~----~----~----~------~----~------~--~---
