Hi @mohobook
I hope you are doing well today.
I cannot replicate this on my lab site.
This issue could be a plugin conflict. Would you please run a conflict test? Please deactivate all plugins except Defender and check if the problem is gone. If so, then enable all plugins one by one and find which one is having a conflict. If there is no positive result, switch to the default WordPress theme like 2019, and see if it works.
Before this test, we recommend full site backup or running this test on the staging site.
Please let us know about the results.
Also can you check do you see any kind of errors in the browser console?
Kind Regards,
Kris
Hello, I found the conflicting plugin, what’s your recommendation at this point? It’s a very useful plugin and I need to keep it in my stack
Hi @mohobook
Please let us know this plugin name and is it a free one so that we could replicate this issue on our side and see does any fix can be done after we narrow down main issue.
Kind Regards,
Kris
Hello,
Checking in to see if you have had a chance to look into this
Hi @mohobook
Sorry for the delay here, it seems we didn’t receive the notification from your latest response.
I tried to replicate the issue using the shared plugin but it worked well, can you please navigate to the Admin and Site Enhancements dashboard and disable one module by one until the issue is gone? In case any module is causing the issue on your website we can then check specific modules and try to replicate the problem on a lab site.
Best Regards
Patrick Freitas
Hello,
The setting that is causing the problem is here
Disable Components > Disable Smaller Components > Disable loading of dashicons CSS and JS files on the front-end for public site visitors.
Looking forward to a resolution
Hi @mohobook
Thank you for response!
I checked and was able to replicate this fully.
Technically speaking, this should ideally be fixed byt the other plugin developers as a compatibility bug – as it’s that other plugin that breaks Defender and not the other way around.
However, I have also already reported it to our Defender Team to look into it to see if we can make changes on our end that would make them both work together.
I’ve reported it as a bug and it needs to be closely tested and code needs to be reviewed first, then change must be implemented in core code and, finally, before release it needs to be tested by our QA Team.
That’s a process and we aim to do it as fast as possible but I’m not able to give ETA yet.
Thank you for reporting this!
Kind regards,
Adam
Thank you for looking into this
Very happy with your plugin, will be leaving a review
Hi @mohobook,
You are welcome. We would be glad to hear your review. Since the issue has been forwarded as a bug, we are marking this topic as resolved for now. Please let us know in case you need further help.
Please also subscribe to our roadmap on https://wpmudev.com/roadmap/ to receive the details on each update and also check the changelog in https://wordpress.org/plugins/defender-security/#developers
Kind regards,
Zafer
