Hello Tristan,
Which version were you upgrading from? Was it 1.2.x? If so, there's a
change in model definition (covered in Upgrade section of README).
Basis models are no longer used, and since plugin:upgrade seems to
only write new files, leaving old in place, you might have to remove
all Basis either from plugin's lib folder, and from your own as well.
Ideally would be to generate diff, before running doctrine:build --all-
classes, however there could be still some problems with it.

Where this error originated in? Was just after running? if so, there's
probably autoload's cache trying to access, if you've got info, it's
probably one of the old sfGuardUserProfileBasis model.

On 26 Lip, 14:56, Tristan <tristan.bessou...@gmail.com> wrote:
> Hello,
>
> after upgrading to the 1.3.2 version of the
> sfForkedDoctrineApplyPlugin, here what i've got right after
> plugin:upgrade
> :
> [CODE]
> Warning: require(/Users/Tristan/Sites/plugins/
> sfForkedDoctrineApplyPlugin/lib/model/doctrine/
> PluginsfGuardUserProfileBasis.class.php) [function.require]: failed to
> open stream: No such file or directory in /Users/Tristan/Sites/lib/
> vendor/symfony/lib/autoload/sfAutoload.class.php  on line 188
>
> Fatal error: require() [function.require]: Failed opening required '/
> Users/Tristan/Sites/plugins/sfForkedDoctrineApplyPlugin/lib/model/
> doctrine/PluginsfGuardUserProfileBasis.class.php' (include_path='.:/
> usr/lib/php') in /Users/Tristan/Sites/lib/vendor/symfony/lib/autoload/
> sfAutoload.class.php on line 188[/CODE]

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to