$this->y = 150;
$description = wordwrap(strip_tags($product->getDescription()), 110, "<br />");
 foreach (explode("<br />", $description) as $i => $line) {
     $page->drawText($line, 65, $this->y - $i * 12, 'UTF-8');
}

Dit onderzoek hebben we beoordeeld gekregen met een 8 en daar zijn we dan ook blij mee. We hebben ons best gedaan om zo nauwkeurig mogelijk te werk te gaan, maar kunnen niet garanderen dat het foutloos is.

Lees hier het onderzoeksrapport


jQuery.validator.addMethod("elfproef", function(value, element) {
var sum=0;
for (i=1; i<10; i++) {
amount=value.charAt(i-1);
sum+=amount*(10-i);
}

if (sum % 11==0 && value.length==9) {
return true
} else {
return false
}
}, "Vul hier een geldige bankrekeningnummer in.");


With Symfony I have worked with Doctrine regularly and in this blog I’ll show you how to use Doctrine for your own component in Joomla. Doctrine is an Object Relational  Mapping framework and offers you a persistence library. This not the holy grail and you should determine  if you need the extra overhead and if you are comfortable with it.

The first step

I’ll start with an clean Joomla 1.6 install from the Joomla website. Also I installed Doctrine ORM from the Doctrine website. I unpacked the archive in  a new folder in the Joomla folder libraries.The structure in this new folder would be the same as the archive, so you get a Doctrine folder and a bin folder in the libraries/doctrine folder.

By the way, we live in 2011 and the current release of PHP is 5.3.5. Doctrine and the implementation I show you here assumes you use PHP 5.3. If you still use PHP 5.2 you seriously need to work on the upgrade of that projects.

The example

I’m going to provide you a very simple example. The most important thing I want to show you is how to implement Doctrine in your Joomla project, not how to use Doctrine. The documentation on the Doctrine website is of high quality and should give you enough information to get going.

We are writing a new component called Bugs end hold one entity called ‘Bug’. It has five attributes. ID, title, description, notificationDate and solvedDate. In the controller I’ll show you some examples how to use it.

Setting up the defaults

It is possible that you want to use Doctrine on multiple components you are going to write. This is the reason why I choose to add Doctrine to the libraries folder. In this folder we are going to add two files. One is an interface to provide a generic interface, the other is a bootstrapper to get Doctrine going. First the easy stuff, the interface.

The interface looks like this:

<?php

interface JoomlaDoctrineController {
public function setEntityManager(Doctrine\ORM\EntityManager $entityManager);
}

?>

Nothing spectacular  here, lets move on.

Doctrine needs to have some basic configuration to get going. We need to tell Doctrine where it can find the entities and where it needs to place the generated proxies. Here is the implementation of JoomlaDoctrineBootstrapper:

<?php
/**
 * Configuration class to integrate Doctrine into Joomla.
 *
 * @author pderaaij <paul@paulderaaij.nl>
 */

use Doctrine\Common\ClassLoader,
    Doctrine\ORM\EntityManager,
    Doctrine\ORM\Configuration,
   Doctrine\Common\Cache\ArrayCache;

if( !class_exists('\Doctrine\Common\Classloader')) {
    require_once dirname(__FILE__) . '/../doctrine/Doctrine/Common/ClassLoader.php';
}

class JoomlaDoctrineBootstrapper {

    const APP_MODE_DEVELOPMENT = 1;
    const APP_MODE_PRODUCTION  = 2;

    private $applicationMode;
    private $cache;
    private $entityLibrary;
    private $proxyLibrary;
    private $proxyNamespace;
    private $entityManager;
    private $connectionOptions;

    public function __construct($applicationMode) {
        $this->applicationMode = $applicationMode;
    }

    public function getConnectionOptions() {
        return $this->connectionOptions;
    }

    public function setConnectionOptions($connectionOptions) {
        $this->connectionOptions = $connectionOptions;
    }

    public function getProxyLibrary() {
        return $this->proxyLibrary;
    }

    public function setProxyLibrary($proxyLibrary) {
        $this->proxyLibrary = $proxyLibrary;
    }

