level; it can be achieved in two ways:
1. Customise a core Drupal function by copying it to our template file (like I had to do for the pager) e.g. here: http://www.silviogutierrez.com/blog/advanced-drupal-7-form-element-theming/ ; the biggest downside is that one must keep track of core Drupal function changes, understand new code and keep-up at each upgrade.
2. Try and manually render the form only asking Drupal for the form ids and likes; login form underlying format should in theory easily to track should it change; biggest downside: inserting additional checks (e.g. CAPTCHA) becomes ugly.
I'll try version 2 as it seems more straight forward.
Update: bad idea as the form values will NOT be kept between attempts.
Author: mdoering@gbif.org
Created: 2013-06-20 11:01:36.612
Updated: 2013-06-20 11:01:36.612
The registration page title in the infoband header is still wrong on uat:
http://uat.gbif.org/user/register
it should read "Register new GBIF account" instead of SIGN IN TO GBIF
Author: cvizitiu@gbif.org
Comment: Olivery Meyn *SPECIFICALLY* FORBADE me from migrating changes from "staging" to "dupallive"; in hist own words: "That's what staging is for; changes are migrated to drupallive once we've got them approved". So please check-out chnages on staging, on Friday they're supposed to be frozen and migrated to drupallive/uat. If the plan has changed please let me know but a little clarification within the dev team will for sure help.
Created: 2013-06-20 12:04:07.884
Updated: 2013-06-20 12:04:16.203
Author: mdoering@gbif.org
Created: 2013-06-20 12:11:45.88
Updated: 2013-06-20 12:11:45.88
... and he is right, thanks for the staging reminder. That looks pretty nice!
The usage agreement link has an extra bracket at its end: http://data.gbif.org/tutorial/datauseagreement)