So far, I have the login with FFC views working, and started fixing
the specs now. Currently, I am still having some issues around the
users_controller since devise has naturally some impact there
(password reset, rendering user data for other users).
It would be great to hear your feedback, or eventually interest in
collaboration on this. I guess, once devise is working, using openid
should be only a small step. What would be needed more eventually, is
a rake task to migrate authlog user based passwords into devise based
passwords (have not yet looked into it, maybe devise can 'read'
authlogic sha's too)
Good point about the password migration. I think devise would by
default need to use the same sha, otherwise current accounts would
have no way to authorize. Thanks for looking into this.
On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
> So far, I have the login with FFC views working, and started fixing
> the specs now. Currently, I am still having some issues around the
> users_controller since devise has naturally some impact there
> (password reset, rendering user data for other users).
> It would be great to hear your feedback, or eventually interest in
> collaboration on this. I guess, once devise is working, using openid
> should be only a small step. What would be needed more eventually, is
> a rake task to migrate authlog user based passwords into devise based
> passwords (have not yet looked into it, maybe devise can 'read'
> authlogic sha's too)
> Thanks for your interest.
> best,
> patrick
> --
> You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
On Mon, May 7, 2012 at 5:57 AM, ben tillman <ben.till...@gmail.com> wrote:
> Hi Patrick,
> Good point about the password migration. I think devise would by
> default need to use the same sha, otherwise current accounts would
> have no way to authorize. Thanks for looking into this.
> On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
> > Hello,
> > So far, I have the login with FFC views working, and started fixing
> > the specs now. Currently, I am still having some issues around the
> > users_controller since devise has naturally some impact there
> > (password reset, rendering user data for other users).
> > It would be great to hear your feedback, or eventually interest in
> > collaboration on this. I guess, once devise is working, using openid
> > should be only a small step. What would be needed more eventually, is
> > a rake task to migrate authlog user based passwords into devise based
> > passwords (have not yet looked into it, maybe devise can 'read'
> > authlogic sha's too)
> > Thanks for your interest.
> > best,
> > patrick
> > --
> > You received this message because you are subscribed to the Google
> Groups "Fat Free CRM Developers" group.
> > To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> > To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
Thanks for the pointer.
From quickly looking over the commits, I see no conflicting changes
with the devise branch.
The main difference I can see, is that Devise is more related to some
kind of refactoring (AuthenticationController --> SessionsController)
and (UsersController --> RegistrationsController)
The next step, using OpenId, would indeed be related to a new feature.
So far, I am still missing the password reset part in my feature, and
eventually, how to have the re-login after a session time-out. And, as
Devise uses different columns for storing password and salt, I would
need to look how to migrate old authlogic passwords to new ones too.
On Mon, May 7, 2012 at 11:12 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> Ben has also been working on a 'cancan' branch for ffcrm with a view to
> strengthen group permissions and flexibility.
> As these branches affect similar parts of the system, it would be good to
> make sure they work nicely together.
> FFCRM + devise + cancan would be a very appealing setup.
> Thanks to you both.
> Steve
> On Mon, May 7, 2012 at 5:57 AM, ben tillman <ben.till...@gmail.com> wrote:
>> Hi Patrick,
>> Good point about the password migration. I think devise would by
>> default need to use the same sha, otherwise current accounts would
>> have no way to authorize. Thanks for looking into this.
>> On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
>> > Hello,
>> > Since it's a good opportunity to get a better understanding of both
>> > devise and FFC, I started work to setup devise authentication for FFC
>> > https://github.com/mulderp/fat_free_crm/tree/devise
>> > So far, I have the login with FFC views working, and started fixing
>> > the specs now. Currently, I am still having some issues around the
>> > users_controller since devise has naturally some impact there
>> > (password reset, rendering user data for other users).
>> > It would be great to hear your feedback, or eventually interest in
>> > collaboration on this. I guess, once devise is working, using openid
>> > should be only a small step. What would be needed more eventually, is
>> > a rake task to migrate authlog user based passwords into devise based
>> > passwords (have not yet looked into it, maybe devise can 'read'
>> > authlogic sha's too)
>> > Thanks for your interest.
>> > best,
>> > patrick
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Fat Free CRM Developers" group.
>> > To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > fat-free-crm-dev+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
I had a talk this afternoon with a fellow Rails developer, and we
discussed the 'scoping' of resources in a REST style.
And I thought that there comes a nice supplement or add-on that comes
with devise, namely routes likes this:
As I am thinking to do some test with devise and the cancan branch,
what types of groups were you thinking of using? What groups would be
added in the demo data? Are the groups roles based, location based or
job based for example?
On Mon, May 7, 2012 at 11:12 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> Ben has also been working on a 'cancan' branch for ffcrm with a view to
> strengthen group permissions and flexibility.
> As these branches affect similar parts of the system, it would be good to
> make sure they work nicely together.
> FFCRM + devise + cancan would be a very appealing setup.
> Thanks to you both.
> Steve
> On Mon, May 7, 2012 at 5:57 AM, ben tillman <ben.till...@gmail.com> wrote:
>> Hi Patrick,
>> Good point about the password migration. I think devise would by
>> default need to use the same sha, otherwise current accounts would
>> have no way to authorize. Thanks for looking into this.
>> On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
>> > Hello,
>> > Since it's a good opportunity to get a better understanding of both
>> > devise and FFC, I started work to setup devise authentication for FFC
>> > https://github.com/mulderp/fat_free_crm/tree/devise
>> > So far, I have the login with FFC views working, and started fixing
>> > the specs now. Currently, I am still having some issues around the
>> > users_controller since devise has naturally some impact there
>> > (password reset, rendering user data for other users).
>> > It would be great to hear your feedback, or eventually interest in
>> > collaboration on this. I guess, once devise is working, using openid
>> > should be only a small step. What would be needed more eventually, is
>> > a rake task to migrate authlog user based passwords into devise based
>> > passwords (have not yet looked into it, maybe devise can 'read'
>> > authlogic sha's too)
>> > Thanks for your interest.
>> > best,
>> > patrick
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Fat Free CRM Developers" group.
>> > To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > fat-free-crm-dev+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
My suggestion would be that we make the groups as flexible as possible. The
plan of the cancan branch is to provide the ability to FFCRM to know about
groups but for the actual implementation of groups (whether they are
location based or job based) to be left to the person who is customising
ffcrm for their own usage.
Perhaps, you could make devise do a similar thing... provide the framework
but leave the details to the user. And then perhaps provide a plugin that
shows how one might leverage the framework to turn the features into a
'jobs' based setup or a 'location' based one (hopefully with just a few
lines of code).
How does that sound?
Ben would have more understanding of this topic, so I'll defer to him as he
has been doing the actual work.
Regards,
Steve
On Thu, May 10, 2012 at 4:12 AM, Patrick Mulder <mulder.patr...@gmail.com>wrote:
> I had a talk this afternoon with a fellow Rails developer, and we
> discussed the 'scoping' of resources in a REST style.
> And I thought that there comes a nice supplement or add-on that comes
> with devise, namely routes likes this:
> As I am thinking to do some test with devise and the cancan branch,
> what types of groups were you thinking of using? What groups would be
> added in the demo data? Are the groups roles based, location based or
> job based for example?
> thanks and best regards,
> patrick
> On Mon, May 7, 2012 at 11:12 AM, Steve Kenworthy <stevey...@gmail.com>
> wrote:
> > Ben has also been working on a 'cancan' branch for ffcrm with a view to
> > strengthen group permissions and flexibility.
> > As these branches affect similar parts of the system, it would be good to
> > make sure they work nicely together.
> > FFCRM + devise + cancan would be a very appealing setup.
> > Thanks to you both.
> > Steve
> > On Mon, May 7, 2012 at 5:57 AM, ben tillman <ben.till...@gmail.com>
> wrote:
> >> Hi Patrick,
> >> Good point about the password migration. I think devise would by
> >> default need to use the same sha, otherwise current accounts would
> >> have no way to authorize. Thanks for looking into this.
> >> On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
> >> > Hello,
> >> > Since it's a good opportunity to get a better understanding of both
> >> > devise and FFC, I started work to setup devise authentication for FFC
> >> > https://github.com/mulderp/fat_free_crm/tree/devise
> >> > So far, I have the login with FFC views working, and started fixing
> >> > the specs now. Currently, I am still having some issues around the
> >> > users_controller since devise has naturally some impact there
> >> > (password reset, rendering user data for other users).
> >> > It would be great to hear your feedback, or eventually interest in
> >> > collaboration on this. I guess, once devise is working, using openid
> >> > should be only a small step. What would be needed more eventually, is
> >> > a rake task to migrate authlog user based passwords into devise based
> >> > passwords (have not yet looked into it, maybe devise can 'read'
> >> > authlogic sha's too)
> >> > Thanks for your interest.
> >> > best,
> >> > patrick
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups "Fat Free CRM Developers" group.
> >> > To post to this group, send email to
> fat-free-crm-dev@googlegroups.com.
> >> > To unsubscribe from this group, send email to
> >> > fat-free-crm-dev+unsubscribe@googlegroups.com.
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Fat Free CRM Developers" group.
> >> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> fat-free-crm-dev+unsubscribe@googlegroups.com.
> >> For more options, visit this group at
> >> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Fat Free CRM Developers" group.
> > To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> > To unsubscribe from this group, send email to
> > fat-free-crm-dev+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
Yes the cancan branch implements group permissions, but is still
failing specs I really need to go in and fix them but have been busy
on another project. If someone would like to volunteer for a spec
fixing session feel free :)
On 10 May 2012 14:23, Steve Kenworthy <stevey...@gmail.com> wrote:
> My suggestion would be that we make the groups as flexible as possible. The
> plan of the cancan branch is to provide the ability to FFCRM to know about
> groups but for the actual implementation of groups (whether they are
> location based or job based) to be left to the person who is customising
> ffcrm for their own usage.
> Perhaps, you could make devise do a similar thing... provide the framework
> but leave the details to the user. And then perhaps provide a plugin that
> shows how one might leverage the framework to turn the features into a
> 'jobs' based setup or a 'location' based one (hopefully with just a few
> lines of code).
> How does that sound?
> Ben would have more understanding of this topic, so I'll defer to him as he
> has been doing the actual work.
> Regards,
> Steve
> On Thu, May 10, 2012 at 4:12 AM, Patrick Mulder <mulder.patr...@gmail.com>
> wrote:
>> Hi Steve, Ben,
>> I had a talk this afternoon with a fellow Rails developer, and we
>> discussed the 'scoping' of resources in a REST style.
>> And I thought that there comes a nice supplement or add-on that comes
>> with devise, namely routes likes this:
>> As I am thinking to do some test with devise and the cancan branch,
>> what types of groups were you thinking of using? What groups would be
>> added in the demo data? Are the groups roles based, location based or
>> job based for example?
>> thanks and best regards,
>> patrick
>> On Mon, May 7, 2012 at 11:12 AM, Steve Kenworthy <stevey...@gmail.com>
>> wrote:
>> > Ben has also been working on a 'cancan' branch for ffcrm with a view to
>> > strengthen group permissions and flexibility.
>> > As these branches affect similar parts of the system, it would be good
>> > to
>> > make sure they work nicely together.
>> > FFCRM + devise + cancan would be a very appealing setup.
>> > Thanks to you both.
>> > Steve
>> > On Mon, May 7, 2012 at 5:57 AM, ben tillman <ben.till...@gmail.com>
>> > wrote:
>> >> Hi Patrick,
>> >> Good point about the password migration. I think devise would by
>> >> default need to use the same sha, otherwise current accounts would
>> >> have no way to authorize. Thanks for looking into this.
>> >> On 7 May 2012 02:12, patrickm <mulder.patr...@gmail.com> wrote:
>> >> > Hello,
>> >> > I saw an open issue for using openid with FFC here:
>> >> > https://github.com/fatfreecrm/fat_free_crm/issues/108 - and there is
>> >> > a
>> >> > small discussion whether devise should be introduced for this.
>> >> > Since it's a good opportunity to get a better understanding of both
>> >> > devise and FFC, I started work to setup devise authentication for FFC
>> >> > https://github.com/mulderp/fat_free_crm/tree/devise
>> >> > So far, I have the login with FFC views working, and started fixing
>> >> > the specs now. Currently, I am still having some issues around the
>> >> > users_controller since devise has naturally some impact there
>> >> > (password reset, rendering user data for other users).
>> >> > It would be great to hear your feedback, or eventually interest in
>> >> > collaboration on this. I guess, once devise is working, using openid
>> >> > should be only a small step. What would be needed more eventually, is
>> >> > a rake task to migrate authlog user based passwords into devise based
>> >> > passwords (have not yet looked into it, maybe devise can 'read'
>> >> > authlogic sha's too)
>> >> > Thanks for your interest.
>> >> > best,
>> >> > patrick
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups "Fat Free CRM Developers" group.
>> >> > To post to this group, send email to
>> >> > fat-free-crm-dev@googlegroups.com.
>> >> > To unsubscribe from this group, send email to
>> >> > fat-free-crm-dev+unsubscribe@googlegroups.com.
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Fat Free CRM Developers" group.
>> >> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>> >> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/fat-free-crm-dev?hl=en.
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Fat Free CRM Developers" group.
>> > To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > fat-free-crm-dev+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/fat-free-crm-dev?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
On Thu, May 10, 2012 at 5:32 AM, ben tillman <ben.till...@gmail.com> wrote:
> Yes the cancan branch implements group permissions, but is still
> failing specs I really need to go in and fix them but have been busy
> on another project. If someone would like to volunteer for a spec
> fixing session feel free :)
Hi Ben!
I had a bit of time this morning to fix some specs related to the
missing partial permission spec. If I am right, the main issues are
around the view specs, the rest looks good. As I was working from a
Starbucks without web access, I am going to push my commits this
evening after work.
> On Thu, May 10, 2012 at 5:32 AM, ben tillman <ben.till...@gmail.com> wrote:
>> Yes the cancan branch implements group permissions, but is still
>> failing specs I really need to go in and fix them but have been busy
>> on another project. If someone would like to volunteer for a spec
>> fixing session feel free :)
> Hi Ben!
> I had a bit of time this morning to fix some specs related to the
> missing partial permission spec. If I am right, the main issues are
> around the view specs, the rest looks good. As I was working from a
> Starbucks without web access, I am going to push my commits this
> evening after work.
> BR,
> Patrick
> --
> You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
hm.. Github also included the commits with respect to synching the
cancan branch to master. Not sure, if that's the right process for
submitting a pull request.
The commit with the fixes for the view specs is actually:
https://github.com/mulderp/fat_free_crm/commit/7beceb65cfce021b9e8b75...
But I am still observing the common practices for doing this (synching
a feature branch with master, take a clean branch, and re-submit the
pull-request, etc. the mysteries of git rebase... ;-) )
On Wed, May 16, 2012 at 9:45 AM, ben tillman <ben.till...@gmail.com> wrote:
> Hi Patrick,
> Thanks a lot for that. Looking forward to your pull request :)
> On 16 May 2012 18:51, Patrick Mulder <mulder.patr...@gmail.com> wrote:
>> On Thu, May 10, 2012 at 5:32 AM, ben tillman <ben.till...@gmail.com> wrote:
>>> Yes the cancan branch implements group permissions, but is still
>>> failing specs I really need to go in and fix them but have been busy
>>> on another project. If someone would like to volunteer for a spec
>>> fixing session feel free :)
>> Hi Ben!
>> I had a bit of time this morning to fix some specs related to the
>> missing partial permission spec. If I am right, the main issues are
>> around the view specs, the rest looks good. As I was working from a
>> Starbucks without web access, I am going to push my commits this
>> evening after work.
>> BR,
>> Patrick
>> --
>> You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
On Thu, May 10, 2012 at 4:23 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> Perhaps, you could make devise do a similar thing... provide the framework
> but leave the details to the user. And then perhaps provide a plugin that
> shows how one might leverage the framework to turn the features into a
> 'jobs' based setup or a 'location' based one (hopefully with just a few
> lines of code).
Just a small update regarding my experiments with Devise. I encounter
a bit of problems when trying to migrate Authlogic user authentication
to Devise based authentication. Devise authentication can be used for
_new_ FFCRM installations without problems, but in my view, without
asking users to re-enter a new password, backwards compatibility of
passwords is an open discussion.
However, there are some inspiring discussions for the Spree framework,
that show some interesting authentication themes:
I think it is possible to switch devise authentication into
authlogic_sha512 mode. This means you can use devise but maintain the old
encrypted passwords. (they've just refactored this out into a
devise-encryptable gem)
For new installations, it would be good to offer the default devise
authentication strategy (I don't know what that is), but we could have a
config.yml setting to tell devise to use authlogic_sha512 for backwards
compatibility.
> On Thu, May 10, 2012 at 4:23 AM, Steve Kenworthy <stevey...@gmail.com>
> wrote:
> > Perhaps, you could make devise do a similar thing... provide the
> framework
> > but leave the details to the user. And then perhaps provide a plugin that
> > shows how one might leverage the framework to turn the features into a
> > 'jobs' based setup or a 'location' based one (hopefully with just a few
> > lines of code).
> Just a small update regarding my experiments with Devise. I encounter
> a bit of problems when trying to migrate Authlogic user authentication
> to Devise based authentication. Devise authentication can be used for
> _new_ FFCRM installations without problems, but in my view, without
> asking users to re-enter a new password, backwards compatibility of
> passwords is an open discussion.
> However, there are some inspiring discussions for the Spree framework,
> that show some interesting authentication themes:
> So, eventually, Devise is a nice option to keep in the back of the head.
> Cheers,
> Patrick
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
On Thu, Jun 7, 2012 at 4:31 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> Hi Patrick,
> I think it is possible to switch devise authentication into authlogic_sha512
> mode. This means you can use devise but maintain the old encrypted
> passwords. (they've just refactored this out into a devise-encryptable gem)
> For new installations, it would be good to offer the default devise
> authentication strategy (I don't know what that is), but we could have a
> config.yml setting to tell devise to use authlogic_sha512 for backwards
> compatibility.
> On Thu, Jun 7, 2012 at 4:31 AM, Steve Kenworthy <stevey...@gmail.com>
> wrote:
> > Hi Patrick,
> > I think it is possible to switch devise authentication into
> authlogic_sha512
> > mode. This means you can use devise but maintain the old encrypted
> > passwords. (they've just refactored this out into a devise-encryptable
> gem)
> > For new installations, it would be good to offer the default devise
> > authentication strategy (I don't know what that is), but we could have a
> > config.yml setting to tell devise to use authlogic_sha512 for backwards
> > compatibility.
> I see if I can make some more progress with the rest.
> Cheers,
> Patrick
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> Great! I've also just started focussing more on the cancan branch. I'm keen to get the permissions sorted out soon and into master.
> If anyone else is interested in testing and fixing some, please checkout the branch and play with it. I'll keep pushing my changes regularly.
> Steve
> On Thu, Jul 5, 2012 at 3:39 AM, Patrick Mulder <mulder.patr...@gmail.com> wrote:
> On Thu, Jun 7, 2012 at 4:31 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> > Hi Patrick,
> > I think it is possible to switch devise authentication into authlogic_sha512
> > mode. This means you can use devise but maintain the old encrypted
> > passwords. (they've just refactored this out into a devise-encryptable gem)
> > For new installations, it would be good to offer the default devise
> > authentication strategy (I don't know what that is), but we could have a
> > config.yml setting to tell devise to use authlogic_sha512 for backwards
> > compatibility.
> I see if I can make some more progress with the rest.
> Cheers,
> Patrick
> --
> You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/fat-free-crm-dev?hl=en.
I completed the 'cancan' branch implementation this week and would be keen
for others to try it out... it still uses the underlying Permission table
and hence should be a seemless migration from instances running
fat_free_crm master.
- There is a new admin "groups" tab that enables new groups to be
created/deleted and users can be joined to those groups.
- On the 'users' tab, you can also add a user to multiple groups.
- Users and groups can be set in the 'shared' permissions section of any
entity
- Also handles special 'shared' permissions, such as "copy permissions
from Campaign", when converting a lead
- Some new steak tests for the admin groups tab
- New permissions_spec.rb for testing the permission logic that gets
added when a class 'uses_user_permissions'
Thanks to bstillman for doing a large proportion of this work a while ago.
It's good to have it in a place where we're almost ready to push to master.
Would appreciate feedback and any bug fixes so we can get this into master
soon.
Regards,
Steve
On Thu, Jul 5, 2012 at 3:23 PM, Patrick Mulder <mulder.patr...@gmail.com>wrote:
> Ok, great! I might to clean my devise branch, since it got a bit out of
> synch with master. I'll watch the CanCan branch too. Update soon.
> Am 05.07.2012 um 06:24 schrieb Steve Kenworthy <stevey...@gmail.com>:
> Great! I've also just started focussing more on the cancan branch. I'm
> keen to get the permissions sorted out soon and into master.
> If anyone else is interested in testing and fixing some, please checkout
> the branch and play with it. I'll keep pushing my changes regularly.
> Steve
> On Thu, Jul 5, 2012 at 3:39 AM, Patrick Mulder <mulder.patr...@gmail.com>wrote:
>> On Thu, Jun 7, 2012 at 4:31 AM, Steve Kenworthy <stevey...@gmail.com>
>> wrote:
>> > Hi Patrick,
>> > I think it is possible to switch devise authentication into
>> authlogic_sha512
>> > mode. This means you can use devise but maintain the old encrypted
>> > passwords. (they've just refactored this out into a devise-encryptable
>> gem)
>> > For new installations, it would be good to offer the default devise
>> > authentication strategy (I don't know what that is), but we could have a
>> > config.yml setting to tell devise to use authlogic_sha512 for backwards
>> > compatibility.
>> I see if I can make some more progress with the rest.
>> Cheers,
>> Patrick
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
On Sat, Jul 7, 2012 at 11:52 AM, Steve Kenworthy <stevey...@gmail.com> wrote:
> There is a new admin "groups" tab that enables new groups to be
> created/deleted and users can be joined to those groups.
> On the 'users' tab, you can also add a user to multiple groups.
> Users and groups can be set in the 'shared' permissions section of any
> entity
> Also handles special 'shared' permissions, such as "copy permissions from
> Campaign", when converting a lead
> Some new steak tests for the admin groups tab
> New permissions_spec.rb for testing the permission logic that gets added
> when a class 'uses_user_permissions'
> Thanks to bstillman for doing a large proportion of this work a while ago.
> It's good to have it in a place where we're almost ready to push to master.
> Would appreciate feedback and any bug fixes so we can get this into master
> soon.
It looks great so far.
Eventually, I don't see the groups tab enabled by default. Should we
use something like this in settings.yml:
> On Sat, Jul 7, 2012 at 11:52 AM, Steve Kenworthy <stevey...@gmail.com>
> wrote:
> > There is a new admin "groups" tab that enables new groups to be
> > created/deleted and users can be joined to those groups.
> > On the 'users' tab, you can also add a user to multiple groups.
> > Users and groups can be set in the 'shared' permissions section of any
> > entity
> > Also handles special 'shared' permissions, such as "copy permissions from
> > Campaign", when converting a lead
> > Some new steak tests for the admin groups tab
> > New permissions_spec.rb for testing the permission logic that gets added
> > when a class 'uses_user_permissions'
> > Thanks to bstillman for doing a large proportion of this work a while
> ago.
> > It's good to have it in a place where we're almost ready to push to
> master.
> > Would appreciate feedback and any bug fixes so we can get this into
> master
> > soon.
> It looks great so far.
> Eventually, I don't see the groups tab enabled by default. Should we
> use something like this in settings.yml:
> --
> You received this message because you are subscribed to the Google Groups
> "Fat Free CRM Developers" group.
> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> fat-free-crm-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/fat-free-crm-dev?hl=en.
> It's basically added there but of course, with the current settings
> architecture, you have to turn it on to see it.
> That's another thing I'd love to get to soon... not sure if I will though.
> Glad you've had no problems... I'll be doing final testing this week,
> including migrations from current ffcrm instances to confirm things don't
> break.
> steve
> On Mon, Jul 9, 2012 at 7:56 PM, Patrick Mulder <mulder.patr...@gmail.com>wrote:
>> On Sat, Jul 7, 2012 at 11:52 AM, Steve Kenworthy <stevey...@gmail.com>
>> wrote:
>> > There is a new admin "groups" tab that enables new groups to be
>> > created/deleted and users can be joined to those groups.
>> > On the 'users' tab, you can also add a user to multiple groups.
>> > Users and groups can be set in the 'shared' permissions section of any
>> > entity
>> > Also handles special 'shared' permissions, such as "copy permissions
>> from
>> > Campaign", when converting a lead
>> > Some new steak tests for the admin groups tab
>> > New permissions_spec.rb for testing the permission logic that gets added
>> > when a class 'uses_user_permissions'
>> > Thanks to bstillman for doing a large proportion of this work a while
>> ago.
>> > It's good to have it in a place where we're almost ready to push to
>> master.
>> > Would appreciate feedback and any bug fixes so we can get this into
>> master
>> > soon.
>> It looks great so far.
>> Eventually, I don't see the groups tab enabled by default. Should we
>> use something like this in settings.yml:
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Fat Free CRM Developers" group.
>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/fat-free-crm-dev?hl=en.
We hit a major milestone today when we introduced the 'cancan' branch into
fat_free_crm master.
This means that groups can now be created in the admin interface and then
used to 'share' contacts, opportunities, accounts etc. It also means that
the permissions refactoring that has been underway for a while has now been
completed.
To see the admin groups tab so you can create groups and add users to them,
you'll need to update your settings.yml file to ensure that groups are in
the admin tab. See config/settings.default.yml line 225.
We've tested this pretty hard on the 'cancan' branch before bringing the
feature into master, but as this is a feature that touches on many core
parts of the system, please be vigilant and quickly flag any issues that
arise so that we can address them. I will endeavour to respond quickly as
issues arise.
It's an exciting moment as it provides us with a much more flexible
permissions system that will lend itself to all sorts of innovative
solutions as they arise. See app/models/users/ability.rb for where the
permissions are currently defined. The possibilities are limitless as to
what could effectively go here e.g. permissions based on a particular tag
or inherited from a related model... such as being given permission to view
contacts that belong to an account you already have permissions for... and
so on...
Thanks to all those who had a part in this feature. In particular, Ben
Tillman (warp) who wrote the core sections of this feature.
Regards,
Steve Kenworthy
On Fri, Jul 13, 2012 at 5:16 PM, Steve Kenworthy <stevey...@gmail.com>wrote:
>> It's basically added there but of course, with the current settings
>> architecture, you have to turn it on to see it.
>> That's another thing I'd love to get to soon... not sure if I will though.
>> Glad you've had no problems... I'll be doing final testing this week,
>> including migrations from current ffcrm instances to confirm things don't
>> break.
>> steve
>> On Mon, Jul 9, 2012 at 7:56 PM, Patrick Mulder <mulder.patr...@gmail.com>wrote:
>>> On Sat, Jul 7, 2012 at 11:52 AM, Steve Kenworthy <stevey...@gmail.com>
>>> wrote:
>>> > There is a new admin "groups" tab that enables new groups to be
>>> > created/deleted and users can be joined to those groups.
>>> > On the 'users' tab, you can also add a user to multiple groups.
>>> > Users and groups can be set in the 'shared' permissions section of any
>>> > entity
>>> > Also handles special 'shared' permissions, such as "copy permissions
>>> from
>>> > Campaign", when converting a lead
>>> > Some new steak tests for the admin groups tab
>>> > New permissions_spec.rb for testing the permission logic that gets
>>> added
>>> > when a class 'uses_user_permissions'
>>> > Thanks to bstillman for doing a large proportion of this work a while
>>> ago.
>>> > It's good to have it in a place where we're almost ready to push to
>>> master.
>>> > Would appreciate feedback and any bug fixes so we can get this into
>>> master
>>> > soon.
>>> It looks great so far.
>>> Eventually, I don't see the groups tab enabled by default. Should we
>>> use something like this in settings.yml:
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Fat Free CRM Developers" group.
>>> To post to this group, send email to fat-free-crm-dev@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> fat-free-crm-dev+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/fat-free-crm-dev?hl=en.