-
Notifications
You must be signed in to change notification settings - Fork 2
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 with new user registration when annotation is disabled #36
Comments
I think I know what the issue is. I'll fix it and let you know. Thanks for pointing it out. |
@marksilvis before you go ahead to do any fixes, @kvb2univpitt pointed out that I'll just need to update the database tables using a shell script to add the "first_name" column on AWS. And he'll also make some changes in causal-web to disable the javascript calls to the annotation server when annotation is disabled in Causal Web. |
@yuanzhou I think disabling calls when the profile is not set is a good idea. This particular annotations service call is done on the server, though, so I don't think that would be sufficient to solve this issue. |
User registration failed is because the columns for the person table in the MySQL database need to be updated. Execute the following command to update the columns: |
@kvb2univpitt That is part of it, but does not resolve the MalformedURLException. Changing the database column does fix the registration failure, just not all exceptions listed. |
@kvb2univpitt I just updated the database table using the 3 lines of SQL queries and now I can register new users. |
@marksilvis Other exceptions should be individually reported as new issue. This issue is pertaining to user registration. We should close this issue if the user registration is fixed. I am closing this issue since @yuanzhou confirmed that it is resolved. Feel free to open it again if you think otherwise. |
On AWS I disabled the annotation profile, but when registering new users, I still got this error related to "Column 'first_name' cannot be null":
The according log says:
@kvb2univpitt @marksilvis please take a look at this issue. I noticed this issue couple weeks ago and I thought we got it fixed. I'm using the v1.3.1 branch with d3 improvements: https://github.com/bd2kccd/causal-web/tree/v1.3.1-d3-improvements. Except the d3 updates, everything else should be the latest code.
The text was updated successfully, but these errors were encountered: