You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a re-post of a bug incorrectly reported in the General Questions forum.
In Piwik 1.9.1, the Visitor Location (City) widget does not behave properly under the following circumstance:
My site has GeoIP (Php) installed and enabled. When the incoming IP address is not in the GeoLite City database from MaxMind, and when that incoming connection is the only one, the Visitor Location (City) widget tells me that the GeoIP feature is not properly installed. The location of this incoming IP address is properly shown as "Unknown".
As soon as my site sees a connection from an IP address that is in the MaxMind database, the above error goes away. The location of that first IP address is, of course, still shown as "Unknown".
I suggest that the error message text be amended to include the possibility that the database is out of date (it wasn't, in my case) or to simply not produce an error message at all when the MaxMind database is present.
The text was updated successfully, but these errors were encountered:
I propose that when there is region data, but the geoip is detected as "Working" then we display the standard message "There is no data for this report", Does it sound good capedfuzz?
This is a re-post of a bug incorrectly reported in the General Questions forum.
In Piwik 1.9.1, the Visitor Location (City) widget does not behave properly under the following circumstance:
My site has GeoIP (Php) installed and enabled. When the incoming IP address is not in the GeoLite City database from MaxMind, and when that incoming connection is the only one, the Visitor Location (City) widget tells me that the GeoIP feature is not properly installed. The location of this incoming IP address is properly shown as "Unknown".
As soon as my site sees a connection from an IP address that is in the MaxMind database, the above error goes away. The location of that first IP address is, of course, still shown as "Unknown".
I suggest that the error message text be amended to include the possibility that the database is out of date (it wasn't, in my case) or to simply not produce an error message at all when the MaxMind database is present.
The text was updated successfully, but these errors were encountered: