SQL error on user information update about laravel-4-bootstrap-starter-site HOT 11 CLOSED

The username field is in the form. What url are you getting this at?

Both admin/users/create and users/create are working for me.

from laravel-4-bootstrap-starter-site.

Apologies Andrew, I think I've thrown you off course here, it's not the create routes it's the profile update/user index routes (e.g. www.example.com/user). Try submitting this form? It has no username field and it also submits to postIndex() which seems quite tailored for the create submission (which is why i was wondering if there should be a postCreate() or postIndex() is supposed to handle user registration and user updates.

from laravel-4-bootstrap-starter-site.

Ah, got it. I thought I had removed that page. I'll patch it up.

from laravel-4-bootstrap-starter-site.

Great work, will have a look at this now. Just to let you know you have a duplicate form close tag in / app / views / site / user / index.blade.php

from laravel-4-bootstrap-starter-site.

And ln57 of UserController.php should be

            ->with( 'notice', Lang::get('user/user.user_account_updated') );

not

            ->with( 'notice', Lang::get('user.user.user_account_updated') );

from laravel-4-bootstrap-starter-site.

This still redirects to user.login even when the user is updating their details? They're already logged in so should probably direct to their profile page or something?

from laravel-4-bootstrap-starter-site.

Also, the update form only updates if the user enters their password/confirm password, that's probably not desired behaviour is it? They shouldn't have to do that if they're already logged in.

If they don't enter their password, they updates don't take effect but you still get the message 'user account updated'.

(sorry for all the comments, should I raise new issues?)

from laravel-4-bootstrap-starter-site.

There is also an error on submission of the user/create form (using {{ Confide::makeSignupForm()->render() }} to generate the form)

The error is:

Missing argument 1 for UserController::postIndex()

Because that function is now expecting a User object? I think the function still has dual purposes (probably by design) of handling user creation and user updates but isn't quite handling both (either) at the moment.

from laravel-4-bootstrap-starter-site.

Any thoughts?

from laravel-4-bootstrap-starter-site.

I see you've been doing fixes.... that relate to this also 👍

from laravel-4-bootstrap-starter-site.

Yeah I'll have this updated shortly when I merge the phpunit test branch.

from laravel-4-bootstrap-starter-site.