They create the links between the tables (two hasOne relationships), a search() method to find the destinations for a user, a sorting method to multisort based on the subkeys of the value passed in and the methods for updating the information already in the database.

That's it for now, feel free to download this tiny Smarty and Doctrine framework. Note that for this to work you have to put Smarty and Doctrine in the lib folder. There is a login interface involved, just click submit there without entering anything. There is also an SQL file in the trip_selector folder if you want to try this out with some test data (same as in the picture above).

Following our tutorials on uploading files and listing files, this tutorial will walk you through deleting files from a directory. This is done using the unlink() function.

Their example is pretty simple (as is the concept) - they show how to check to be sure that the file you want to remove isn't in use/open and then issue the unlink to remove it from the file system.

I've recently been wrapped up in an effort to design and implement a RESTful API using the Atom Protocol for a project at work. We are using the Zend Framework as the underlying framework for the project, so, in order to follow the Atom Protocol, I needed to support the HTTP methods PUT and DELETE

Since the Zend Framework has been playing such a prominent role in the development, he's been digging into the Zend_Rest_Server component code and isn't too happy about its support for PUT and DELETE. As a result, he's proposed methods that might help resolve things such as isGet, isDelete, isOptions and getEntityBody. He' even created a patch to make the needed changes.

A cookie is often used to store data which can be used to identify a user, for example, person's username. [...] In this tutorial, we will learn how to write, read and delete cookies in PHP.

They show how to create the cookie (with set_cookie) - both one that will timeout when the browser closes and one that stays after - how to read the value from them and how to remove them by setting the data in the past.

A canny data import technique that emerged from praxis, while working on the import of data-centered XML resources, is utilitizing the abilities of Xslt. The generation of the required SQL statements actually only needs a simple Xsl stylesheet which might import for an PHP XSLTProcessor object or pass to the xsltproc command line tool. Both further described approaches are based upon the libxslt library and are assuming the use of XSLT 1.0.

He starts with an example bit of XML that has the XSL stylesheet at the top that will be used to transform the data and the information to perform inserts on several "partner" values in the XML below. Following this, he creates a PHP class to load the file and apply the stylesheet.

He also mentions a few different approaches to the same problem - XSLTProcessor class approach returning a single SQL string , xsltproc approach and the XSLTProcessor class approach using the ability to use PHP functions as XSLT functions.

Previously we covered an all-at-once approach to indexing objects in your symfony app. But for some reason, people find the need to allow users to sign up, or change their email addresses and then all of a sudden our wonderful Lucene index is out of date.

Here lies the strength of using Zend Search Lucene in your app, you can now get the flexibility of interacting with a Lucene index, no matter how it was created and add, update and delete documents to it.

Instead of going the "clunky" route of having a cron job update the search information nightly, they opt for a method that updates the database whenever new content is added/updated/deleted. They change up the class they generated before and add methods to reindex whenever each method is run.

• An example of a "Soft delete" behavior implementation automatically in a current Model in your application.
• A new tutorial showing an update in the "Simple Form Authentication" implementation for your app.
• A method for advanced validation for your Models

I just wanted to drop another quick line saying that our favorite blogging engine has once again been updated. The developers deemed it important to get some more security fixes pushed out to the Wordpress users, so Wordpress 2.0.7 has been released.

Updates in this release include:

• a fix to wp_unregister_GLOBALS()
• Feeds now properly serve 304 Not Modified headers
• Deleting WordPress Pages no longer gives an '�Are You Sure?'� prompt.

In this fourth and final article covering the creation of a PHP invoicing system, we're going to put together the user management section. In this section we will be able to view all available users and do all the associated things like deleting or updating user details. We are also going to be able to add new users.

They start with grabbing the information of the current users of the system and listing them out. This allows simple modification and deletion of any of the users on the list. They give the code (and screenshots) for the user modification screen and show you how to set up an email reminder that sends out to the clients when a bill hasn't been paid.

You know how to get users to interact with a PHP application using a Web form, but sometimes e-mail is just more convenient. Maybe your users are using small devices like cell phones or interacting in a way that's not real time, such as subscribing to an e-mail list. Find out how to read and send e-mail by building a PHP Webmail application.

They cover connecting to the server, grabbing the information from a specific email inbox, pulling the data for a single message, deleting emails, getting a list of the current emails, and how to work with attachments and multipart MIME messages.

You'll need to log in to get to it, but it's a great example of how to work with email in PHP (more than just sending them with mail() or PEAR's mailer package).