geoip-detect icon indicating copy to clipboard operation
geoip-detect copied to clipboard

Troubleshooting Mode

Open benjaminpick opened this issue 3 years ago • 0 comments

Is your feature request related to a problem / specific use-case? Please describe.

Common support requests are caused by:

  • Reverse proxy configured incorrectly
  • Page Caching is active
  • Unexpected ("wrong") lookup results See https://github.com/yellowtree/geoip-detect/wiki/Troubleshooting

How can we reduce the amount of such requests by making it easier to troubleshoot?

Describe the solution you'd like There should be a "Troubleshooting" mode similar to "verbose logging" that guides along the troubles above and explains how the plugin is functioning. Output can be both in console.log and, if GEOIP_DETECT_DEBUG is enabled, as trigger_notice (i.e. either in frontend or log file, depending on WP_DEBUG_DISPLAY and WP_DEBUG_LOG).

Client IP is incorrect

The detected client IP is ....
(If this is incorrect, please follow these steps: https://github.com/yellowtree/geoip-detect/wiki/Troubleshooting#q1-he-says-my-ip-is-x-but-i-know-it-is-y)

Warning: Site-caching seems to be enabled - please enable the option "Disable caching a page that contains a shortcode or API call to geo-dependent functions." See https://github.com/yellowtree/geoip-detect/wiki/Troubleshooting#q2-sometimes-the-ip-detection-shows-the-correct-results-but-sometimes-not

`` This is the data connected to your IP (...):

  • Country
  • City
  • Raw Data If this is incorrect, please check https://github.com/yellowtree/geoip-detect/wiki/Troubleshooting#q3-how-can-i-check-if-the-plugin-gets-it-wrong-or-the-database-provider-has-the-correct-information ``

benjaminpick avatar Feb 22 '22 15:02 benjaminpick