Devise Functionality

[William G.K. Zhang]

Hey Sam, in the Devise mailing list, you said that you may make some additional modifications to this gist and perhaps submit that as a pull request or make a gem based around it.  Any update to that by any chance? 

Thanks,

William Zhang

[Sam Pohlenz]

Hi William,

I haven't had a chance yet to revisit that code yet, particularly as I rarely use Devise. Are you currently using the code from the gist successfully? If so, I may consider that a vote to put something together soon.

Alternatively, if you feel like putting together your own gem based on the code (e.g. mongomodel-devise), I'd be more than happy to endorse it by linking it from the MongoModel README.

Regards,
Sam

William G.K. Zhang wrote:

--
You received this message because you are subscribed to the Google Groups "MongoModel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongomodel+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Sam Pohlenz | Wheelhouse Labs | www.wheelhousecms.com
+61 8 8842 1872 | @spohlenz | Skype: SamPohlenz

[William G.K. Zhang]

I have not actually used it just yet but I will be doing so shortly.  I'll report back and let you know if I find any issues.

[William "G.K." Zhang]

I've been using this gist for a few months now and pretty much everything has been going pretty well.  It's been relatively pain free and I'm really happy with it.  

I did run into one small problem today though.  If you destroy an account with Devise, it tells the ORM to destroy the object first and then logout.  However, when Devise/Warden  logs out, it tries to write some data to the object.  The problem is that whenever MongoModel destroys an object, it freezes it afterwards.  So an exception occurs whenever it tries to logout and write data to that frozen object.  

To solve this, you can roll your own controller and inherit the Devise registration controller.  Just copy the code from the destroy function from Devise and make sure to call the logouts before you destroy the object.  

I've forked the gist and added the modifications pertaining to this problem here: https://gist.github.com/williamgkzhang/5817457

------------------------------------------------

William "G.K." Zhang
william...@gmail.com
infinit...@gmail.com

(337) 205-4844

--
You received this message because you are subscribed to a topic in the Google Groups "MongoModel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mongomodel/1fR7gvwECCc/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to mongomodel+...@googlegroups.com.