I had everything working so well with the profile page as I set editable to "yes"
I have the unique id of the table as the "target field name" and also as the "request parameter name"
It all works great until I logged in as a user with no id specified in the url. At this point, it wrongly pulls up the record whose unique id matches the userid of the logged in user (not at all the record that should be loading)
When I am not logged in, no record is pulling up and populating the form
When I use the extra "&id=62" appended on the url, then I pull up the appropriate record.
So it's like it is assigning the "default value" (when nothing is in the url request) as the userid of the person who is logged in.
Placing 0 in the default value of the profile page, doesn't fix this either.
Suggestions?
I have the unique id of the table as the "target field name" and also as the "request parameter name"
It all works great until I logged in as a user with no id specified in the url. At this point, it wrongly pulls up the record whose unique id matches the userid of the logged in user (not at all the record that should be loading)
When I am not logged in, no record is pulling up and populating the form
When I use the extra "&id=62" appended on the url, then I pull up the appropriate record.
So it's like it is assigning the "default value" (when nothing is in the url request) as the userid of the person who is logged in.
Placing 0 in the default value of the profile page, doesn't fix this either.
Suggestions?