Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.5.0-b1
-
Component/s: None
-
Labels:None
Description
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. They are less accurate, however, since they do not contain latitude or longitude values. Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!)
https://dev.maxmind.com/geoip/geoip2/web-services/
- The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary.
- Ensure all locations are updated accordingly and existing functionality work
- Consider updates to the Order (
CORE-2335) and SystemOverview plugins as well
Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/
Issue Links
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Assignee | Tyson Phillips [ tyson ] |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. They are less accurate, however, since they do not contain latitude or longitude values. The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. They are less accurate, however, since they do not contain latitude or longitude values. The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. They are less accurate, however, since they do not contain latitude or longitude values. The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 1 [ 66 ] |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 1 [ 66 ] | 4.5.0 Sprint 2 [ 67 ] |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked lower |
Tyson Phillips (Inactive)
made changes -
Link | This issue is blocked by CORE-2123 [ CORE-2123 ] |
Tyson Phillips (Inactive)
made changes -
Link | This issue is blocked by CORE-2884 [ CORE-2884 ] |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. # Consider updates to the Order plugin as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. # Consider updates to the Order plugin as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order plugin as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order plugin as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order and SystemOverview plugins as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order and SystemOverview plugins as well Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order ( Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Description |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order ( Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Maxmind GeoIP legacy databases are being discontinued January 2, 2019. https://support.maxmind.com/geolite-legacy-discontinuation-notice/
There are GeoLite2 databases available, and we need to consider transitioning over to use them instead. -They are less accurate, however, since they do not contain latitude or longitude values.- Latitude and longitude will continue to exist as mentioned April 11, 2018 (yay!) https://dev.maxmind.com/geoip/geoip2/web-services/ # The NetGeoIP component in Blesta will need to be updated/deprecated/replaced as necessary. #* Ensure all locations are updated accordingly and existing functionality work # Consider updates to the Order ( Also brought up on the forums @ https://www.blesta.com/forums/index.php?/topic/10971-does-the-maxmind-geolite-legacy-database-discontinuance-affect-blesta/ |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 2 [ 67 ] | 4.5.0 Sprint 2, 4.5.0 Sprint 3 [ 67, 74 ] |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 2, 4.5.0 Sprint 3 [ 67, 74 ] | 4.5.0 Sprint 2, 4.5.0 Sprint 3, 4.5.0 Sprint 4 [ 67, 74, 75 ] |
Paul Phillips
made changes -
Fix Version/s | Short Term [ 10800 ] |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 2, 4.5.0 Sprint 3, 4.5.0 Sprint 4 [ 67, 74, 75 ] | 4.5.0 Sprint 2, 4.5.0 Sprint 3, 4.5.0 Sprint 4, 4.5.0 Sprint 5 [ 67, 74, 75, 77 ] |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.5.0 Sprint 2, 4.5.0 Sprint 3, 4.5.0 Sprint 4, 4.5.0 Sprint 5 [ 67, 74, 75, 77 ] | 4.5.0 Sprint 2, 4.5.0 Sprint 3, 4.5.0 Sprint 4, 4.5.0 Sprint 5, 4.5.0 Sprint 6 [ 67, 74, 75, 77, 78 ] |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Jonathan Reissmueller
made changes -
Assignee | Jonathan Reissmueller [ jonathan ] |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
Status | Open [ 1 ] | In Progress [ 3 ] |
Jonathan Reissmueller
made changes -
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 2 hours, 5 minutes [ 7500 ] | |
Worklog Id | 11870 [ 11870 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #600 in Stash -
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Jonathan Reissmueller
made changes -
Time Spent | 2 hours, 5 minutes [ 7500 ] | 2 hours, 39 minutes [ 9540 ] |
Worklog Id | 11871 [ 11871 ] |
Jonathan Reissmueller
made changes -
Time Spent | 2 hours, 39 minutes [ 9540 ] | 4 hours, 33 minutes [ 16380 ] |
Worklog Id | 11880 [ 11880 ] |
Jonathan Reissmueller
made changes -
Time Spent | 4 hours, 33 minutes [ 16380 ] | 5 hours, 42 minutes [ 20520 ] |
Worklog Id | 11883 [ 11883 ] |
Jonathan Reissmueller
made changes -
Time Spent | 5 hours, 42 minutes [ 20520 ] | 6 hours, 7 minutes [ 22020 ] |
Worklog Id | 11884 [ 11884 ] |
Tyson Phillips (Inactive)
made changes -
Fix Version/s | 4.5.0-b1 [ 11108 ] | |
Fix Version/s | Short Term [ 10800 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #601 in Stash -
Status | In Review [ 5 ] | Closed [ 6 ] |