<?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>Thu, 24 May 2012 15:10:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Get involved in the PHP community: 5 easy steps that take less than 5 min. each]]></title>
      <guid>http://www.phpdeveloper.org/news/14987</guid>
      <link>http://www.phpdeveloper.org/news/14987</link>
      <description><![CDATA[<p>
On the Zend Developer Zone there's a new post from <i>Cal Evans</i> about <a href="http://devzone.zend.com/article/12450-Get-involed-in-the-PHP-community-5-easy-steps-that-take-less-than-5-minutes-each">five ways to get involved</a> in the PHP community that take about five minutes each (and can both help you and the community).
</p>
<blockquote>
ome developers develop because it pays the bills. They don't want to be part of the community, they have other passions. I am ok with that, I don't want anyone involved who doesn't want to be. Other developers however tell me they didn't know the community existed, they don't know how to get involved or they are just too shy to step up. It is to this second group (and anyone who is already involved but wants more) that I want to talk to. If you want to get involved in the PHP community here are 5 quick ideas to get you going.
</blockquote>
<p>
His five things are simple and cover a lot of different media, from blogs to twitter:
</p>
<ul>
<li>Email your local PHP User Group and offer to speak.
<li>Setup a PHP tag on your blog.
<li>Submit something to <a href="http://devzone.zend.com/">DevZone</a>!
<li>Re-tweet something about PHP.
<li>Find at least one other PHP developer that is not involved in the PHP community and convince them to read this list and take action.
</ul>
<p>
He equates this last one to a "chain letter" but it's key to helping th community grow. It's all about people getting together around a language they love and sharing that with more and more people.
</p>]]></description>
      <pubDate>Thu, 19 Aug 2010 09:14:47 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[JoomlaBlogger.net: How to understand Joomla templates in five easy steps]]></title>
      <guid>http://www.phpdeveloper.org/news/14843</guid>
      <link>http://www.phpdeveloper.org/news/14843</link>
      <description><![CDATA[<p>
On JoomlaBlogger.net there's <a href="http://www.joomlablogger.net/joomla-tutorials/joomla-template-tutorials/understand-joomla-templates/">a recent post</a> that wants to help you understand the Joomla templating system in "five easy steps".
</p>
<blockquote>
There are very few tutorials on how to build templates. There are two books and a handful of other resources scattered around the web. So, we set out to build the very best template class we could. Here are first five sessions of the class: Joomla templates are not rocket science. You can learn how to build and modify them. We can show you how. Interested?
</blockquote>
<p>They break it up into the basic parts:</p>
<ul>
<li>Template setup and templateDetails.xml
<li>Index.php
<li>CSS/Cascading Style Sheets
<li>Images
<li>Security
</ul>]]></description>
      <pubDate>Fri, 23 Jul 2010 12:48:49 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Kevin van Zonneveld's Blog: 7 Steps to better PEAR documentation]]></title>
      <guid>http://www.phpdeveloper.org/news/12001</guid>
      <link>http://www.phpdeveloper.org/news/12001</link>
      <description><![CDATA[<p>
<i>Kevin van Zonneveld</i> has posted <a href="http://kevin.vanzonneveld.net/techblog/article/7_steps_to_better_pear_documentation/">seven steps</a> that you can follow to help the documentation for your PEAR class come out better and be more useful in the end.
</p>
<blockquote>
If you've written a <a href="http://pear.php.net/">PEAR</a> package, it's probably a good idea to submit some end user documentation. Here's how to do it.
</blockquote>
<p>
He explains what it is (XML in CVS, easily convertible with phpd) and how the process flows - save the current docs, add your own, build locally and submit to CVS. Here's his tips to help things go smoothly/turn out better:
</p>
<ul>
<li>Gather the prerequisites
<li>Save current documentation
<li>Try building the docs
<li>Write your own XML docs
<li>ReBuild peardoc
<li>Commit your XML
<li>(There is no seventh step - you're done!)
</ul>]]></description>
      <pubDate>Mon, 23 Feb 2009 11:11:55 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Smashing Magazine: 10 Steps To Protect The Admin Area In WordPress]]></title>
      <guid>http://www.phpdeveloper.org/news/11830</guid>
      <link>http://www.phpdeveloper.org/news/11830</link>
      <description><![CDATA[<p>
As all of the WordPress users out there know, the "admin" section of the installations is one of the most important areas of your site. That being said, it should also be one of the most well protected parts. <a href="http://www.smashingmagazine.com/2009/01/26/10-steps-to-protect-the-admin-area-in-wordpress/">This new article</a> from Smashing Magazine has ten tips that you can use to help protect you and your blog from prying eyes.
</p>
<blockquote>
The administration area of a Web application is a favorite target of hackers and thus particularly well protected. The same goes for WordPress: when creating a blog, the system creates an administrative user with a perfectly secure password and blocks public access to the settings area with a log-in page. This is the cornerstone of its protection. Let's dig deeper!
</blockquote>
<p>Here's their ten tips:</p>
<ul>
<li>Rename and Upload the wordpress Folder
<li>Extend the file wp-config.php
<li>Move the wp-config.php file
<li>Protect the wp-config.php file
<li>Delete the admin User Account
<li>Choose strong passwords
<li>Protect the wp-admin Directory
<li>Suppress Error Feedback on the Log-In Page
<li>Restrict Erroneous Log-In Attempts
<li>Keep Software Up to Date
</ul>]]></description>
      <pubDate>Wed, 28 Jan 2009 09:31:54 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Developer Tutorials Blog: RSS feeds in PHP: 3 simple steps to PHP RSS generation]]></title>
      <guid>http://www.phpdeveloper.org/news/9985</guid>
      <link>http://www.phpdeveloper.org/news/9985</link>
      <description><![CDATA[<p>
On the Developer Tutorials blog today, there's <a href="http://www.developertutorials.com/blog/php/rss-feeds-in-php-3-simple-steps-to-php-rss-generation-121/">a new post</a> talking about the "three easy steps" to making an RSS feed for your blog:
</p>
<blockquote>
Adding an RSS feed to your site is quick and painless, and can be done with pure PHP (and some kind of data source). After the jump, 3 simple steps to building an RSS feed in php.
</blockquote>
<p>
The steps are pretty simple - figure out what content you want to serve, set up the basic RSS XML structure, and loop through your data to push it in to the template and echoed out. Some simple example code is included.
</p>]]></description>
      <pubDate>Thu, 17 Apr 2008 08:47:50 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Nessa's Blog: Installing suPHP on cPanel]]></title>
      <guid>http://www.phpdeveloper.org/news/9188</guid>
      <link>http://www.phpdeveloper.org/news/9188</link>
      <description><![CDATA[<p>
On her blog today <i>Nessa</i> has <a href="http://www.v-nessa.net/2007/12/05/installing-suphp-on-cpanel">written up a tutorial</a> on getting SuPHP working along with cPanel on your system.
</p>
<blockquote>
I wrote this tutorial a while back and figured it would be good to post because suPHP is growing more popular as an alternative to phpSuExec. The instructions assume that you are on a Linux cPanel server and are familiar with how to install PHP, but do not want to use EasyApache's suPHP installer in WHM.
</blockquote>
<p>
It's a long process but a lot of it is just configuration changes and grabbing the right software. Every line of each of the config files you'll need to change is there ready to cut and paste into your files as well as the command line calls you'll need to make to configure/compile and move files to where they need to go.
</p>]]></description>
      <pubDate>Thu, 06 Dec 2007 12:06:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: Scalability and Responsiveness with Zend Platform's Job Queue]]></title>
      <guid>http://www.phpdeveloper.org/news/8097</guid>
      <link>http://www.phpdeveloper.org/news/8097</link>
      <description><![CDATA[<p>
On the Zend Developer Zone today, there's <a href="http://devzone.zend.com/article/2207-Scalability-and-Responsiveness-with-Zend-Platforms-Job-Queue">a new article</a> by <i>Dotan Perry</i> and <i>Shie Erlich</i> talking about what kind of scalability and responsiveness that the Zend Platform's Job Queue functionality has to offer.
</p>
<blockquote>
The <a href="http://www.zend.com/products/zend_platform">Zend Platform</a> Job Queue is used to make applications more responsive by allowing tasks to be performed on other machines (e.g.: dedicated machine), and scheduling tasks to a future time (usually to low-traffic hours). [...] Job Queue offers both a web-based management UI, and a programmer-oriented rich API, which allows embedding sophisticated logic into applications. This article will demonstrate basic usage of Job Queue, through an imaginary company wesellalot.com.
</blockquote>
<p>
They start by presenting a scenario where a simple cluster of machines behind a load balancer all work with the same database. Because of some of the tasks they want to perform, things could get overloaded very easily under a high load. Enter the Job Queue and their four step process to integrate it into this setup:
</p>
<ul>
<li>Step 1: Off Load to a Dedicated Server
<li>Step 2: Scheduling to low-traffic hours
<li>Step 3: Breaking down tasks using dependencies
<li>Step 4: A recurring cleanup job
</ul>
<p>
They also include an explanation as to why this method is preferable over just using croned scripts for the same purpose.
</p>]]></description>
      <pubDate>Thu, 21 Jun 2007 11:24:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Christopher Jones' Blog: Configuring and Running PHP's OCI8 tests]]></title>
      <guid>http://www.phpdeveloper.org/news/7599</guid>
      <link>http://www.phpdeveloper.org/news/7599</link>
      <description><![CDATA[<p>
<i>Christopher Jones</i> <a href="http://blogs.oracle.com/opal/2007/04/10#a112">shows us</a> today how to set up and run tests (using the built-in extension testing PHP has) to test the OCI8 functionality that that extension provides.
</p>
<blockquote>
<p>
The test suite can't test everything. You should test your applications with your new PHP too. This gives load and real-life testing not possible with PHP's script based test suite.
</p>
<p>
[...] The tests in ext/oci8/tests verify the behavior of the OCI8 extension. To run them follow these steps.
</p>
</blockquote>
<p>
There's <a href="http://blogs.oracle.com/opal/2007/04/10#a112">four steps</a> he gives that will help you check your Oracle compile installation including what the response of the test results will look like.
</p>]]></description>
      <pubDate>Wed, 11 Apr 2007 08:33:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Norbet Mocsnik's Blog: Setting Up DokuWiki with Simple Authentication]]></title>
      <guid>http://www.phpdeveloper.org/news/6931</guid>
      <link>http://www.phpdeveloper.org/news/6931</link>
      <description><![CDATA[<p>
<i>Norbet Mocsnik</i>, having just set it up himself, is <a href="http://norbert.mocsnik.hu/blog/archives/208-Setting-Up-DokuWiki-with-Simple-Authentication.html">sharing the steps needed</a> to get DokuWiki set up and working with a simple authentication system.
</p>
<blockquote>
I promised to investigate the steps needed to set up DokuWiki with the simplest authentication scheme for a friend and I thought others might benefit from it too, so here it is.
</blockquote>
<p>
There's about fifteen steps in all, including the download/install of the package and creating the basic functionality (like a simple Auth schema - he gives an example). Create the superuser and set up the desired restrictions and you're home free. If you want more information on authentication in DokuWiki, check out <a href="http://wiki.splitbrain.org/wiki:acl">this page</a> on the DokuWiki's wiki. 
</p>]]></description>
      <pubDate>Tue, 19 Dec 2006 09:02:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Ben Ramsey's Blog: Installing the Eclipse PHP IDE]]></title>
      <guid>http://www.phpdeveloper.org/news/6922</guid>
      <link>http://www.phpdeveloper.org/news/6922</link>
      <description><![CDATA[<p>
Wanting to try out something new in the IDE department, <i>Ben Ramsey</i> reached for the <a href="http://www.eclipse.org/php/">Eclipse PHP IDE</a> to see how it ran. His <a href="http://benramsey.com/archives/installing-the-eclipse-php-ide/">latest post</a> details the installation process he went through to get things up and running.
</p>
<blockquote>
I already had a working Eclipse installation that I had used to try out <a href="http://www.phpeclipse.de/">PHPeclipse</a> for Eclipse (not to be confused with the PHP IDE), so I didn't want to bother downloading a brand new full package of Eclipse that includes the PHP IDE and all its requirements. So, I set about on a tedious journey to figure out how to install PHP IDE using the Eclipse Update Manager. These are my notes.
</blockquote>
<p>
There's really only three main steps <a href="http://benramsey.com/archives/installing-the-eclipse-php-ide/">he went through</a>: disable PHPeclipse (if installed), install the other software needed by PHP IDE, and finally, install the PHP IDE plugin itself. That's it (assuming all goes well with the prerequisites).
</p>
<p>
You can grab the latest copy of the Eclipse PHP IDE from <a href="http://www.eclipse.org/php/">the project's website</a>.
</p>]]></description>
      <pubDate>Mon, 18 Dec 2006 16:34:00 -0600</pubDate>
    </item>
  </channel>
</rss>

