-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when clicking 'get my invite' #169
Comments
WARNING: the invite form does not currently appear to work
same issue here |
same here. going back to 0.8.1 brings up a syntax error. can't get login screen to work. |
Encountering this issue as well, used the one-click heroku deploy link in the readme. Of possible note: the first person to sign-up to this channel via slackin seems to have done so without any issues. All following attempts are resulting in errors. |
I'm using slackin on my own server and this change fixes the issue for me, if anyone else needs it in the meantime:
|
Worked fine for me. Thanks @nbolt ! |
Provided by rauchg#169
Yes, the fix works for me too. Should be rolled in to a new release. |
issue #169, add turnary assignment for client sdk channels
I have the same issue with Slackin version 0.8.3 even after applying the fix which changes When adding an email to the list the following error does still occur: You can test for yourself at http://ec2-54-175-247-25.compute-1.amazonaws.com:3000/ |
PRs welcome! |
Oh and where does Slackin log to? My above mentioned error (undefined value) was not visible in Slackin console output on the server. |
@nbolt thanks - that worked for me on 0.8.3 |
starting slackin with:
slackin {my_team_name} xoxp-276xxx505139-xxxxxxxxx-xxxxxxx-4xxx0e3x5 -h localhost -p 3001
When adding an email address and clicking 'get my invite', this message appears in the console:
client.js:22 Uncaught TypeError: Cannot read property 'value' of undefined
Screenshots:
https://www.dropbox.com/s/iq3lwmel0x7etmx/Screenshot%202016-03-18%2023.59.38.png?dl=0
https://www.dropbox.com/s/cjwokeaefkh8nw0/Screenshot%202016-03-18%2023.59.32.png?dl=0
https://www.dropbox.com/s/zmsroho719gwyyl/Screenshot%202016-03-18%2023.59.48.png?dl=0
node v4.4
npm v2.14
The text was updated successfully, but these errors were encountered: