sfForkedDoctrineApplyPlugin - 1.1.1

Add's register and profile functionality to websites protected with sfDoctrineGuardPlugin.

You are currently browsing
the website for symfony 1

Visit the Symfony2 website

« Back to the Plugins Home


Forgot your password?
Create an account



advanced search
Information Readme Dependencies Releases Changelog Contribute
Show source

sfForkedDoctrineApply plugin

Forked from sfDoctrineApply plugin (version 1.1.1).

It's stripped of Zend Mail dependencies as proposed by stephenrs on symfony forums, here

Thanks to punkave guys for the original plugin, and Big thanks to stephen for the modifications.


  • symfony 1.4
  • sfDoctrineGuardPlugin - installed and configured

Requirements should be similar as the original plugin, although I can only be sure of symfony 1.4. When sfDoctrineGuardPlugin will introduce email in official package, our current plugin should be modified to use sfGuardUser's email field, not it's own.

Changes to sfDoctrineApplyPlugin

  • removed all Zend Mail dependency
  • created a general library with all sfApplyActions functions
  • introduced inheritance to Profile model.


Installation should be simple as:

symfony plugin:install sfForkedDoctrineApplyPlugin

However it is also possible to install it through archive:

symfony plugin:install sfForkedDoctrineApplyPlugin-1.1.1.tgz

just place downloaded package in your project's root first.

You can also install it manually, unpacking archive, placing it's content in your project's plugin/ directory, and enabling it in your ProjectConfiguration.class.php file:


class ProjectConfiguration extends sfProjectConfiguration
    public function setup()

After installing this plugin, add this declaration into your schema.yml file: config/doctrine/schema.yml

    type: simple
    extends: sfGuardUserProfileBasis
  # Don't forget this!
      class: sfGuardUser
      foreign: id
      local: user_id
      type: one
      onDelete: cascade
      foreignType: one
      foreignAlias: Profile

You can add your own columns, if needed, it just won't be possible to set these as not null in database. Build your model after those steps.

All you need to do is to enable sfApply module in your settings.yml file:


    enabled_modules: [default, ... , sfGuardAuth, sfApply]

and set up routes for your app:


  url:  /user/new
  param: { module: sfApply, action: apply }

  url: /user/password-reset
  param: { module: sfApply, action: reset }

  url: /user/reset-request
  param: { module: sfApply, action: resetRequest }

  url: /user/reset-cancel
  param: { module: sfApply, action: resetCancel }

  url: /user/confirm/:validate
  param: { module: sfApply, action: confirm }

  url: /user/settings
  param: { module: sfApply, action: settings }

And you can enjoy user registration on your website.


To configure this plugin to actually send registration emails, You need to set up email settings according to day 16 of Jobeet tutorial.


In order to send emails with confirmation codes you've got to add these settings in your app.yml:


          email: "your@emailaddress.com"
          fullname: "the staff at yoursite.com"

You should also turn on i18n engine, as this plugin, like the project it rooted from is fully internationalised (You might have to prepare i18n files for your language though):


    i18n: on


Starting from 1.1.0 version, sfForkedDoctrineApplyPlugin integrates reCaptcha. To use it, you have to install sfFormExtraPlugin to get access to reCaptcha widget and validator. Second step is to be conducted in your app.yml file, and add these:


    enabled:        true
    public_key:     YOUR_PUBLIC_reCAPTCHA_KEY
    private_key:    YOUR_PRIVATE_reCAPTCHA_KEY

enabled property is for enabling and disabling captcha. After setting this, reCaptcha will appear on apply and reset request pages.

Custom forms

Since version 1.1.1, it is possible to define own, custom forms for apply action, however all custom forms must extend the Apply ones. To use custom forms, you need to define them in your app.yml file:


    applyForm: sfApplyApplyForm
    resetForm: sfApplyResetForm
    resetRequestForm: sfApplyResetRequestForm
    settingsForm: sfApplySettingsForm

The above example uses standard sfApplyForms.

Login redirect

There are two settings regarding directing user after actions he takes within sfApply module:

    afterLogin: after_login_route
    after: after_route

You can use these settings to direct user to your own pages after user loggs in, or in other cases with second setting.

Displaying Login and Logout Prompts

(fragment of sfDoctrineApplyPlugin's README)

You probably have pages on which logging in is optional. It's nice to display a login prompt directly on these pages. If you want to do that, try including my login/logout prompt component from your apps/frontend/templates/layout.php file:

<?php include_component('sfApply', 'login') ?>

Note that you can suppress the login prompt on pages that do include this partial by setting the sf_apply_login slot:

<?php slot('sf_apply_login') ?>
<?php end_slot() ?>


sfDoctrineApplyPlugin was written by Tom Boutell. He can be contacted at tom@punkave.com. See also www.punkave.com and www.boutell.com for further information about his work.

Changes resulting in forking the original plugin were written by stephenrs. sfForkedDoctrineApplyPlugin was created by Grzegorz Śliwiński as a result of those changes with some additions. You can contact him at fizyk@fizyk.net.pl or through jabber/xmpp at fizyk@jabbim.pl and follow his adventures on his homepage.


  • Italian - Alessandro Rossi
  • Polish - Grzegorz ÅšliwiÅ„ski