Facebook error: You have not defined a path for the route alias postLoginPath. about mongoose-auth

I'm using:

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Oh yeah - [email protected]/[email protected]

It's happening, of course, when setting up the routes:

mod_mongoose = require('mongoose');
mod_mongooseAuth  = require("mongoose-auth");

app = module.exports = mod_express.createServer();

app.configure(function(){
  ...
  mod_mongooseAuth.middleware();
});

[bnoguchi]

Thanks for notifying me of the Issue. The bug is that the code loads ALL of the modules. I just pushed a fix for this. Now, modules are only enabled when you first access them via everyauth like:

everyauth.facebook;

Or via mongoose-auth like:

schema.plugin(mongooseAuth, {
    facebook: {
        everyauth: {...}
    }
}); // i.e., the modules that are now enabled are the keys of this Object -- i.e., `facebook`

Should be everyauth v0.0.10 now via npm install.

Thanks! Makes sense. I just did a quick npm update of everyauth (verified @0.0.10) and am getting the same error, but I'll dig in a little later and confirm if it's still an issue or not.

[bnoguchi]

Can you send me a gist?

[liamdon]

This was giving me trouble today as well - it works via everyauth but not via mongoose-auth.

I propose the following fix:
https://github.com/bnoguchi/mongoose-auth/pull/2/files

[bnoguchi]

mongoose-auth does not need a patch. The issue lies with everyauth. I just fixed this completely this time. Install everyauth v0.1.0 via

$ npm install everyauth

Thanks - seems to be working now (at least not crashing on startup.) I also
noticed that node was still using the older 0.9.0 everyauth when I followed
up, have upgraded/forced 0.1.0 and it's looking good, thanks.

Jason Bond Pratt
President/CTO, Tixelated
202.841.8396
http://tixelated.com/[email protected]

http://tixelated.com/
http://tixelated.com/ [email protected]://tixelated.com
http://twitter.com/tixelated

On Thu, Apr 14, 2011 at 1:49 PM, bnoguchi <
[email protected]>wrote:

mongoose-auth does not need a patch. The issue lies with everyauth. I just
fixed this completely this time. Install everyauth v0.1.0 via

$ npm install everyauth

Reply to this email directly or view it on GitHub:
#1 (comment)