Active
Project:
Visitor Info
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2010 at 18:31 UTC
Updated:
19 Aug 2011 at 20:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
twooten commentedSounds like it might be worth looking into. I'll dig in and check it out.
Comment #2
roball commentedThank you.
Comment #3
klonos...just checked one of my test setups and I got hit by the 'You must supply an IPInfoDB API Key in order for Visitor Info to be able to do lookups.' error. I saw the info in the project's page that there was a change in IPInfoDB.com as of November 15, 2010 that now requires (free) registration and that work is done to be set free from it in the upcoming 2.x branch. So, I am updating this issue's title a bit.
@twooten, #1: Tim, it seems that after these recent changes the need to switch to the GeoIP API is upgraded from simply checking it out to actually doing it. This post of mine also serves as me subscribing in order to know when there'll be some 2.x-dev available for testing. Let us know ;)
Comment #4
roball commentedWould be great when the switch is going to be done soon.
Comment #5
twooten commentedYep, I've had the code working for a couple of weeks on my site, using the GeoIP module. I went ahead and made an update (6.x-1.6) to take into account the changes to IPInfoDB API. If you install that version you'll have a place where you can enter in your API key and continue to use that service.
Version 6.x-2.0 is a complete rewrite. I've really simplified the module and integrated it better with Views. I have removed all the Google map stuff and made it rely upon the GeoIP module and the free MaxMind Geo City data. So now there are no external calls being made. And because the data is exposed to Views, you can use any mapping solution you want, Google maps, OpenLayers, etc. You can see it working with OpenLayers on the demo page at my site, http://www.wootenswebdesign.com/demo/visitorinfo.
So 6.x-2.0 will not provide any default pages, nor will it provide any map blocks. If you've got Views you can easily do that with the data that the module provides, and really, who doesn't have Views? Is that going to be a problem for anyone?
I'll see about getting out a dev version for you guys to try this weekend. Any other suggestions as far as this module goes?
Tim
Comment #6
klonosSome default views that would provide the same (or similar) functionality that good-old 1.x branch used to offer would be nice ;)
Comment #7
klonos...since there is no 2.x branch available (so we can assign this issue to that version), I'm adding it to the title as a reminder for when a 2.x-dev will be available. BTW Tim, any chance you create a 2.x branch sooner and upload whatever code you are already using at your site?
Comment #8
roball commentedGreat news! Will try the 6.x-2.0 dev as soon as it's available. Thanks.
Comment #9
twooten commented@klonos - I'm attaching the code for the 6.x-2.0 branch here. As always, backup your data before doing anything with this. It shouldn't cause any problems but you know, just to be safe.
Also, please read this post in the GeoIP issue queue about the versions I used to make this work and note that I had to rename the GeoLiteCity.dat file to GeoIP.dat.
http://drupal.org/node/964418
Tim
Comment #10
klonos...will test this tomorrow and report back (been working for too many hours and I'm getting clumsy and unproductive). Thanx for sharing ;)
As for backing up and the heads-up on this perhaps being unstable, don't worry, I always back things up and I have more than a couple of test setups available for these kind of tests anyways.
Comment #11
izmeez commentedThanks, this looks like a great direction to go. I'll also do some tests.
Comment #12
klonos..testing right now and will report back in a few. Just a minor type in the demo site's help text (2nd paragraph):
Comment #13
twooten commentedSo what's the results of the testing? Soon as drupal.org moves to using Git I'd like to get 6.x-2 up so just looking for feedback here.
Thanks!
Comment #14
roball commentedIs there a reason for not officially releasing 6.x-2.0 dev?
Comment #15
twooten commentedYes, actually I was waiting on the d.o move to git.
Comment #16
izmeez commentedMy apologies for needing to update this post.
@twooten Thanks for the reminder to test the new version. I tried the version (2.x) that was attached to the comment but found it was not working. Visitorinfo no longer appeared in the user permissions table and I was not able to view visitorinfo-map.
So I downloaded and tested the 2010-Nov-14 version. It works as stated in the readme file. Also had to change the filename in the GeoIP module configuration when using GeoLiteCity.dat file as described in http://drupal.org/node/964418. I only had to wait for a few minutes for the marker and table info to be updated.
Looking forward to v.2.0 without the dependency on the IPInfo.com API key.
My biggest obstacle to using the module is Visitor Info Map visible to anonymous users with pathname since it does not obey the user permissions.
Otherwise this is a great module. Thanks for the work.
Izzy
Comment #17
klonosOk, it seems we're only a few days away from that ...hopefully ;)
Comment #18
klonos...I meant from the d.o move to Git. I know this is meant for the 2.x branch, but I am temporarily switching to the 1.x-dev - the latest dev build available where new features are allowed to go in.
Comment #19
izmeez commented@twooten Thanks for all the work on this module.
Since 6.x-2.0 release this issue thread might be closed and specific issues opened as they arise, so I have started a new issue, http://drupal.org/node/1079262 for the problem described in #16, no user permissions to access visitorinfo.
Comment #20
AvvAdeh commented#5:
It is a good thing that your module evolve with time, but from the time you change the behavior with 2.0, I'm not able to use it anymore and I'm stuck with 1.6 version.
The reason is that the file we must upload to our server is too big for my free provider, and as soon as it is uploaded it automatically deletes it because of its size.
So, I don't know but perhaps you may consider to re-add Google map as an option in 2.0.
#16 and #19:
I put a trick to make visitor-map showing depending on the actual rights defined, on the topic Visitor Info Map visible to anonymous users with pathname. Even if it's only a trick, it still works.