mbajames
Results 1 - 2 of 2
bymbajames, December 19, 2009
I really wanted to be able to use this plug-in as its premise is great. However, when doing as the author states (with CB 1.2.1), adjusting tab order and field order, the field is always placed either at the absolute top or bottom of my registration form, as I have 20 custom fields on the form (not just name, username, password, password verification, and email).
When it is in the absolute top position I have tried moving the fields all the way up...no luck, it is always absolutely at the top. If I change the tab order more (it goes to the absolute bottom below the custom fields). Without instructions on how to adapt it when a registration form has custom fields the plugin is not achieving its potential.
When it is in the absolute top position I have tried moving the fields all the way up...no luck, it is always absolutely at the top. If I change the tab order more (it goes to the absolute bottom below the custom fields). Without instructions on how to adapt it when a registration form has custom fields the plugin is not achieving its potential.
Owner's reply
If you contact me directly through Source Forge I may be able to help you. It does not appear to be possible, although I haven't read enough to know for sure, to place a field in the middle on the core Contact Info fields. The trick is to order the tabs so that the Confirm Email tab appears just below the Contact Info tab, and then reorder the fields within the Contacy Info tab so the Email field is at the bottom. In this way the Email field will be just above the Confirm Email field. Again, if you contact me directly I may be able to help.
The flaw is that the component uses some common css which can conflict with templates. That is, the component uses the div id "footer" which means if you use it in your template you will have 2 footers rendered on a page. So, you either have to go into the component files and change all instances of #footer or do so in your own template and css file.
The flaw was major enough that I will not use it until I can get all instances cleaned from the component as I write all my templates using the footer id.