Issue 12749

Restyle register page

Reporter: mdoering
Assignee: cvizitiu
Type: Bug
Summary: Restyle register page
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2013-02-19 10:04:07.643
Updated: 2013-09-02 13:46:32.315
Resolved: 2013-06-20 13:35:11.392
Description: Similar to POR-549 the user registration page needs to be restyled:

1 - No tab menu should be shown at all
2 - page title and infoband heading should be "Register New GBIF Account" instead of "User page - "
3 - Form needs to be restyled matching the vizzuality design (see 2nd screenshot)

Attachment original registration.png

Attachment registration.png

Created: 2013-02-19 10:07:55.983
Updated: 2013-02-19 10:07:55.983
See the original vizzuality design:

I would slightly modify this be keeping the green infoband banner and remove the need for several pages (we dont have many user properties to register right now)

Created: 2013-06-19 19:55:36.238
Updated: 2013-06-19 20:53:50.643
Changing the very form markup for the registration form in order to look like the Vissuality design using the styles means we have to follow Vizzuality's design down to 
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: ; 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.

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:

it should read "Register new GBIF account" instead of SIGN IN TO GBIF


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

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: