Plugin Contributor
Leland
(@addthisleland)
Hi there!
Thanks for contacting AddThis Support 🙂
As of now, I wasn’t able to replicate this debug notice on my end with the same plugin and WP version as you which leads me to believe that there may be some sort of conflict between our plugin and your theme or one of your other plugins.
Can you send me a screenshot of that error and you can you to see if you can deactivate your plugins one at a time to see if there’s any possible conflicts?
Thanks for your help!
Cheers,
Leland
Thanks for reply
Unfortunately I can not determine which event causes the warning and therefore I can not understand if it does not occur by progressively deactivating the installed plugins.
Plugin Contributor
Leland
(@addthisleland)
You’re welcome! Always a pleasure to help 🙂
With that said, are you still able to produce this warning?
If you are, the best way to test if its a plugin conflict is to deactivate your active plugins all at once so we can see if its a plugin conflict. If the warning goes away, then that means it has something to do with your other plugins and we can then deactivate them each one at a time to find the root cause.
Also are you noticing any AddThis features not working?
An alternative to using AddThis is to install AddThis directly into your site’s theme template, let me know if you’re interested in testing that route!
Thanks,
Leland
Anonymous User 16148154
(@anonymized-16148154)
Hello,
Sorry to warm this up, but I found out when this happens and how to fix it.
It seems when a post is updated using the WordPress API the function metaBoxDisablesTools receives an invalid value for $post, causing the error.
I did not yet have time for in-depth testing, but it seems it is safe to return true if $post == null, as metaboxes are simply skipped on the wp api anyway.
It would be neat to see a null check in there by default for future versions so we don’t need to do this manually on each update.
Best,
Tao
Yes, me too, How to fix it, i have use ithemes security
