-
- 1,193 Posts
No.
This is just the way WebLoginPE works to make sure that data you have not provided in a form does not get overwritten.
WebLoginPE uses an array of all the columns in the default attributes table, then loops $_POST to see if those columns are in there. if they ARE NOT, then they are not posted to the db. so if you previously filled out the zipcode, then set it to ""(blank), well that value will not end up in the $_POST Array and thus not end up being saved into the database.
Using the "Zip code" example:
Let’s say you have a userprofile form where you DO NOT let them edit the zip code, so you do not provide a text input named "zip". If WebLoginPE did not work the way it does, the zip column in the database would be set to blank everytime the user saved their profile since no value was passed for it. That is why I had it loop through and get rid of fields with no value before saving to the db.
You can change the value to whatever you want, just not (Blank). This is simple data protection 101.
-sD-
Dr. Scotty Delicious, DFPA
-
- 1,193 Posts
Interesting.
I am glad you found the solution, and thanks for sharing it. I wonder what was causing the conflict?
Anyway, glad you have it sorted out.
-sD-
Dr. Scotty Delicious, DFPA.