Skip to content
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

"Start a group" not redirecting correctly #161

Closed
taoeffect opened this issue Jan 6, 2017 · 3 comments
Closed

"Start a group" not redirecting correctly #161

taoeffect opened this issue Jan 6, 2017 · 3 comments

Comments

@taoeffect
Copy link
Member

taoeffect commented Jan 6, 2017

Problem

With latest changes in #155 (commit eb64870).

Multiple issues with "Start a group":

  1. Clicking "Start a group" highlights "New User" menu item instead of "Start a group" EDIT: Err, I guess this makes sense since we're on the SignUp view.
  2. Proceeding with "Sign Up" results in error. Tried this twice, screenshots from both attempts:

screen shot 2017-01-05 at 7 50 31 pm

screen shot 2017-01-05 at 7 53 58 pm

Meanwhile, the server console outputs:

Running "watch" task
Waiting...
Gruntfile.js: loading file with babel support: ./backend/index.js
API server running at: http://Alice.local:3000
Debug: handler, error
    {"msec":12.488315999507904,"error":"Not Found","data":{"data":null,"isBoom":true,"isServer":false,"output":{"statusCode":404,"payload":{"statusCode":404,"error":"Not Found"},"headers":{}},"message":"Not Found"}}

Solution

  1. Clicking "Start a group" should highlight "Start a group" tab/menu
  2. Clicking "Sign Up" should redirect to group creation screen. Right now it's trying to load localhost:8000/user/ for some reason, and it also fails to load even that.
@taoeffect
Copy link
Member Author

Added label Kind:Test: Should probably create a test for this as well so that we can automatically check this for correct behavior in the future.

@vijayee
Copy link
Contributor

vijayee commented Jan 12, 2017

It is not redirecting to the localhost:3000/user/ but failing to make the xhr request to the backend at that route due to it being removed. It now fails the CORS request. It should redirect correctly once a new login scheme is created.

@vijayee
Copy link
Contributor

vijayee commented Feb 21, 2017

Fixed in #186

@vijayee vijayee closed this as completed Feb 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants