« Back to blog

Viewed
times
Favorited 0 times
Get Updates
 

sfPropel16Plugin Is Already There, Didn't You Know?

The question arose several times in the past weeks: When will sfPropel16Plugin be published? Well, it's been published for a long time already, it's just that it was called "sfPropel15Plugin/1.6 branch". You can find it on GitHub: 

This repository used to default to the 'master' branch, which is a clone of the current 1.5 branch of sfPropel15Plugin. Enhancements were added to the 1.6 branch, which recently became the default branch. 

The repository contains an 'INSTALL' file explaining the few steps to get the plugin running on a symfony 1.4 project. 

Compared to the 1.5 version, this plugin features new tasks to deal with migrations: `diff`, `migrate`, `up`, and `down`. Use the `symfony help` command to get usage information on these tasks, and refer to the Propel documentation for a complete explanation of Propel migrations. There is also support for master-slave configuration right in the `databases.yml`, the ability to filter embedded forms with a `Criteria`, and several bug fixes.

It's a drop-in replacement for the previous sfPropel15Plugin from the symfony plugins page.

Last question: Why is it called sfPropel15Plugin if it embeds Propel 1.6? Because we won't force you to use different class names for each minor release of Propel. Backwards compatibility has always been a central concern, and changing the plugin name (and the names of the classes it embeds) wouldn't allow that. That wouldn't be so surprising if Propel 1.5 was named Propel 2, except that wasn't the case ;)

Posted by Francois Zaninotto 

18 comments

Jan 27, 2011
xplo said...
any plan to use a simple svn repo with the final release ?
it s becoming a little hard/impossible to manage externals with github that itself need svn external :)
Jan 28, 2011
Frosty Z said...
About "Why is it called sfPropel15Plugin if it embeds Propel 1.6?"

In the future, could it be possible to name it, once for all, sfPropelPlugin ?

Jan 28, 2011
Francois Zaninotto said...
@FrostyZ: I'd love that, but I think it would conflict with the sfPropelPlugin embedded with symfony...
Jan 28, 2011
Frosty Z said...
Ok, thanks for your quick answer.
Jan 30, 2011
ZsoltK said...
+1 for svn (though I don't like svn, I must use it)

Please consider it, thanks.

Jan 30, 2011
garakkio said...
Maybe it's jut a little improvement, but it should be worth a note: now sfPropel15Plugin automagically generates an admin module for a Model with sortable behavior with moving links (you know, that little arrows to move up and/or down rows)
Jan 31, 2011
Arkadiusz Tułodziecki said...
Last published version of sfPropel15Plugin is 1.1.4 - 08/08/2010. Please create new stable package for SF1.4.

Me and probably many other users prefer to install and upgrade plugins using symfony peer channel.

Jan 31, 2011
rozwell said...
@Francois:

Why not use the newest Propel in symfony then?
Most users upgrade it anyway (it's not m$ - so it's becomes faster and better) by themselves to the newest version and as you just mentioned, Propel is backward compatible (IMHO to exaggeration - it may hold evolution) so there's no good reason for symfony to stick with old releases, right?

I have no idea what happened to my posts above - delete them, please?

Jan 31, 2011
Francois Zaninotto said...
@rozwell: Do you mean updating sfPropelPlugin in the symfony 1 codebase? As far as I know, there is no activity on the 1.x branch of the symfony project. All devs work on version 2.0. They don't want to invest time on the 1.x.
Feb 02, 2011
theluctus said...
Hi Francois,

Once again, thank you for all your hard work, we appreciate it so much.

I was trying to install the 1.6 branch and followed all the instructions from the INSTALL.md file (github site)

I did everything, but then I run a simple "symfony cc" and I got this message:

PHP Warning: require_once(propel/Propel.php): failed to open stream: No such file or directory in /myproject/plugins/sfPropel15Plugin/config/sfPropel15PluginConfiguration.class.php on line 29

By the way, why did I have to do "mkdir vendor"?

Thanks!

Feb 02, 2011
Francois Zaninotto said...
@theluctus: Please use the mailing-list for support, a blog engine is really not a good way to track requests.
Feb 03, 2011
theluctus said...
You are right Francois, I have just posted this issue in the mailing list: https://groups.google.com/forum/#!topic/propel-users/DxOSaktsSr0

Have a nice day

Feb 13, 2011
Adam Frame said...
Small problem using in symfony 1.4 project regarding sluggable behaviour.

When adding primaryString: true to the schema of an article_i18n table, it generates two __toString() methods in /om/BaseArticle.class.php when building forms, causing an error. Removing the primaryString option from the schema doesn't cause error.

Feb 13, 2011
Adam Frame said...
Ignore previous message. Have posted to mailing list instead.
Apr 14, 2011
rozwell said...
Sorry for my absence, but I have a lot of work lately...
In INSTALL.md file, there's: "git checkout -b 1.6 remotes/origin/1.6" but AFAIK "-b" is used for branch creation - shouldn't it be removed?
Apr 14, 2011
rozwell said...
And changed to: "git checkout remotes/origin/1.6"
Apr 18, 2011
Francois Zaninotto said...
@rozwell: Thanks, I modified the INSTALL.md to be more simple. Don't hesitate to open a pull request on GitHub for such issues.
Jul 21, 2011
Hendra Saputra said...
i still cant manage to use many-to-many relationship in propel. already use sfPropel15Plugin, but the *_list widget still never declared on BaseFormXxx object. any suggestions guys? thanks

Leave a comment...