Thanks, I will look into.

Also how is the "verify password" field generated on the "Registration Form" seems like that is a "virtual field"

As I mentioned yesterday that field is missing its css class selector so the form does not view correctly once you modify the css.

You can check there. But I will re-post here.

<tr  id="auth_user_password__row">
<td  class="w2p_fl"><label  
for="auth_user_password"id="auth_user_password__label">Password:</label></td>
<td  class="w2p_fw"><input  
class="password"id="auth_user_password"name="password"type="password"value=""/></td>
<td  class="w2p_fc"></td></tr>

<tr  id="auth_user_password_two__row"><td><label>Verify Password:</label></td>
<td><input  name="password_two"type="password"/></td><td>please input your password 
again</td>
</tr>



On 12/30/10 3:07 PM, mdipierro wrote:
these are the list lines in the SQLFORM constructor:

         elif type(formstyle) == type(lambda:None):
             table = TABLE()
             for id,a,b,c in xfields:
                 td_b = self.field_parent[id] = TD(b,_class='w2p_fw')
                newrows = formstyle(id,a,td_b,c)
                 if type(newrows).__name__ != "tuple":
                     newrows = [newrows]
                 for newrow in newrows:
                     table.append(newrow)

perhaps we can make this more general?

On Dec 30, 1:59 pm, "David J."<[email protected]>  wrote:
What is the best way to create a new FORM renderer?

How can I override or add a new form render type, ie instead of
"table|div|ul"?

Thanks.

Reply via email to