On the Cloudways blog they've posted a tutorial showing you how to create a simple contact form that emails when someone fills it out and the information they submitted.

Laravel is well known for providing multiple solutions for a problem. This is one of the main reasons of the popularity of the framework. Popular Laravel solutions cover routine functionality such as authentication, sessions, routing, and caching.

Contact Us forms are another routine functionality that is a requirement of more or less every website. In this article, I am going to demonstrate how you can easily create a contact form in Laravel with email. To understand the functionality of Laravel mail function. I suggest you read my previous article on sending emails in Laravel.

The author then walks you through the installation of a new Laravel application on the Cloudways service. He then shows how to install the "Form" package (laravelcollective/html) and enable it as a service provider. Next up comes the database configuration and the creation of the table to handle the data submitted via the "Contact Us" form. The model is then created to work with the table, the route is added to show the form (and handle the submission) as well as the matching view and controller. The post wraps up with the commands and configuration you'll need to send the emails and an example of a "mailable" class to handle the email's construction.

New on the ITNewb.com site today there's a tutorial looking at making your forms a bit more "spam free" without resorting to CAPTCHA images.

Most anti-spam methods used by websites today are annoying at best. They use impossible-to-read captcha images, or they make users jump through some kind of hoop to get the email address instead of just clicking on it. This can mean lost sales and opportunities for you, because each hurdle turns away more users.

The trick uses some CSS and Javascript to hide a form field (display:none) and check on the submit to ensure that it's empty. The email address is the output of a Javascript document.write() as well, preventing those pulling the information off of your site without Javascript support (like some automated tools) to miss it completely.

NETTUTS.com has posted a new tutorial on how to create and use your own CAPTCHA image to help protect the submission of your form.

Ever get hit with spam through the contact form on your personal site? Well, here is a short tutorial on how to build a custom captcha to keep the bad guys out.

The tutorial's broken up into eight steps:

• captcha.php and the Session
• Random String
• Storage Folder and Colors
• Building the Image
• Image Final
• contact.php
• HTML & CSS
• Validate

Plenty of screen shots and example code/HTML/CSS are included.

This new article from PHPBuilder.com talks about getting started with one of the newly introduced components of the Zend Framework (in collaboration with Adobe) - the Zend_Amf interface.

To introduce this new Zend Framework extension and give you a look inside its functionality, I show you how to build a Flex application that pulls data from a MySQL database using PHP. First, you set up the application to use XML, the conventional cross-platform data-exchange method. Then, you change the code to use AMF and custom classes.

They give you the tools you'll need to set up the right environment (including version 1.7 or later of the Zend Framework and Adobe Flex Builder) and the steps to create the simple application. It uses a MySQL backend to store contact information ad a basic Flex interface to pull that information back out for display.

In a new blog post today Jonathan Snook shows how to create a contact form for your CakePHP application (version 1.2).

Most contact forms take a name and feedback from a user and mail it off to the administrator but don't store any information in the database. This tutorial will show how to use CakePHP's models, even when no table is being used.

He shows how to define the model class, set up the mapping of columns to named elements and the code to handle the submit. It just sends a basic email with the contents of the form with a few validation rules to ensure it's not abused. Simple stuff...

In an effort to help employers/recruiters/etc find the PHP people they're looking for, the PHPClasses.org website has launched their PHP Professionals Directory:

So, I thought to myself, instead of recommending people, I could provide a place where available PHP professionals looking for work could list. Then companies can look up the list of available professionals and contact them directly.

Developers are divided first by country, then by name and have all the contact information you'd need (address, zip, location, phone) to get in contact with the developer. You can also add your own profile to the directory to make it easier for others to find you.

In an effort to help employers/recruiters/etc find the PHP people they're looking for, the PHPClasses.org website has launched their PHP Professionals Directory:

So, I thought to myself, instead of recommending people, I could provide a place where available PHP professionals looking for work could list. Then companies can look up the list of available professionals and contact them directly.

Developers are divided first by country, then by name and have all the contact information you'd need (address, zip, location, phone) to get in contact with the developer. You can also add your own profile to the directory to make it easier for others to find you.

On the Zend Developer Zone, there's a new tutorial talking about one developer's method for creating a link between Flex and Drupal to create a data entry form.

Why Flex? Because I'd like to be able to put the widget on any site and Ajax has security issues there. Web browsers, quite rightly, ensure that Ajax pages only request data from their server of origin. So it's much harder to host an Ajax widgets on external sites without kludges like IFrames or Script tag data transit. Flex allows data access from different servers. So it's far easier to write widgets that can be hosted externally.

You'll already need Drupal installed to start working with the tutorial - he chose Mac OS X as his platform of choice, but this setup will work with any installation that supports Flex. He uses the AMF protocol to interface with the PHP scripts on the backend (via AMFPHP) and a small update will need to be made to Drupal to get it to cooperate.

The rest of the tutorial shows how to create the Flex interface - making a simple information form that takes in a user's name, address and phone number and updates the Drupal contact information for them.

On the Zend Developer Zone, there's a new tutorial talking about one developer's method for creating a link between Flex and Drupal to create a data entry form.

Why Flex? Because I'd like to be able to put the widget on any site and Ajax has security issues there. Web browsers, quite rightly, ensure that Ajax pages only request data from their server of origin. So it's much harder to host an Ajax widgets on external sites without kludges like IFrames or Script tag data transit. Flex allows data access from different servers. So it's far easier to write widgets that can be hosted externally.

You'll already need Drupal installed to start working with the tutorial - he chose Mac OS X as his platform of choice, but this setup will work with any installation that supports Flex. He uses the AMF protocol to interface with the PHP scripts on the backend (via AMFPHP) and a small update will need to be made to Drupal to get it to cooperate.

The rest of the tutorial shows how to create the Flex interface - making a simple information form that takes in a user's name, address and phone number and updates the Drupal contact information for them.

In his search for "contact grabber" classes, Jonathan Street came across one posted to the PHPClasses.org website recently, the Contact Grabber class, and decided to give it a shot and report back his findings.

I haven't tried it yet but apparently it can connect to hotmail, yahoo, gmail, orkut, rediff and myspace. It is an impressive collection of scripts. [...] Generally speaking I wouldn't have a problem with the script being included in another project. In fact I would encourage it. In this instance though there are a few problems.

He breaks it up into a few different kinds of issues: inaccuracies, updates, licensing problems, and that the author wouldn't make contact back to Jonathan about some of his problems.