<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 02:56:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Rob Allen's Blog: Zend_Filter_Input / Zend_Validate Messages]]></title>
      <guid>http://www.phpdeveloper.org/news/8661</guid>
      <link>http://www.phpdeveloper.org/news/8661</link>
      <description><![CDATA[<p>
<i>Rob Allen</i> has been working with the Zend_Filter component of the <a href="http://framework.zend.com">Zend Framework</a> and has discovered a few things:
</p>
<blockquote>
The basic usage of Zend_Filter_Input is [a simple call to Zend_Filter_Input with the filter types and data to filter]. The problem is that the message you get out isn't always written as you would like. Consider the output if the body record is empty. The text isn't exactly what I would want to display to a user. To change it you pass in a messages parameter to the $validators array.
</blockquote>
<p>
There's a long list of these "messages parameters" and <i>Rob</i> <a href="http://akrabat.com/2007/09/14/zend_filter_input-zend_validate-messages/">includes them in the post</a> - things like NOT_ALNUM, CHECKSUM, QUOTED_STRING, INVALID_DASH and UNDECIPHERABLE_TLD (37 of them in all).
</p>]]></description>
      <pubDate>Mon, 17 Sep 2007 08:48:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Building the Index Page for a PHP Email Application]]></title>
      <guid>http://www.phpdeveloper.org/news/6668</guid>
      <link>http://www.phpdeveloper.org/news/6668</link>
      <description><![CDATA[<p>
DevShed is continuing their look at the creation of an email application with the <a href="http://www.devshed.com/c/a/PHP/Building-the-Index-Page-for-a-PHP-Email-Application/">third part</a> of the series. It looks at building the main index page of the application as well as some of the sub-pages that it links to for other features.
</p>
<blockquote>
The index page displays the newly downloaded messages in a table with five columns. These columns list (among other things) the date, subject and from field of the messages. 
</blockquote>
<p>
They break out the actions the page takes when someone logs in/views email - grab user info, grab messages, and display the navigation panels. Since they've already looked at the first of the list in a <a href="http://www.phpdeveloper.org/news/6621">previous tutorial</a>, they cover the last two, showing how to create the navigation (and some sub-pages) and how to grab all of the messages for the currently logged in user.
</p>]]></description>
      <pubDate>Wed, 08 Nov 2006 10:29:20 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Creating the Admin Script for a PHP/MySQL Blogging System (Part 3)]]></title>
      <guid>http://www.phpdeveloper.org/news/6516</guid>
      <link>http://www.phpdeveloper.org/news/6516</link>
      <description><![CDATA[<p>
DevShed continues their look at the creation of a simple blogging script with <a href="http://www.devshed.com/c/a/MySQL/Creating-the-Admin-Script-for-a-PHP-MySQL-Blogging-System/">part three</a> of the series (<a href="http://www.phpdeveloper.org/news/6410">part 1</a>, <a href="http://www.phpdeveloper.org/news/6468">part 2</a>) - the creation of an admin utility to work with the contents of the blog.
</p>
<blockquote>
The idea is to give the owner of the blog the ability to manage the blog by being able to remove users and articles as required, or to alter the status of users by upgrading them to admin status or banning them. It is also a place where the administrator can start new topics that will then garner their own replies.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/MySQL/Creating-the-Admin-Script-for-a-PHP-MySQL-Blogging-System/">go through</a> the creation of the main admin script (functionality managed with a switch statement, including other external PHP files) and the functions that go in each of those individual files to make things work - managing messages, managing users, and managing categories.
</p>]]></description>
      <pubDate>Tue, 17 Oct 2006 11:23:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Adobe Developer Source: Using PHP and Flex to Browse a MySQL Database]]></title>
      <guid>http://www.phpdeveloper.org/news/5839</guid>
      <link>http://www.phpdeveloper.org/news/5839</link>
      <description><![CDATA[<p>
The Adobe Developer Source has posted <a href="http://www.devx.com/Adobe/Article/31923">a new tutorial</a> showing how to, with the combination of PHP and Flex, to browse the contents of a MySQL database.
</p>
<blockquote>
One critical element to remember about programming with Flex is that it cannot connect to a database directly - it requires some form of middleware in order to access data. You'll be using PHP in order to generate the XML files that Flex will use to manipulate the data from the database.
</blockquote>
<p>
PHP plays the middle-man in <a href="http://www.devx.com/Adobe/Article/31923">this lengthy tutorial</a>, passing XML messages back and forth between the Flex application and interpreting it into MySQL queries and results. They take the PHP script through, step by step, to ensre you know exactly how it works. Next up is the Flex, complete with the code listing to create the simple database browsing application.
</p>
<p>
There's explainations, screenshots, and even a little ActionScript here and there, but in the end, you'll have a light, simple database browser to view the contents of your table.
</p>]]></description>
      <pubDate>Thu, 20 Jul 2006 14:12:31 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Nexen.net: Error Messages in PHP (a Search)]]></title>
      <guid>http://www.phpdeveloper.org/news/4577</guid>
      <link>http://www.phpdeveloper.org/news/4577</link>
      <description><![CDATA[PHP can throw out some pretty cryptic error messages sometimes, and those new to the langauge might have a difficult time understanding what they relate to. Well, Nexen.net has created a guide to the errors to help you make your way through them (as mentioned <a href="http://www.nexen.net/news/gen.php/2005/12/28/4892,0,0,0,0.php">in this post</a>).
<p>
<quote>
<i>
The errors that PHP throws can sometimes be confusing and mysterious. It outputs them in an effort to make debugging your scripts easier so you can go and correct the error. To help with deciphering them, we have created a guide by looking at the source code for PHP versions: 4.0.0, 4.0.6, 4.1.2, 4.2.3, 4.3.6 and 5.0.0RC2. versions 4.3.6 and 5.0.0RC2.
</i>
</quote>
<p>
On <a href="http://www.nexen.net/erreurs/">the tool</a> they've created, all you need to do is enter in the error code number that the script spits back and it will show you the relevant information. It also has a listing of some of the samples below it to help you narrow it down quickly if you already know what you're looking for.
<p>
The site and the tool are all in French.]]></description>
      <pubDate>Thu, 29 Dec 2005 07:04:09 -0600</pubDate>
    </item>
  </channel>
</rss>