    public function getProxyNamespace() {
        return $this->proxyNamespace;
    }

    public function setProxyNamespace($proxyNamespace) {
        $this->proxyNamespace = $proxyNamespace;
    }

    public function getCache() {
        return $this->cache;
    }

    public function setCache($cache) {
        $this->cache = $cache;
    }

    public function getEntityLibrary() {
        return $this->entityLibrary;
    }

    public function setEntityLibrary($entityLibrary) {
        $this->entityLibrary = $entityLibrary;
    }

    public function getApplicationMode() {
        return $this->applicationMode;
    }

    public function setApplicationMode($applicationMode) {
        $this->applicationMode = $applicationMode;
    }

    public function getEntityManager() {
        return $this->entityManager;
    }

    public function setEntityManager($entityManager) {
        $this->entityManager = $entityManager;
    }

    /**
     * Bootstrap Doctrine, setting the libraries and namespaces and creating
     * the entitymanager
     */
    public function bootstrap() {
        $this->registerClassLoader();

        // Load cache
        if ($this->getApplicationMode() == self::APP_MODE_DEVELOPMENT) {
            $this->cache = new ArrayCache;
        } else {
            $this->cache = new ApcCache;
        }

        /** @var $config Doctrine\ORM\Configuration */
        $config = new Configuration;
        $config->setMetadataCacheImpl($this->cache);
        $driverImpl = $config->newDefaultAnnotationDriver($this->getEntityLibrary());

        $config->setMetadataDriverImpl($driverImpl);
        $config->setQueryCacheImpl($this->cache);
        $config->setProxyDir($this->getProxyLibrary());
        $config->setProxyNamespace($this->getProxyNamespace());

        if ($this->applicationMode == self::APP_MODE_DEVELOPMENT) {
            $config->setAutoGenerateProxyClasses(true);
        } else {
            $config->setAutoGenerateProxyClasses(false);
        }

        $this->entityManager = EntityManager::create($this->getConnectionOptions(), $config);
    }

    /**
     * Register the different classloaders for each type.
     */
    private function registerClassLoader() {
        // Autoloader for all the Doctrine library files
        $classLoader = new ClassLoader('Doctrine', dirname(__FILE__) . '/');
        $classLoader->register();

        // Autoloader for all Entities
        $modelLoader = new ClassLoader('Entities', $this->getEntityLibrary());
        $modelLoader->register();

        // Autoloader for all Proxies
        $proxiesClassLoader = new ClassLoader('Proxies', $this->getProxyLibrary());
        $proxiesClassLoader->register();
    }

}
?>

Creating the component

Now we can start with setting up our component. Create a com_bugs folder in components with a models folder in it. In the models folder you should create an Entities folder (mind the capital, it’s important!).

Create the ‘Bug’ entity next. Copy the text below and place it in Bug.php in the models/Entities folder. Do not forget to set the namespace it is essential. If you forget it the entity can’t be found by the classloader. This is also the reason why the capitalization is so important.

<?php

namespace Entities;

/**

* @Entity @Table(name="bugs")

*/

class Bug {

/** @Id @Column(type="integer") @GeneratedValue */

private $id;

/** @Column(type="string") */

private $title;

/** @Column(type="string") */

private $description;

/** @Column(type="datetime") */

private $notificationDate;

/** @Column(type="datetime") */

private $solvedDate;

public function getId() {

return $this->id;

}

public function setId($id) {

$this->id = $id;

}

public function getTitle() {

return $this->title;

}

public function setTitle($title) {

$this->title = $title;

}

public function getDescription() {

return $this->description;

}

public function setDescription($description) {

$this->description = $description;

}

public function getNotificationDate() {

return $this->notificationDate;

}

public function setNotificationDate($notificationDate) {

$this->notificationDate = $notificationDate;

}

public function getSolvedDate() {

return $this->solvedDate;

}

public function setSolvedDate($solvedDate) {

$this->solvedDate = $solvedDate;

}

}

?>

