Jonknee, I agree with you. It's better to fill a little form and then upload
the photo; but I also need to upload product's pictures in BackOffice all in
one form.
What you say applies also to it, sure; but would be nicer if I can make
everything in one step.
That's why I asked the group: how do
> I think a good choice may be Submit user info using AJAX and if everything's
> OK, upload photo.
Hmm, that would probably work nicely. Another way (one that I
appreciate as a user) is to have a small sign up form and then let
users expand their profile. Just get the bare minimum and then once
t
Hi
That's what I would like to avoid: re-upload the photo. I would like to
upload photo, leave it in temp files; show the user the uploaded photo
without creating its account, and reporting each error he has commited as
"Username already used".
I think a good choice may be Submit user info using
> But what happens when Model does not validate, Insert is not done and there
> is no ID to use as filename?
If the registration form didn't validate, why would you bother doing
anything with the file? They are going to get an error and have to
resubmit the form (with a new photo).
--~--~
I'm doing something similar but images are not uploaded until a user
has been enabled, so the ID will already exist, of course. You may not
have that luxury. I do have a resumé upload but, instead of using the
UID, I'm naming it after the user's name. I'm already creating a
"slug" anyway from the
