1) I am not talking about deactivating WPDM. I am saying that WPDM reports this error when ANY OTHER plugin is deactivated/activated.
2) Your line of code, I reported above, COULD have a null pointer test added before accessing, even if your testing does not experience the issue.
I am a plugin developer myself (see WPMathPub), and when my users report an error, I try to reproduce it. BUT I also continue to clean up my plugin code to avoid unnecessary NULL references when the client can provide the exact line number, as I have done.
It’s only a warning, but as a tech support engineer for many years, I learned to stop assuming the client’s usage is at fault and try my best to use the information the client spent valuable time on your behalf, pointing out a potential weakness.
Thanks for taking the time to respond. It’s only a warning. Use my “expert” feedback or not. I love your team’s product and quick responses.