There is our entity! Now we need a way to get that entity definition in our database. Doctrine has command-line tools for us to do that, but they need the same configuration as we give to our controller in the front-end. So, lets set-up that configuration and use it on the command line.

The configuration

In order to use Doctrine within our controllers we have to create the configuration and use our created bootstrapper to get Doctrine going. At the moment I chose the component initialization file for our initialization work on Doctrine. I’m looking for a way to extract this initialization in to a nicer place, but the options I’ve tried didn’t made me happy at all.

What do we need to do? Well, we need to tell where our entities are stored on the file system and where we want to store our proxy files. also we need to pass our database parameters to Doctrine so it has authorization to the database. Here is my init file (bugs.php) of the component:

<?php
// no direct access
defined('_JEXEC') or die;

// Include dependancies
jimport('joomla.application.component.controller');

require_once(JPATH_LIBRARIES . '/doctrine/bootstrap.php');

$controller = JController::getInstance('Bugs');
// configure Doctrine thru the bootstrapper
$controller->setEntityManager(bootstrapDoctrine());
$controller->execute(JRequest::getCmd('task', 'index'));
$controller->redirect();

/**
 * Initialize doctrine by setting the entities and proxies locaties. Also define
 * a default namespace for the proxies.
 */
function bootstrapDoctrine() {
    $doctrineProxy = new JoomlaDoctrineBootstrapper( JoomlaDoctrineBootstrapper::APP_MODE_DEVELOPMENT );
    $doctrineProxy->setEntityLibrary(dirname(__FILE__) . '/models');
    $doctrineProxy->setProxyLibrary(dirname(__FILE__) . '/proxies');
    $doctrineProxy->setProxyNamespace('Joomla\Proxies');
    $doctrineProxy->setConnectionOptions(getConfigurationOptions());
    $doctrineProxy->bootstrap();

    return $doctrineProxy->getEntityManager();
}

function getConfigurationOptions() {
     // Define database configuration options
    $joomlaConfig = JFactory::getConfig();
    return array(
        'driver' => 'pdo_mysql',
        'path' => 'database.mysql',
        'dbname' => $joomlaConfig->get('db'),
        'user' =>  $joomlaConfig->get('user'),
        'password' =>  $joomlaConfig->get('password')
    );
}

What do we do here. We retrieve an instance of our controller and our going to inject an EntityManager to this controller. In order to this we are going to call the JoomlaDoctrineBootstrapper, set the configuration parameters and it will return us the EntityManager. To make the configuration and use a little easier we are using the database credentials from the Joomla configuration.

That’s nice for the front-end, but how about that command line tool? Well Doctrine will search for a file called ‘cli-config.php’ on the location you call the doctrine command line tool. The file ‘cli-config.php’ will return an EntityManager using the configuration we set from our bootstrap file.

Before we start sorting out this file, a little notice. This file is somewhat strange. We have to perform a number of tricks so we can make use of the Joomla framework on the command line. The way we do use led to the fact we need a separate configuration file containing the database credentials and other configuration options. I’m sure that a number of trick I use here aren’t necessary, but I just can’t find a better way to do this. If you know the trick, please let me know. I, for sure, don’t like the way this file has been built up and would love to improve it.

Now with that out, I’ll show you the file.

<?php
// We are a valid Joomla entry point.
define('_JEXEC', 1);

// Setup the path related constants.
define('DS', DIRECTORY_SEPARATOR);
define('JPATH_BASE', __DIR__ . '/../../');
define('JPATH_ROOT', JPATH_BASE);
define('JPATH_CONFIGURATION', JPATH_BASE);
define('JPATH_LIBRARIES', JPATH_BASE.DS.'libraries');
define('JPATH_METHODS', JPATH_ROOT.DS.'methods');

// Load the library importer.
require_once (JPATH_LIBRARIES.'/joomla/import.php');
require_once (JPATH_CONFIGURATION.'/configuration.php');

// Import library dependencies.
jimport('joomla.application.application');
jimport('joomla.utilities.utility');
jimport('joomla.language.language');
jimport('joomla.utilities.string');
jimport('joomla.factory');

require_once __DIR__ . '/../../libraries/doctrine/bootstrap.php';

