sfGuard and usage of sfGuardUserProfile

Prev		Next

http://www.symfony-project.org/forum/index.php?t=msg&goto=20465&&srch=sfGuard#msg_20465

> I don't get how is sfGuardUserProfile intended to be used (in backend).
> How should i connect sfGuardUserProfile and sfGuardUser?

Profile feature of sfGuardPlugin is intended to enable adding more information to user above standard username and password (etc) available in sfGuardUser.

You can create for example user table, where you want store first name, surname, email, address etc.

To connect 'user' and 'sf_guard_user' tables together, you must add new column (let's say sf_guard_user_id) with "foreign key to sf_guard_user" to your user table.

And then edit app.yml and add following.

all:
  sf_guard_plugin:
    profile_class:      User
    profile_field_name: sf_guard_user_id

(The reason why it cannot be done with real foreign keys is the limitation of Propel.)

Then you can access data from your user table by doing

$this->getUser()->getProfile()->getEmail();

for example.

documented on: 11 February 2007, qube

sfGuard and usage of sfGuardUserProfile

I think the point that the first two posts are making is that the fields of the 'user' table are not automatically available in the generated sfGuardUser admin module.

If you want to add these fields, you would need to add partials to the sfGuardUser admin generator.yml. One for each field you want to have access to. You would then need to extend the actions and add validation. I'm not sure, but I guess that you can create a module called sfGuardUser and put your actions, partials, generator.yml and validation.yml in there, to override the built in settings.

It would be nice if this could be taken care of automatically by the admin generator, but unfortunately the generated admin modules can only handle a single table.

documented on: 11 February 2007, flat stanley

usage of sfGuardUserProfile

http://www.symfony-project.org/forum/index.php?t=msg&th=4782#msg_21884

COil wrote on Sat, 17 February 2007 07:42

Well in fact it's easy [to automate setting profile], just make a setProfile() in your myUser.class.php, in this one you will put the profile object in the session, call this function in sfGuardAuth sigin function… and also re-implement getProfile() in myUser to take profile from session and not from database

where is the best place to put the profile object in the session?

I hacked the following, but I get this error:

Fatal error: Call to a member function getProfile() on a non-object in /var/www/my_proj/plugins/sfGuardPlugin/lib/user/sfGuardSecur ityUser.class.php on line 193

$ symfony init-module reqs sfGuardAuth

Define getProfileId in myUser:

$ cat apps/reqs/lib/myUser.class.php
<?php

class myUser extends sfGuardSecurityUser
{
    public function getProfileId()
    {
        return $this->getAttribute('sfGuardProfileId');
    }
}

Save profile ID in the session:

$ cat apps/reqs/modules/sfGuardAuth/actions/actions.class.php
<?php

require_once(sfConfig::get('sf_plugins_dir').'/sfGuardPlugin/modules/sfGuardAuth/lib/BasesfGuardAuthActions.class.php');

/**
 * sfGuardAuth actions.
 *
 * @package    cm
 * @subpackage sfGuardAuth
 * @author     Your name here
 * @version    SVN: $Id: actions.class.php 2692 2006-11-15 21:03:55Z fabien $
 */
class sfGuardAuthActions extends BasesfGuardAuthActions
{
  /**
   * Executes Signin action
   *
   */
    public function executeSignin()
    {
        // pre hook
        // Store data in the user session
        $this->getUser()->
            setAttribute('sfGuardProfileId',
                         $this->getUser()->getProfile()->getId());

        // call the parent method
        parent::executeSignin();

        // post hook
    }
}

How to use it:

$ tail -13 apps/reqs/modules/req/actions/actions.class.php
    protected function saveReq($req)
    {
        // pre save hook
        //$req->setStaffId($this->getUser()->getProfile()->getId());
        //$req->setStaffId($this->getUser()->getAttribute('sfGuardProfileId'));
        $req->setStaffId($this->getUser()->getProfileId());

        // call the parent save() method
        parent::saveReq($req);

        // post save hook
    }
}

Help

If you want to customize or add methods to the sfGuardAuth:

Create a sfGuardAuth module in your application

Create an actions.class.php file in your actions directory that inherit from BasesfGuardAuthActions

<?php

class sfGuardAuthActions extends BasesfGuardAuthActions
{
  public function executeNewAction()
  {
    return $this->renderText('This is a new sfGuardAuth action.');
  }
}

documented on: 2007.02.27