RSSAll Entries Tagged With: "symfony"

Set Credentials using security.yml in Symfony 1.4

Symfony provides some cool configuration features that would allow you to minimize your coding part .  In this tutorial i would explain how to configure security.yml to set credentials for a different users.

Create a class file named account.class.php under apps/frontend/lib folder with content .The class below checks weather the user is admin and sets his credential as ‘admin’ . Update the class file as your requirement .


class account
public static function getLoginAdmin($username, $password)
// code to check for username and password in a particular table : ORM is doctrine
$usr = Doctrine::getTable(‘TableName’)
->where(‘a.adminuser = ?’,$username)
->andWhere(‘a.password = ?’,$password)

$login_user = count($usr);

if($login_user > 0)

return true;
return false;
public static function LogoutSession()


return true;


And in login action file after receiving username and password call the library function as shown below


$login_flag = account::getLoginAdmin($this->username,$this->password);


and if $login_flag returns true you have successfully logged in else enter username or password is invalid .

You have done with the class file and action page . Now you need to configure security.yml .

Create a folder named config inside a module ( say for eg : under admin module ) with security.yml in it and paste the following code .


is_secure: true
credentials: admin


Now admin module can be accessed only by one with ‘admin’ credential .

You can flush the credential as


$logout = account::LogoutSession();


You are done !

Symfony | Doctrine | Error | SQLSTATE[HY000]: General error: 1005 Can’t create table XXX.#sql-818 _1′ (errno: 121). Failing Query:” ALTER TABLE xxx ADD CONSTRAINT …. FOREIGN KEY (xyz) REFERENCES XXX(id) ON DELETE CASCADE”

Symfony is a web application framework written in PHP which follows the model-view-controller (MVC) paradigm . A symfony developer may use Object-Relational Mapping (ORM) – Propel or Doctrine . The earlier version of symfony supported propel and i was using it . But in updated versions symfony supported Doctrine and was forced to update my skills in ORM .

Configuring symfony is pretty simple and model and sql was generated successfully . But on executing the command line argument to insert sql .


symfony doctrine:insert-sql


i got an error :

SQLSTATE[HY000]: General error: 1005 Can’t create table XXX.#sql-818_1′ (errno: 121). Failing Query:” ALTER TABLE xxx ADD CONSTRAINT …. FOREIGN KEY (XYZ) REFERENCES XXX(id) ON DELETE CASCADE”

The error got on my nerves and couldn’t figure out what was it all about . But i was sure its something related to foreign key and after some research i got a fix for it and i am sharing it with you .

There is an issue with your ID columns. Normally this has to do with the foreign key and primary keys having different length constraints. Your fix:

Make sure that the length constraints match. If you aren’t specifying a length, you can simply remove the ID field from your schema.yml, and let Doctrine create it for you, or if you want to be explicit, you can set a length and make sure it is matched in the related foreign key field.

actAs: { Timestampable: ~ }
username: { type: string(255), notnull: true, unique: true }
password: { type: string(255), notnull: true }
hash: { type: string(255), notnull: true }

actAs: { Timestampable: ~ }
metro_user_id: { type: integer, notnull: true }
ref_from: { type: string(255), notnull: true, unique: true }
mobilenumber: { type: string(255), notnull: true }
is_mobile_valid: { type: boolean, notnull: true, default: 0 }
email_id: { type: string(255), notnull: true }
MetroUsers: { onDelete: CASCADE, local: metro_user_id, foreign: id, foreignAlias: MetroUserDetail }

Here id is generated automatically for MetroUsers and make sure that metro_user_id is of type integer .