/**
 * Initialize doctrine by setting the entities and proxies locaties. Also define
 * a default namespace for the proxies.
 */
function bootstrapDoctrine() {
    $doctrineProxy = new JoomlaDoctrineBootstrapper( JoomlaDoctrineBootstrapper::APP_MODE_DEVELOPMENT );
    $doctrineProxy->setEntityLibrary(dirname(__FILE__) . '/models');
    $doctrineProxy->setProxyLibrary(dirname(__FILE__) . '/proxies');
    $doctrineProxy->setProxyNamespace('Joomla\Proxies');
    $doctrineProxy->setConnectionOptions(getConfigurationOptions());
    $doctrineProxy->bootstrap();

    return $doctrineProxy->getEntityManager();
}

function getConfigurationOptions() {
     // Define database configuration options
    $joomlaConfig = JFactory::getConfig(JPATH_BASE . '/cli-configuration.php');
    return array(
        'driver' => 'pdo_mysql',
        'path' => 'database.mysql',
        'dbname' => $joomlaConfig->get('db'),
        'user' =>  $joomlaConfig->get('user'),
        'password' =>  $joomlaConfig->get('password')
    );
}

$helperSet = new \Symfony\Component\Console\Helper\HelperSet(array(
    'em' => new \Doctrine\ORM\Tools\Console\Helper\EntityManagerHelper(bootstrapDoctrine())
));

The first part of the file is just bootstrapping of the Joomla framework. We determine the location of some core folders, we import core classes and all that will bootstrap the Joomla Framework. Then two function follow that we have seen before. The only difference is that we can’t use the default configuration, which will give us an blank configuration class, but an alternative file. Why not the default file? Well the default file is of the type JConfig and the factory expects an JFrameworkConfig to import.

The bottom three lines are the default code of Doctrine to get the command line tools going. You see, the only thing we do here is setting the EntityManager. More information about this file can be found on the Doctrine website.

The last mile

It has been a long way already, but we are getting there.The last thing I’m going to show you is how to make use of the Doctrine. If you remember we have created an interface earlier in this blog. Just implement this on your controller and implement the setEntityManager() method as required by the interface.

If you look back in the init file of the component we are using this method to set the EntityManager on the controller. We use the interface to make sure we use an generic method on all the controllers. In the example below you see how I created a simple example which makes use of Doctrine and outputs some basic information.

<?php

// No direct access
defined('_JEXEC') or die;

jimport('joomla.application.component.controller');
require_once(JPATH_LIBRARIES . '/doctrine/JoomlaDoctrineController.php');

/**
 * Description of BugsController
 *
 * @author pderaaij
 */
class BugsController extends JController implements JoomlaDoctrineController {

    /**
     *
     * @var Doctrine\ORM\EntityManager
     */
    private $em;

    public function setEntityManager(Doctrine\ORM\EntityManager $entityManager) {
        $this->em = $entityManager;
    }

    public function index() {
        // add a default bug every refresh
        $newBug = new Entities\Bug();
        $newBug->setTitle('Doctrine Test');
        $newBug->setDescription('test');
        $newBug->setNotificationDate(new DateTime());
        $newBug->setSolvedDate(new DateTime());
        $this->em->persist($newBug);
        $this->em->flush();

        $dql = "SELECT b FROM Entities\Bug b";
        $query = $this->em->createQuery($dql);
        $query->setMaxResults(30);
        $bugs = $query->getResult();

        echo '<h1>Bug overview</h1>';
        echo '<table width="100%">';
        echo '<tr>';
            echo '<th>#</th>';
            echo '<th>Title</th>';
            echo '<th>Notification date</th>';
            echo '<th>Date solved</th>';
        echo '</tr>';

        foreach( $bugs as $bug ) {
            /* @var $bug Bug */
            echo '<tr>';
                echo '<td>' . $bug->getId() . '</td>';
                echo '<td>' . $bug->getTitle() . '</td>';
                echo '<td>' . $bug->getNotificationDate()->format("Y-m-d H:i:s") . '</td>';
                echo '<td>' . $bug->getSolvedDate()->format("Y-m-d H:i:s") . '</td>';
            echo '</tr>';
        }

        echo '</table>';

        echo '<h1>Bug #1</h1>';
        $bug = $this->em->find("Entities\Bug", 1);
        echo '<pre>';
            var_dump($bug);
        echo '</pre>';
    }

}
?>

