Closed (fixed)
Project:
Visitor Info
Version:
6.x-1.3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2010 at 21:27 UTC
Updated:
2 Apr 2010 at 13:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
twooten commentedHi BWV,
It sounds like you have already checked the most obvious causes, permissions and cache. I did look at your page source and noticed that the Javascript visitors array is empty.
But you say that logged in users can see the locations? So there is definitely data in the db. Still sounds like a caching issue of some sort.
Tim
Comment #2
bwv commentedFYI, here is the source from the same page when I am logged in.
Comment #3
bwv commentedUpon further investigation, it turns out that only admin can see the markers. I gave permission to anonymous and authenticated users, logged in as an an authenticated user, and was unable to see the markers.
Here is the page source:
Is this phenomenon something that anyone is familiar with? I will gladly compensate the person who can help me figure this out.
PS: I have rebuilt all the post permissions under "post settings," but that did not produce the desired effect.
Thanks again, david
Comment #4
bwv commentedImage of page with markers visible is attached.
I'll pay someone $25 if they can help me figure this out, more if reasonable.
Comment #5
twooten commentedBWV,
I think dan.reimer has the right solution in this comment http://drupal.org/node/674686#comment-2491882. At line 44 of the visitorinfo.module file
Change:
'access arguments' => array('access content'),
to:
'access arguments' => array('access visitorinfo'),
I need to make a patch to fix this and will do so this weekend unless someone beats me to it, which would be just great.
Hope this helps.
Tim
Comment #6
bwv commentedTim, thank you. I made the change per dan.reimer's suggestion, but the result is the same: only admin can see the markers. I unfortunately do not know where to begin to try to fix this. I regard this feature as important enough that I am willing to pay an expert to sort it out for me.
Comment #7
bwv commentedIssue fixed here:
http://drupal.org/node/691758
Comment #8
twooten commentedFixed in 6.x-1.4