Last modified: 2011-08-18 03:16:49 UTC
Complicated and likely fringe problem: http://thethirdturn.com/w/index.php?title=John_O'Neal,_Jr.&oldid=144332 <- ugly output. This normally works fine but it appears if the page name has an apostrophe in it, this templating system breaks. What appears to be happening is that when {{PAGENAME}} is passed, it becomes the first parameter ({{{1}}}) here but it's not returning any values: http://thethirdturn.com/w/index.php?title=Template:SeasonResultForm&action=edit . Somewhere, the encoding is breaking with the {{PAGENAME}} magic word. When I directly substitute a name in (the end-around on the John O'Neal, Jr. page), this works fine, properly returning values that correspond to say the property named John O'Neal, Jr. Name. It just doesn't like Property:{{PAGENAME}} Name when {{PAGENAME}} contains an apostrophe.
Also seems to choke on periods in property names in a similar way. Oddly not for an ampersand. I know this is a relatively minor and fringe bug, but this seems like it would be a rather simple encoding issue somewhere. I would appreciate it receiving a look very soon.
* Correction to Comment #1 - "Choke on periods" ... Periods that are part of the {{PAGENAME}} variable. I do not believe this is an issue with normal properties with periods in them.
Same basic issue as bug 16474