It’s a wrap

That’s it, now you can make use of Doctrine within your component. It was a long blog post, but I hope I’ve shown you an easy way to get going with Doctrine within Joomla.

I hope you liked this article. You can leave your feedback behind on this blog, since I’m always interested in new insights which I can use to learn and grow as an developer.

Via forums een fix gevonden om toch rtl gemist afleveringen bekijken. What to do:

Download de User Agent Switcher add-on voor Firefox: http://chrispederick.com/work/user-agent-switcher/. Voeg via het menu de volgende user agent toe:

Mozilla/5.0(iPad; U; CPU iPhone OS 3_2 like Mac OS X; en-us) AppleWebKit/531.21.10 (KHTML, like Gecko) Version/4.0.4 Mobile/7B314 Safari/531.21.10

Switch naar die user agent. Voor websites toe ben je nu een iPad waardoor je naar deze pagina kan surfen: http://www.rtl.nl/service/gemist/device/ipad/feed/index.xml

Hier kun je alle afleveringen terugkijken aangezien je nu direct toegang tot de mp4′s krijgt. De snelheid is hier wel beduidend lager, de laatste paar weken had ik met de iPad ook al veel buffer problemen en keek alleen maar naar haperende afleveringen. Hopelijk word dat nog gefixed.

While getting my way around the Joomla! framework I have a big problem getting the checked in unit tests to run. If you do a checkout of the unit tests from the svn you’ll see there are about 960 tests and about 600 fails straight out of the box. Pretty annoying and unusable to write your own tests against.

So I’ve been working on a test runner of my own. The test runner tries to use the most of the Joomla! framework, but some things it just have to do itself. It consists of 2 files. One file is the testloader which is setup as an autoloader using the JLoad class. The second class sets some configuration files and kickstarts the Joomla! framework.

Here’s the code for the testloader

<?php

/**

* Testloader class

*

* This class strips the requested class and passes it thru

* to the Joomla autoload function

*

* @author Paul de Raaij <paul@paulderaaij.nl>

*/

// Preload the model so we can add paths to the inlude path of JLoader

jimport( 'joomla.application.component.model' );

class TestLoader {

/**

* Strip the given class and pass it to the

* Joomla autoloader.

*

* If it's a component add the path to the

* include path of the loader

*

* @param String $classname

* @return bool Has the inclusion succeeded

*/

static public function load( $classname ) {

$explodedPath = self::explodeClassname( $classname );

if( $explodedPath == null ) {

return self::loadJoomlaClass( $classname );

}

// Add the folder to the loader include path

JModel::addIncludePath('../components/com_' . $explodedPath['component'] . '/' . $explodedPath['type'] . 's');

return self::loadJoomlaClass( $classname );

}

/**

* Explode the classname and strip component name,

* type and type name

*

* @param string $classname

* @return mixed Returns null when it's a core file. Returns an array with data if it's a component data

*/

static protected function explodeClassname( $classname ) {

$types = array('model', 'controller', 'helper', 'view');

$classname = strtolower($classname);

if( $classname == 'jmodel' ) {

return null;

}

$fileInfo = array();

foreach( $types as $type ) {

if( false !== strpos($classname, $type) ) {

$fileInfo['type']       = $type;

}

}

if( isset( $fileInfo['type'] ) ) {

$fileInfo['component']  = substr($classname, 0, strpos($classname, $fileInfo['type'] ) );

$fileInfo['name']       = substr($classname, ( strpos($classname, $fileInfo['type'] ) + strlen($fileInfo['type']) ) );

return $fileInfo;

}

return null;

}

/**

* Simple pass thru function to the Joomla autoloader

*

* @param string $class

* @return bool Has inclusion succeeded?

*/

static public function loadJoomlaClass( $class ) {

return JLoader::load( $class );

}

}

