Hi @testrelay1584
I hope you’re well today and thank you for contacting us.
I have asked our Defender developers’ team for consultation on this but meanwhile, let us know please:
1. what PHP version are you using currently?
2. is everything else (WP core, other plugins, theme) up to date on site?
3. are you using any other security plugins on site at the same time, especially if they provide some sort of Two-Factor auth?
Best regards,
Adam
Hi @testrelay1584
I just got some updated questions suggested by our Defender Team:
4. are you using any plugin (either native or 3rd-party) that adds Matomo analytics to site and if yes – is error happening if you disable it or is it gone? If it’s gone, what plugin it is exactly (including version number)?
5. if above is not the case, could you see if the same error is happening if you switch off (temporarily) all the plugins except Defender and switch site to Twenty Twenty Two theme only?
Kind regards,
Adam
Hi Adam,
Thank you for the quick reaction. Hereby the answers:
1. php 7.4
2. Yes
3. No, the only plugins installed are: classic editor, ManageWP – worker, OptimizePress dashboard and OptimizePress builder.
4. No (unless one of the above plugins use it, I see OptimizePress has some stats, not sure how they are powered)
5. Yes, it works fine after disabling the other plugins and it keeps working fine when I enable all but the OptimizePress. After enabling the OptimizePress dashboard plugin the defender crashes. Will you please get in touch with the OptimizePress team (https://www.optimizepress.com) to work out the solution?
Hi @testrelay1584
Thank you for response!
Unfortunately, I have no way to test it with OptimizePress myself (as it’s a 3rd-party premium plugin) but your test means that there is compatibility issues.
It’d be caused by the php-di library version and the way it’s loaded. I have already reported it to our Defender Team and they’ll look into it in order to get it fixed.
However, please also report it as a bug to OptimizePress support as you are their customer and it’s actually that plugin breaking Defender rather than the other way around.
Kind regards,
Adam
Thank you Adam. I’ve just reported this issue, together with this thread, to the OP team. I will appreciate if you could work together to solve the compatibility problem.
Hi @testrelay1584,
I will appreciate if you could work together to solve the compatibility problem.
Yes, our team is currently checking on how to move forward with troubleshooting this further and ways to get access to OptimizePress.
In the meanwhile, if you happen to get further feedback from the OP team regarding what might be causing it, then please so let us know too.
Have a great day ahead.
Kind Regards,
Nithin
.
Hello Nithin,
The OptimizePress team has looked into this issue and it’s clear the problem lies within your plugin, as it gives the error after updating from version 3.0.1. to a newer one. I hope you will be able to provide a fix soon. Thank you in advance.
As for the access to OP, maybe you can get in touch with the OptimizePress team and ask for a short-term license to troubleshoot the problem with the Defender? They also provide a refund within 30 days of purchase, so that could be another possibility.
Hi @testrelay1584
Our developers are looking into it, as already mentioned.
The problem is due to certain PHP library that OptimizePress is also using. It’s not a bug in Defender. It is a compatibility issue, indeed. As mentioned, our developers are already aware of it and are in fact also already looking into solution that would completely isolate PHP dependencies on our end (in our plugin) and that would solve similar issues for good. However, I don’t have an ETA on this at the moment.
OptimizePress actually should consider similar action on their code (isolating PHP dependencies) as sooner or later it may lead to other similar conflicts with other plugins (not necessarily ours) but that’s up to them of course.
To sum it up on our end:
– it is not a bug in Defender but it indeed is a compatibility issue (caused by the other plugin)
– we are working on a general solution for this and similar issues so it will be addressed on our end anyway
– unfortunately, I’m not able to give you an ETA on this; I can only confirm that our developers are working on this and will address it.
Kind regards,
Adam
Hello @testrelay1584 ,
We haven’t heard from you for some time now, so it looks like you don’t have any more questions for us.
Feel free to re-open this ticket if needed.
Kind regards
Kasia
Hi Kasia,
Please keep the ticket open, it’s far from resolved:
“As mentioned, our developers are already aware of it and are in fact also already looking into solution that would completely isolate PHP dependencies on our end (in our plugin) and that would solve similar issues for good. However, I don’t have an ETA on this at the moment.”
[ Please do not bump. ]
Hi @testrelay1584
I hope you are doing well
I can see the fix is coming in Defender 3.4 if all development and tests work as expected, this is our upcoming version https://wpmudev.com/roadmap/#defender we are safe to close this ticket as the bug was isolated and reported.
Best Regards
Patrick Freitas
Hi Patrick,
Is it known (at least approximately) when Defender 3.4 will be released?
Hi @testrelay1584
It is the Beginning of October but we don’t have the correct day since it depends on development and tests done by our QA team, usually, it is in the first 15 days.
Best Regards
Patrick Freitas
Ok, great. Thanks for the information.
Any updates on the release of the fix?
