Quote:
Originally Posted by Geisthund99
I ran the sql
now getting
This appears to be related to table prefix I add to the sql statement.
SELECT userid FROM dc_membermap WHERE userid = ".$vbulletin->userinfo['userid']
This works:
SELECT userid FROM vb_dc_membermap WHERE userid = ".$vbulletin->userinfo['userid']
The map appears fine.
It might be nice to have the map import users location from their profiiles. Just a thought cheers
Gareth
|
Though it sounds great, there are two reason why it would be better to not do that:
#1. It'll have to use Google's geo search function to mass convert all this data. They put restrictions on how many times per day (and how fast) you can do that. You'll quickly get yourself blocked if you do 8k* queries right after each other to get all the data.
* Depending on the size of the member base of course.
#2. Like soniceffect stated above, some cities are interpreted wrongly as they exist in multiple countries. There's a fairly big chance members will be put in the US while they actually live in the UK for example. Lots of people neglect to define their location properly.