?>

And this is the TestCase class which is required by each unit test file:

<?php

require_once 'PHPUnit/Framework.php';

// We are a valid Joomla entry point.

define('_JEXEC', 1);

// Setup the path related constants.

define('DS', DIRECTORY_SEPARATOR);

define('JPATH_BASE', dirname( __FILE__ ) . '\..');

define('JPATH_ROOT', JPATH_BASE);

define('JPATH_CONFIGURATION', JPATH_BASE);

define('JPATH_LIBRARIES', JPATH_BASE.DS.'libraries');

define('JPATH_METHODS', JPATH_ROOT.DS.'methods');

// Load the library importer, datbase class and configuration

require_once (JPATH_LIBRARIES.'/joomla/import.php');

require_once (JPATH_LIBRARIES.'/joomla/database/database.php');

// Load the TestLoader

require_once dirname(__FILE__) . '\lib\TestLoader.php';

// register specific test autloader

if( !defined('LOADED_AUTOLOADER') ) {

spl_autoload_register( array('TestLoader', 'load') );

define('LOADED_AUTOLOADER', true);

}

// Define configuration

jimport( 'joomla.registry.registry' );

require_once( JPATH_CONFIGURATION.'/configuration.php' );

// Create the JConfig object

$config = new JConfig();

// Get the global configuration object

$registry =& JFactory::getConfig();

// Load the configuration values into the registry

$registry->loadObject($config);

$options = array ('driver' => $config->driver,

'host' => $config->host,

'user' => $config->user,

'password' => $config->password,

'database' => $config->database,

'prefix' => $config->prefix );

// Preload database with configuration

$db = JDatabase::getInstance( $options );

?>

An example unit test looks like this:

<?php

require_once dirname(__FILE__) . '\..\..\..\TestCase.php';

class Model_Test_Base extends PHPUnit_Framework_TestCase {

protected $model = null;

public function setUp() {

$this->model = JModel::getInstance('<modelname>', '<componentname>Model');

}

public function testSimpleAssertion() {

$this->assertTrue( $this->model->test() );

}

}

?>

Perhaps this isn’t the best way to use unit testing in Joomla! But at the moment this is the only thing I got working. If you’ve got some suggestions your glad to leave it behind as a reaction!

Het afgelopen jaar heb ik op dit blog al geregeld gepost hoe de opleiding mij verging. Over het algemeen ben ik best tevreden met de HHS, natuurlijk zijn er behoorlijk wat rare situaties, maar inmiddels begrijp ik ook wel dat je die overal wel tegenkomt.

Het laatste blok moesten we van een zeer oud en slecht geschreven programma het beheer op ons nemen en daar nieuwe functionaliteiten inbakken en dat volgens nette beheer methodes. Met weer een deels nieuw project groepje ging het ons aardig af. Voor de praktijk opdracht kregen we een 7 en voor de theoretische toets had ik een 7,3. Prima voor elkaar dus!

Eindresultaat van het eerste jaar is dan ook dat ik met de diverse vrijstellingen in het eerste jaar al 105 studiepunten heb gehaald, de propedeuse binnen is en dat ik lekker op schema lig om over 1,5 jaar het diploma op te halen.

Kortom… doe mij nog maar zo’n schooljaar!

Zes jaar lang ben ik aan de gang gegaan met Mediactief en heb ik geprobeerd mijn droom te realiseren. De laatste maanden kwam ik er echter steeds meer achter dat ik het niet zo gevormd kreeg zoals ik het graag zou willen hebben. Helaas, had ik ook niet het vertrouwen dat ik dit wel voor elkaar kreeg zoals ik zou willen. Als je daarbij optelt dat ik daardoor ook steeds meer het plezier kwijtraakte, dan is er maar een juiste beslissing.

En om eerlijk te zijn voel ik me er heel goed bij. Het is de juiste beslissing geweest en zeker ook geen schande. Ik voel dan ook geen schaamte en zie het ook niet als falen. Ik heb het geprobeerd en op tijd ingezien dat het mooi is geweest.

