user profile form not sending data to database

rw1

Moderator
joomla 1.7.3
fabrik-3.0b-361-ge53f068
chrome/firefox

scenario:

user profile form

results:

upon submitting the form i get:

'Record added/updated'

when i go back to the form, the fields are empty (although i want them to be 'saved' and the values from the last submission in there).

when i check the database table prefix_myuserprofile, there are no rows.


my form, list, group, element settings are:

list: myuserprofile

data
connection - site database
link to table - prefix_userprofile
primary key - id
auto increment - yes

publishing
status - published

access
view list - registered
view records - registered
edit records - special or use field id
add records - registered
delete records - special


form: myuserprofile

form processing
record in database - yes

publishing
status - yes

groups
current groups - myuserprofile


group: myuserprofile
all standard, published.


elements: id, date_time, userid, date of birth, favourite color, favourite meal, favourite link

settings for id and date_time
publishing

status - published

access
editable - special
viewable - special

list settings
show in list - yes
link to details - no

settings for userid
hidden - no
user data - name
update on edit - no

publishing
status - published

access
editable - special
viewable - registered

list view settings
show in list - yes
link to details - no

settings for date of birth, favourite color, favourite meal, favourite link
publishing

status - published

access
editable - registered
viewable - registered

list view settings
show in list - yes
link to details - no


and menu item:
type: form
access - registered
form - myuserprofile
row id - '-1' (without the quotes)
key name - userid
 
Change your element's access settings. A registered user can't save anything if id edit access is special (same for userid and date).
 
thanks for your reply.

i changed:

id:
editable - registered
viewable - special

date_time:
editable - registered
viewable - special

userid:
editable - special (this is so they can't change their actual name)
viewable - registered (but they can still see it)

and i am getting the same results as above.
 
i just tried adding a record from the backend via forms > view data > add and it created the necessary row in the database table and is saved in the front end for the user.

what is not resolved is the front end registered user is still not able to complete this process, even though after filling out the form it displays the success message, no data is sent to the database :(
 
pretty hard to tell without seeing the site.
For the elements I'd set everything to registered thats currently special. It doesn't make much sense to have an acl when the user can edit but can't view the element.
 
Same Issue Here

i just tried adding a record from the backend via forms > view data > add and it created the necessary row in the database table and is saved in the front end for the user.

what is not resolved is the front end registered user is still not able to complete this process, even though after filling out the form it displays the success message, no data is sent to the database :(

Did you ever figure this issue out? I'm having the same problem
 
Yup I seem to remember fixing it - no idea what I did though, hard enough to remember last week let alone 10 months ago :)

Possibly something to do with the field that stores the primary key and / or user id not be accessible to the front end user? So try ensuring those elements are published and set to an acl where they are usable to the front end user
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top