Symfony: error when creating models

Question

I'm new to Symfony, and I don't even succeed in creating valid models.

I created my project - which use propel - and wrote the following schema.yml:

propel:
  poc:
    id:           ~
    message:      { type: varchar(140), required: true}
    author:       { type: varchar(255), required: true}
    plus:         { type: integer, default: 0}
    minus:        { type: integer, default: 0}
    created_at:   ~

Then I executed the following commands without errors:

$ php symfony propel:build --sql
$ php symfony propel:insert-sql
$ php symfony propel:build --model

But when I try to load fixtures or generate a module, I obtain this error:

$ php symfony propel:data-load             
>> propel    load data from "/home/me/www/poc/data/fixtures"
PHP Fatal error:  Cannot redefine class constant BasePoc::PEER in /home/me/www/poc/lib/model/om/BasePoc.php on line 85

Fatal error: Cannot redefine class constant BasePoc::PEER in /home/me/www/poc/lib/model/om/BasePoc.php on line 85

The class constant PEER is defined twice in the BasePoc.php, but why ?

I googled and recreated the project several times, but I couldn't see my mistake.

Sometimes symfony can get a little bit confused with the base classes. Try deleting the whole directory that all of the Base model files live in (be careful not to delete any files that you have edited). These base files get generated any time that you build the model. If that doesn't work, I'd try tracking down where the class constant PEER is defined and check that you haven't accidentally added it to a class. — Blair McMillan
– Blair McMillan, Commented Mar 16, 2011 at 22:32

mppfiles · Accepted Answer · 2011-10-27 17:27:09Z

3

If you are using the new sfPropelORMPlugin instead of the sfPropelPlugin bundled with symfony, just read the README file on the plugin, you are missing the last step:

Change the path of the symfony behaviors in the config/propel.ini file of your project:

[ini]
propel.behavior.symfony.class                  = plugins.sfPropelORMPlugin.lib.behavior.SfPropelBehaviorSymfony
propel.behavior.symfony_i18n.class             = plugins.sfPropelORMPlugin.lib.behavior.SfPropelBehaviorI18n
propel.behavior.symfony_i18n_translation.class = plugins.sfPropelORMPlugin.lib.behavior.SfPropelBehaviorI18nTranslation
propel.behavior.symfony_behaviors.class        = plugins.sfPropelORMPlugin.lib.behavior.SfPropelBehaviorSymfonyBehaviors
propel.behavior.symfony_timestampable.class    = plugins.sfPropelORMPlugin.lib.behavior.SfPropelBehaviorTimestampable

Note: a quick "bulk replace" on the file is enough. Note 2: if you are using sfPropel15Plugin, please upgrade to sfPropelORMPlugin.

hope it helps!

edited Oct 27, 2011 at 17:27

answered Apr 5, 2011 at 13:09

mppfiles

2,4171 gold badge22 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Burgi Over a year ago

thanks for that, been updating a lot of old propel projects lately and must've missed that!

mppfiles Over a year ago

For those interested in starting new projects with symfony 1.4 + sfPropelORMPlugin, there's a little bash script that aims to automate such process. Check it out here.

Firemonkey · Accepted Answer · 2011-03-16 21:39:04Z

-1

It seems propel can not render the entire file. (propel has very bas error reporting, yaml) Make sure to check that there are no tabs in your file and that everything is idented with 2 spaces.

The rest of the seems fine to me. i personally prefer using doctrine, (You would just have to put the created_at parameter in a ActAs behavior)

proc:
  actAs: Timestampable: ~
  columns:
    id:           ~
    message:      { type: varchar(140), required: true}
    author:       { type: varchar(255), required: true}
    plus:         { type: integer, default: 0}
    minus:        { type: integer, default: 0}

answered Mar 16, 2011 at 21:39

Firemonkey

613 silver badges7 bronze badges

2 Comments

Maerlyn Over a year ago

He's using propel, you gave a doctrine schema.

K-Phoen Over a year ago

I had the error with Propel 1.5.6, using Propel 1.4.x solved the problem (without changing anything in the schema.yml).

Collectives™ on Stack Overflow

Symfony: error when creating models

2 Answers 2

2 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related