-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Creating Accounts #1
Comments
Hi. A quick fix would be a) a migration to set nullable the avatar fill b) change on the DB directly 👍 |
marktopper
pushed a commit
that referenced
this issue
Nov 26, 2016
Fixed route for update table in database tool
Closed
marktopper
pushed a commit
that referenced
this issue
Apr 6, 2017
marktopper
pushed a commit
that referenced
this issue
Jun 21, 2017
add required attribute on required input field to prevent db error
marktopper
pushed a commit
that referenced
this issue
Aug 23, 2017
* Preserve file upload name when option is set * Adding default functionality for image name to be preserved * Getting the styleci tests to pass * Fixing the primary key issue that was introduced after PR 1452
Closed
Closed
Closed
This was referenced May 15, 2018
Closed
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not so much a issue however to be able to add users without having a image would be cool out of the box. At the moment it spits out a SQL Error. However im guessing its a fairly simple fix of allowing avatar to be null.
Error:
"
QueryException in Connection.php line 763:
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'avatar' cannot be null (SQL: insert into
users
(name
,email
,password
,avatar
,updated_at
,created_at
) values (Dad, dad@dad.com, $2y$10$jZPJuDv/gyXLwSKVhx7Z7uohCf1/MqUmZv7cNJnIVrcLIEsESgAay, , 2016-10-28 02:33:34, 2016-10-28 02:33:34))"
The text was updated successfully, but these errors were encountered: