@ Soshite:
Each Checkbox should have a separate table column. A checkbox can only have two values, "on" if it is checked, or blank if it is unchecked. If you have an input on your form like this:
<input type="checkbox" name="fan_group1" />
if the user checks this box, WebLoginPE will store a value of "on" in the table column. If they did not check the box, the column will have no value.
Take a look at the parameter
&inputHandler in the documentation to see how you can use this for <select> options, checkboxes an radio buttons AND have WebLoginPE automatically check/select the user’s stored values.
So if the user checked "fan_group1" and you have it in the &inputHandler parameter, the next time the user edits their profile, the checkbox will already be checked for them. It is smart like that.
For your PPP table, you should be able to just change the name of the ’webuser’ column to ’internalKey’.
If the PPP table uses the MODx table prefix, then that is good, just pass the table name as the value for &customTable and list all it’s columns in &customFields (separated by commas).
Example:
If your tables name is "web_user_customtable", and with the table prefix it is stored in the DB as "modx_web_user_customtable", you would use &customTable=`web_user_customtable`.
If it was stored in the DB without using the table prefix (i.e. all your MODx tables look like modx_whatever, but the PPP table looks like "my_user_table" without the usual prefix) then you can use the new parameter &prefixTable=`0` (default is 1) and it will not auto append your MODx table prefix when it is looking for the table in &customTable.
It is really very flexible.
A lot of this stuff is in 1.3.0 and full documentation will accompany. It is essentially done except the documentation. I am hoping to post it in the repository tonight.
-sD-
Dr. Scotty Delicious, Scientist DFPA.