Het bedrijf is verkocht aan Eleven in Maasdijk. Zij nemen mijn klanten over en ook ik zal mij bij hun team voegen als webdeveloper. Daar kan ik gaan doen wat ik echt wil doen en dat is het ontwikkelen van (web)applicaties. Lekker in de code duiken zonder te denken aan de BTW aanslag die nog moet gebeuren en dat soort zaken.

Zes jaar lang heb ik me vol overgave gegeven voor mijn bedrijf en mijn klanten. Ik wil hun dan nogmaals ontzettend bedanken voor hun vertrouwen in mij en mijn team. Ik waardeer het zeer en weet zeker dat we samen met Eleven nog betere service en kwaliteit kunnen verlenen.

Ik heb er de volste vertrouwen in!

Account:
columns:
id:             { type: integer, primary: true, autoincrement: true, notnull: true }
accountNumber:  { type: integer, notnull: true }
accountName:    { type: string(255), notnull: true }

Order:
columns:
id:             { type: integer, primary: true, autoincrement: true, notnull: true }
internID:       { type: string(20) }
accountID:      { type: integer, notnull: true }
locationID:    { type: integer }
orderDate:      { type: timestamp }
orderedBy:      { type: integer, notnull: true }
remarks:        { type: string(3000) }
orderDelivered: { type: boolean }
placedOrder:    { type: boolean }
relations:
Account:        { onDelete: CASCADE, local: accountID, foreign: id, foreignAlias: accountOrders }

Article:

columns:

id:            { type: integer, primary: true, autoincrement: true, notnull: true }
accountID:     { type: integer, notnull: true }

articleNumber: { type: string(15) }

description:   { type: string(255) }

currentStock:  { type: integer }

minimumStock:  { type: integer }

packageAmount: { type: integer }

previewFile:   { type: string( 255 ) }

remarks:       { type: string( 3000 ) }

internRemarks: { type: string( 5000 ) }

image:         { type: string( 255 ) }

relations:

Account:       { onDelete: CASCADE, local: accountID, foreign: id, foreignAlias: articleAccount }

In short. We have an account and each account has it own articles. The can order these articles and this is stored in the Order model ( and a bunch of others, which aren’t relevant for this post).

What we want to achieve is that we can filter the client list based on a article number or order id.

To do this I extended the generator.yml to add the two new fields.

config:

fields:
articleNumber:     {label: Artikel nummer, type: string }
orderNumber:     {label: Order nummer, type: string }

Next thing to do is to modify the filter form of the account model. Here we’re going to add the two new fields to the filter form and give them a simple validator.

public function configure()

{

parent::configure();

$this->widgetSchema['articleNumber'] = new sfWidgetFormInputText();

$this->validatorSchema['articleNumber'] = new sfValidatorPass(array('required'=>'false'));

$this->widgetSchema['orderNumber'] = new sfWidgetFormInputText();

$this->validatorSchema['orderNumber'] = new sfValidatorPass(array('required'=>'false'));

}

Now we want to add the filter values to the query so that the list actually gets filtered by the given values. Therefore were going to add a function for each of the filter fields. The function has one purpose and that is to add a where to the doctrine query.

protected function addArticleNumberColumnQuery( Doctrine_Query $query, $field, $values) {

$rootAlias = $query->getRootAlias();

$fieldName = 'articleNumber';

$query->addWhere( sprintf('%s.articleAccount.%s = ?', $rootAlias, $fieldName), $values );

}

protected function addOrderNumberColumnQuery( Doctrine_Query $query, $field, $values) {

$rootAlias = $query->getRootAlias();

$fieldName = 'id';

$query->addWhere( sprintf('%s.accountOrders.%s = ?', $rootAlias, $fieldName), $values );

}

The name of the function is specific and has to match the format add%fieldname%ColumnQuery. The code in the functions are pretty self-explanatory. Somethings are hard coded and could be a  nicer. For example you could name the field accountOrders instead of orderNumber so that you can use the value of $field.

This is the simplest solution I could find for filtering a model based on its relations. If someone knows a better way I’d love to hear about it.