summaryrefslogtreecommitdiffstats
path: root/examples/server/lib/render/idpXrds.php
Commit message (Collapse)AuthorAgeFilesLines
* Revert "[ remove closing ?> tag from all files ]"Luke Shepard2009-05-271-1/+2
| | | | | | This reverts commit a2bdc5c6129ff11b1c1e29a207b1b80153ac6fb0. I'm going to stop playing in bce's fork, and start messing in my own. Sorry for the mess Brian :)
* Revert "[ correct errors in removing trailing ?> ]"Luke Shepard2009-05-271-1/+1
| | | | This reverts commit f963a700e4440074a5b86d382789e75795206482.
* [ correct errors in removing trailing ?> ]Luke Shepard2009-05-271-1/+1
| | | | | | | | In the last commit, I over-aggressively removed closing PHP tags. While I dislike the practice of using close tags within templates, it is how this library works, so let's put them back. Checked that all PHP compiles with "php -l".
* [ remove closing ?> tag from all files ]Luke Shepard2009-05-271-2/+1
| | | | | | | | | | Reviewed By: Will Norris Facebook has a policy to not have closing ?> tags at the bottom of PHP files. It can unintentionally introduce newlines which causes ridiculous bugs. This is recommended in the Zend style guide: http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html
* [project @ Fix user XRDS]tailor2008-02-041-2/+2
|
* [project @ Fix IDP XRDS in example server: advertise correct type]tailor2008-02-041-3/+1
|
* [project @ Use type URI constants in generating XRDS]tailor2007-04-061-2/+8
|
* [project @ Fix 2.0 IDP NS URI]tailor2007-04-051-1/+1
|
* [project @ Example server overhaul; add OpenID 2 features]tailor2007-03-221-0/+28