<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>indeedle &#187; PHP</title>
	<atom:link href="http://indeedle.com/blog/category/web/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://indeedle.com</link>
	<description>blogging the indeedle way</description>
	<lastBuildDate>Thu, 26 Aug 2010 08:16:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Error Messages</title>
		<link>http://indeedle.com/blog/2010/08/04/error-messages/</link>
		<comments>http://indeedle.com/blog/2010/08/04/error-messages/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 06:40:22 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://indeedle.com/blog/2010/08/04/error-messages/</guid>
		<description><![CDATA[I had a complete geek]]></description>
			<content:encoded><![CDATA[<p>I had a complete geek moment over the weekend. Ended up working on my side project I&#8217;m doing in my spare time, and I ended up writing my error management classes.</p>
<p>Inspired by the weird, wonderful and wacky errors found online, I decided my exception handler would also do the same. So what it now does is log the error + details to a file, then display one out of many random messages. The way the site is set up means output is captured before being sent, so if I run into an exception I can discard the built output and display the customized error page instead.</p>
<p>So far I came up with the following (inspired by online sources).</p>
<ol>
<li>A message telling the user to sit very still. Once they move their mouse a new message appears, complaining that they moved and interrupted the process, and that the server was going into a huff.</li>
<li>A request to read the following End User Agreement, followed by a long string of random gibberish.</li>
<li>A video from Youtube (showing Glee&#8217;s &quot;Over the Rainbow&quot; cover).</li>
</ol>
<p>Having a lot of fun coming up with these. Hopefully they make the error experience a little better.</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/08/04/error-messages/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/08/04/error-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More Geekiness (Auto Signature)</title>
		<link>http://indeedle.com/blog/2010/07/11/more-geekiness-auto-signature/</link>
		<comments>http://indeedle.com/blog/2010/07/11/more-geekiness-auto-signature/#comments</comments>
		<pubDate>Sun, 11 Jul 2010 02:08:07 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[gaia]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[sweetnleo]]></category>

		<guid isPermaLink="false">http://indeedle.com/?p=160</guid>
		<description><![CDATA[Some new geekiness going on.]]></description>
			<content:encoded><![CDATA[<p>Some new geekiness going on. I have a journal/blog over at SweetnLeo.com, where I talk about things relating to GaiaOnline. I wanted a way of making this available inside Gaia, so I came up with this.</p>
<p><a href="http://sweetnleo.com/"><img class="alignnone" title="SweetnLeo Journal" src="http://i.sweetnleo.com/s/j" alt="" width="400" height="60" /></a></p>
<p>It&#8217;s an image that shows the last 4 blog titles. How it works if I have a script that uses MagpieRSS to pull the feed from the blog, and then using PHP + GD I generate a simple image. When I make a blog post, it pings the update image script, meaning when I add a new entry the image will update.</p>
<p>It gives me a way to show what&#8217;s going on. Now to make it more pretty (as it&#8217;s just plain text right now).</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/07/11/more-geekiness-auto-signature/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/07/11/more-geekiness-auto-signature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Object Oriented Fun</title>
		<link>http://indeedle.com/blog/2010/05/17/object-oriented-fun/</link>
		<comments>http://indeedle.com/blog/2010/05/17/object-oriented-fun/#comments</comments>
		<pubDate>Mon, 17 May 2010 06:22:00 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[oo programming]]></category>

		<guid isPermaLink="false">http://indeedle.com/object-oriented-fun-144/</guid>
		<description><![CDATA[Currently my attempt is to]]></description>
			<content:encoded><![CDATA[<p>Currently my attempt is to rewrite my progress so far in a more OO manner. What I&#8217;ve previously done is use classes and objects, but infrequently. Let&#8217;s see if I can do this better, third time around.</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/05/17/object-oriented-fun/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/05/17/object-oriented-fun/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>phpbb3 + Flyspray Part 2</title>
		<link>http://indeedle.com/blog/2010/03/01/phpbb3-flyspray-part-2/</link>
		<comments>http://indeedle.com/blog/2010/03/01/phpbb3-flyspray-part-2/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 02:53:18 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[dokuwiki]]></category>
		<category><![CDATA[flyspray]]></category>
		<category><![CDATA[phpbb3]]></category>

		<guid isPermaLink="false">http://indeedle.com/?p=111</guid>
		<description><![CDATA[In my previous post I]]></description>
			<content:encoded><![CDATA[<p>In my <a href="http://indeedle.com/phpbb3-flyspray-109/" target="_self">previous post</a> I mentioned how I wanted to bridge phpbb3 and Flyspray. Well, I&#8217;ve done that, but due to the way Flyspray works, it was basically a complete pain.</p>
<p>I love Flyspray, I really do, but I think it is time I moved on to a new bug tracking system. Unfortunately though I don&#8217;t know of that many (if you do, definitely please contact me through the comments!). I&#8217;ve tried Trac, but on the host I use it is an absolute nightmare to get installed. What I&#8217;d really like is a simple PHP-based system like Flyspray, but one that does get updated regularly.</p>
<p>The trouble I had with Flyspray is I basically had to hack it to get it working with my forum. In the end I get phpbb to do the authentication (on each page load), and if the Flyspray user doesn&#8217;t exist it manually creates it.</p>
<p>It definitely isn&#8217;t the ideal solution, the DokuWiki bridge that someone else (awesome person) wrote works perfectly, but that comes down to DokuWiki being easier to modify with plugins.</p>
<p>So yes, if you are interested in bridging Flyspray and phpBB3, it is possible. However it basically is bypassing all of Flyspray&#8217;s authentication and saying &#8220;This is the ID of the logged in user&#8221;. You also have to rename their Database and User classes, since they clash with phpBB.</p>
<p>All in all, if you&#8217;re looking for a bug tracking system that can easily bridge with a forum, look for something else.</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/03/01/phpbb3-flyspray-part-2/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/03/01/phpbb3-flyspray-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>phpbb3 + Flyspray</title>
		<link>http://indeedle.com/blog/2010/02/25/phpbb3-flyspray/</link>
		<comments>http://indeedle.com/blog/2010/02/25/phpbb3-flyspray/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 06:12:36 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[dokuwiki]]></category>
		<category><![CDATA[flyspray]]></category>
		<category><![CDATA[phpbb3]]></category>

		<guid isPermaLink="false">http://indeedle.com/?p=109</guid>
		<description><![CDATA[I am currently working on]]></description>
			<content:encoded><![CDATA[<p>I am currently working on a mini-project, and part of it requires a forum as well as a wiki and a bug tracking system. I have already set up phpBB3 with Dokuwiki, and they&#8217;re bridged so the accounts are linked. That&#8217;s absolutely great!</p>
<p>What I&#8217;m currently trying to work on is installing Flyspray, and then writing my own bridge between Flyspray and phpBB. The way I theorize it, I&#8217;ll create a hidden group in phpBB called &#8220;flyspray&#8221; or something, and then when you access Flyspray it will check to see if you&#8217;re a member of that group using phpBB&#8217;s functions.</p>
<p>We&#8217;ll have to wait and see if it works, but if it does I&#8217;ll see about making the bridge public.</p>
<p>Wish me luck!</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/02/25/phpbb3-flyspray/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/02/25/phpbb3-flyspray/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trust Nobody</title>
		<link>http://indeedle.com/blog/2010/01/16/trust-nobody/</link>
		<comments>http://indeedle.com/blog/2010/01/16/trust-nobody/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 04:22:38 +0000</pubDate>
		<dc:creator>Cody</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[sanatise]]></category>
		<category><![CDATA[xkcd]]></category>

		<guid isPermaLink="false">http://indeedle.com/?p=71</guid>
		<description><![CDATA[One important lesson when developing]]></description>
			<content:encoded><![CDATA[<p>One important lesson when developing applications (I&#8217;m focusing on websites here, but this applies to all types of applications) is to ditch user trust.</p>
<p>In a nut shell, <strong>do not trust any input you receive from a user</strong>. Seriously, do not assume it is clean and good, treat all user input (whether it be cookies, text from a text box or something else) as potentially dangerous. Check it, filter it, escape it.</p>
<p>Never let input from a user go straight into your database or on to a page without it being filtered. If you let it straight into the database you leave yourself open to SQL Injections and other attacks.</p>
<div class="wp-caption aligncenter" style="width: 543px"><a href="http://imgs.xkcd.com/comics/exploits_of_a_mom.png" rel="lightbox[71]"><img class=" " title="xkcd - Exploits of a Mom" src="http://imgs.xkcd.com/comics/exploits_of_a_mom.png" alt="" width="533" height="164" /></a><p class="wp-caption-text">This is why you should clean up all input. (Click for bigger version)</p></div>
<p>Keep that in mind when you are developing an application, any and all user input needs to be checked out, torn to pieces, ripped apart, put back together before being considered safe.</p>
<hr />
<p><small>© 2008 - 2010 for <a href="http://indeedle.com">indeedle</a>. All rights are reserved. | For more information please visit <a href="http://indeedle.com">indeedle</a>. |
<a href="http://indeedle.com/blog/2010/01/16/trust-nobody/">Permalink</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://indeedle.com/blog/2010/01/16/trust-nobody/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->