Maybe would be intresting to add a register module (with register / confirmation ) and stuff, and also to implement the forgot password functionality.
Alecs 2010/4/28 Michał Piotrowski <[email protected]>: > Hi, > > I asked a similar question a while ago in a comment to blog post on > symfony-project and no one answered. > > I also created a ticket for a bug in sfDoctrineGuard, posted an email > to Jonathan and no one answered. > > I guess that Jonathan is buried alive in his work. Maybe > sfDoctrineguard needs a co-developer? sfDoctrineGuard is really > important plugin and needs a bit more attention IMHO. > > Regards, > Michal > > 2010/4/28 Tom Boutell <[email protected]>: >> I hear crickets chirping... a roadmap for this would be great if possible >> >> On Thu, Apr 8, 2010 at 2:47 PM, Tom Boutell <[email protected]> wrote: >>> Question mostly for Jon Wage: >>> >>> Is there a rough timetable for a stable release of the new >>> sfDoctrineGuardPlugin? >>> >>> The new version has BIGINTs for IDs and incorporates email address and >>> full name fields in the sf_guard_user schema. We are on board with >>> that, but it's difficult to plan for the short and medium-term future >>> without a rough idea of when that might be the commonly installed >>> version. Right now our apps tend to have fullname and email address >>> fields in an sfGuardUserProfile table. And our plugins (including >>> apostrophePlugin), which need to be able to refer to sfGuardUser >>> objects via foreign keys, have 4-byte integers for user ID fields. >>> >>> MySQL generates an error if you try to add a foreign key relationship >>> with a different integer type so there's a compatibility issue here. >>> >>> At the same time I see that the core Symfony and Doctrine teams are >>> working hard on Symfony 2.0 and Doctrine 2.0. So I wonder if the new >>> sfDoctrineGuardPlugin is to be expected any time soon, or if it might >>> make better sense to just skip it and require the use of the currently >>> stable release of sfDoctrineGuardPlugin unless and until we redo our >>> stuff anyway for Symfony 2.0. >>> >>> Any insight welcome. Thanks! >>> >>> -- >>> Tom Boutell >>> P'unk Avenue >>> 215 755 1330 >>> punkave.com >>> window.punkave.com >>> >> >> >> >> -- >> Tom Boutell >> P'unk Avenue >> 215 755 1330 >> punkave.com >> window.punkave.com >> >> -- >> 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 developers" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/symfony-devs?hl=en >> > > -- > 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 developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- Have a nice day! Alecs Certified ScrumMaster There are no cannibals alive! I have ate the last one yesterday ... I am on web: http://www.alecslupu.ro/ I am on twitter: http://twitter.com/alecslupu I am on linkedIn: http://www.linkedin.com/in/alecslupu Tel: (+4)0722 621 280 -- 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 developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
