People list not updated when someone logs in?

[mario]

No description provided.

[mario]

Could this possibly be related to /remote/faye return 400 bad request? Using passenger 4.0.2 and nginx 4.1. I tried both master and 1.2 (which still needs a refresh for room to appear :P)

[mario]

Update: this is the error I have in the logs:

[ERROR] [Faye::RackAdapter] undefined method `call' for nil:NilClas

[choclo]

I tried it today and have the same issue. Also running passenger v4.0.2 with Apache2 though. There are no errors whatsoever, but when someone writes in the room you have to refresh the whole thing to see it.

[fusion94]

Are you running from MASTER or the latest tagged release?

[mario]

I tried both

On Friday, May 24, 2013, Tony Guntharp wrote:

Are you running from MASTER or the latest tagged release?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/270#issuecomment-18375466
.

[choclo]

I had to run:

# bundle exec rake db:migrate kandan:bootstrap

rake assets:precompile:all

I believe the latter can be causing this?

[fusion94]

I know that MASTER is broken but that the latest tagged release 1.3 was working.

[mario]

There is no 1.3? Latest tagged is 1.2?

[krzyzanowskim]

looks like master branch is still affected with this issue, isn't he ?

[coreylafferty]

I'm seeing this on Master. Some people show in the PEOPLE list and have connect/disconnect messages... many do not. Don't really see a pattern to it, but will post if I can find anything that will narrow it down.

[scouttyg]

Hey guys.

This one was a huge pain in the butt. The main thing to note is this is because Devise was updated on the Kandan app without realizing that authentication_token was necessary towards adding a user to the Active Users. If you had upgraded from an old version of Kandan, you wouldn't know anything was wrong because the authentication_token field would already still be there with values in it whereas if you created a new app none of those tokens would be there.

The main way to fix this is to set an authentication_token for each one of your users, and make sure to create a token when you create/save a user. I ended up using the gist here:

https://gist.github.com/josevalim/fb706b1e933ef01e4fb6#file-1_unsafe_token_authenticatable-rb

specifically, the before_save :ensure_authentication_token, and the ensure_authentication_token and generate_authentication_token methods. You'll then have to run through each user and save them to "generate" the tokens.