Hi @daigo75
I hope you’re well today!
The database itself, as far as I’m aware, is already updated but yes – we already have the issue of the Reader reported so our developers are looking into it and I believe it should be taken care of soon.
Best regards,
Adam
Thread Starter
Diego
(@daigo75)
Hi Adam,
I’m not sure what you mean with “the database”, as we haven’t come across issues related to it. If the Reader library is going to be updated, that should be sufficient to fix the errors that some of our users encountered. 👍
Hi @daigo75
Yes, it will be updated. I just got confirmation that it should be taken care of soon so please keep the plugin up to date 🙂
Best regards,
Adam
I can confirm that this is still an issue on a specific website for me.
The conflict for me is Defender Pro and GeoTargeting Lite, causing the same error message regarding MaxMind.
I am forced to use another security plugin for the time being but hope this can be fixed soon.
Hi @webmastersatdycedesigns,
Sorry to hear about your trouble. Would GeoTargeting Lite have similar features as MaxMind which can cause conflicts?
The issue on this original thread was related to a database not being updated with MaxMind, but not a conflict with another plugin. Could you please open a new thread with further details on your setup so that we can properly assist you.
Best,
Jonatahn S
Thread Starter
Diego
(@daigo75)
@wpmudev-support9 If I may re-join the conversation, the issue posted originally was due to a conflict with another plugin, namely our EU VAT Assistant. The root cause was not an outdated MaxMind database, but an outdated MaxMind Reader class.
To reiterate, our EU VAT Assistant, as well as WooCommerce, use version 1.6.0 of the MaxMind library, and the MaxMind Reader class 1.4.x, which was the one within WPMU DEV Defended, is not compatible with it.
This is also likely to solve the issue with the GeoTargeting Lite. That plugin now uses version 2.10 of MaxMind GeoIp2 library (https://plugins.svn.ww.wp.xz.cn/geotargeting/trunk/vendor/geoip2/geoip2/CHANGELOG.md), which required MaxMind Reader 1.5.0 or newer (see https://packagist.org/packages/geoip2/geoip2#v2.10.0). If WPMU DEV Defender still contains an older version of the MaxMind Reader (which seems to be the case: https://plugins.svn.ww.wp.xz.cn/defender-security/trunk/src/extra/maxmind-db/reader/CHANGELOG.md), that can trigger an error.
In summary
The solution to the issue posted originally is to update the MaxMind Reader component included with the WPMU DEV Defender to version 1.6.0. A newer one might also work, it would just have to be tested.
Defender pro was actually updated 2 days ago and included an updated version of MaxMind. It seems to be working fine on the one affected site I had.
So there is now a solution to this – update Defender Pro to v2.4.7.
See changelog: https://bit.ly/383WAGc
-
This reply was modified 5 years, 3 months ago by
John.
Thread Starter
Diego
(@daigo75)
@jhob The link I posted is the change log of the MaxMind Reader included with the trunk of the WPMU DEV Defender here on the public repository (source folder: https://plugins.svn.ww.wp.xz.cn/defender-security/trunk/src/extra/maxmind-db/reader/). The source code in that folder still includes the old version of the reader library.
Perhaps the user who posted the last message (@webmastersatdycedesigns) is using the free version, which is still 2.4.6. That would explain why the issue is still there, in their case.
@daigo75 yes that could well be it. My guess is Defender will be updated soon in the WP plugin repo, I think there’s normally a bit of a delay which you’ll know about better than I do!
Greetings everyone.
I am in fact using the Pro version of Defender.
With the knowledge that it should be updated now, I will copy the site and confirm that the error is no longer an issue and report back here.
Hi @webmastersatdycedesigns
If you are using the Pro version and can confirm the issue.
Kindly create a ticket on our Support forum and we can take a closer look at this, feel free to update this thread too to confirm if the issue is gone, usually the timeframe between free and the pro version is from one – two weeks.
Best Regards
Patrick Freitas
