Hey there, this module is used by drupal.org, and as part of the https://drupal.org/community-initiatives/drupalorg/drupal7 D7 Upgrade Initiative, we need to plan and test a stable upgrade path prior to launch.
What will it take to get a tried and tested upgrade path for this module out the door before July 15th, 2012 so we can test it in-place during the QA phase? Let's use this issue to investigate and generate a bullet-point list of things that need to happen (or a list of links to other issues).
Comments
Comment #1
jm.federico commentedHi Guys
Never done an update for fields from D6 do D7, do you know if there is a guide on what needs to be done (code wise)?
I know there is this (http://drupal.org/node/1144136) but thats just a how-to for site admins, not developers.
Cheers
Comment #2
senpai commented@jm.federico In addition to the Field API docs, you should try using the Coder Upgrade module and the http://upgrade.boombatower.com/tools resource.
Comment #3
senpai commentedJust a reminder: Final QA starts next week, and I'd hate it if this module wasn't ready and we had to put a hold on the entirety of the drupal.org D7 upgrade.
Comment #4
drummWe aren't doing a regular geolocation field upgrade, we are migrating from http://drupal.org/project/html5_user_geolocation to this. drupalorg_update_7004() has been taken care of this since May, with a rewrite for speed from Bdragon, http://drupalcode.org/project/drupalorg.git/blob/refs/heads/7.x-3.x:/dru.... If you view the source of the home page map, you will see lat/lon numbers. And you can log in to set your current location.
The problem seems to be #1820270: Make sure drupalorg JS is included and works.