You can see that in June the traffic started picking up as I began to write more frequently.

Here are the top 5 articles by page views for the same time period:

1. Parsing jQuery’s sortable(”serialize”) Method with PHP (and symfony)
2. Using Symfony Partials In DHTML and Ajax
3. OmniFocus, It’s Not You, It’s me… Really
4. Simple Symfony Login Form Example
5. Dynamically Loading Symfony Applications Via Subdomains

I find it interesting that although the Symfony login form example was posted relatively recently, it’s already in the top five. Also, the only article in the top five that doesn’t deal with Symfony is my mini OmniFocus review.

Well, here’s to another year…

On this day we want to give you another great present, the symfony + Doctrine Book which documents the specific functions of the integration between symfony and Doctrine as well as some commonly used Doctrine functionality.

(Via the Symfony Blog.)

As our early Christmas present, we finalized the 1.2 release of symfony after some weeks of hard work.

Be sure to check out what’s new in Symfony 1.2 as well as the upgrade instructions for upgrading from Symfony 1.1. If you’re upgrading from 1.0, it is recommended that you first upgrade to 1.1. Also, the 1.2 documentation and book will be an invaluable resource if you’re new to Symfony 1.2.

Also, those familiar with Symfony will probably remember the Askeet tutorial from several years ago. It was written as an easy, step-by-step tutorial that showcased Symfony and allowed new users to build an application from start to finish while learning about the framework. Over the years the Askeet tutorial has begun to show its age so to celebrate the release of Symfony 1.2 the Symfony team has put together a new Advent Calendar style tutorial called Jobeet. It’s a great way for both Symfony novices and pros to learn about Symfony best-practices right from the creators of Symfony.

(Via the Symfony Blog.)

Being a release candidate now means that we are no longer doing any changes besides bug fixing and documentation, lots of documentation. Of course with very good reason we do an exception but generally that’s it. This means that you will also have no problems upgrading from this release candidate to the final version. If you haven’t tried 1.2 yet because you were afraid of such changes, you no longer have an excuse.

(Via the Symfony Blog.)

<?php

class LoginForm extends sfForm
{
  public function configure()
  {
    $this->setWidgets(array(
      'username' => new sfWidgetFormInput(), 
      'password' => new sfWidgetFormInputPassword() 
    ));

    $this->widgetSchema->setNameFormat('login[%s]');

    $this->setValidators(array(
      'username' => new sfValidatorChoice(array('required' => true, 'choices' => array('admin'))), 
      'password' => new sfValidatorChoice(array('required' => true, 'choices' => array('some_password')))
    ));
  }
}

The key here is using sfValidatorChoice to ensure that the input matches some predefined keys (“admin” and “some_password” in this case).

For completeness, here’s the action file:

<?php

class authActions extends sfActions
{
  public function executeLogin(sfWebRequest $request)
  {
    $this->form = new LoginForm();

    if ($request->isMethod('post'))
    {
      $this->form->bind($request->getParameter('login'));
      if ($this->form->isValid())
      {
        // authenticate user and redirect them
        $this->getUser()->setAuthenticated(true);
        $this->getUser()->addCredential('user');
        $this->redirect('home/index');
      }
    }
  }

  public function executeLogout()
  {
    $this->getUser()->clearCredentials();
    $this->getUser()->setAuthenticated(false);
    $this->redirect('@homepage');
  }
}

And the template file loginSuccess.php:

<form action="<?php echo url_for('auth/login') ?>" method="POST">
  <table>
    <?php echo $form ?>
    <tr>
      <td colspan="2">
        <input type="submit" />
      </td>
    </tr>
  </table>
</form>

And of course, you’ll want to turn on security for the application in security.yml:

default:
  is_secure: on
  credentials: user

We are very happy to announce the symfony 1.2 beta 2 release, which now supports the admin generators for both Doctrine and Propel. No need to use Propel for sexy admin generator anymore.

This will also be the final Beta release before Symfony 1.2 stable is released.

The sfTaskExtraPlugin is a plugin maintained by the symfony core team. It adds a number of useful tasks to your symfony command line to help streamline your workflow. This plugin is relatively young, so I will just be discussing those tasks that we’ll be using for today’s Plugin Developers Day. I should also note this plugin requires symfony 1.2.

In addition to some basics of setting up Doctrine and Symfony, he also covers a bit of the nested forms implementation that was recently updated in Symfony 1.2. Admittedly I didn’t think much of this feature when reading about it initially but seeing Jonathan’s implementation with translations was an eye opener.

1.2 may sound like a minor release, but we’ve actually stuffed in quite a few upgrades. Our focus was on the Forms and ORM, which combined result in the new Admin Generator. Secondary focus was to streamline the symfony API, and allowing a better foundation for plugins. As you can see this is a natural continuation of the strategy we took when building 1.1.

Symfony 1.2 marks another milestone in Symfony’s development. The core Symfony team has done a lot of work transitioning from the older, more tightly coupled Symfony 1.0 code branch into a much more flexible, powerful and decoupled Symfony. As I’ve mentioned previously, one of my favorite aspects of the new Symfony is the ability to pick and choose which components you need in order to build your own sub-framework for those tasks that are speed or memory intensive.

Be sure to read the rest of the official blog post for more. If you’ve been using Symfony for some time and you just want to know what’s new, then there’s also a document just for you.

Today, I have merged the new_admin branch into the 1.2 one, which means that symfony 1.2 now sports a brand new admin generator, based on the form framework.

Be sure to read the rest of the article which has an overview of the new features as well as the updated tutorial in the Symfony book. It looks like Doctrine users will have to wait a few days while the Propel version is stabilized before they port the work to Doctrine.

I, for one, have been waiting for this for a long while.