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