Hi BABOO,
Thank you so much for reporting this and including the log message that detail made it easy to pinpoint.
You’re right, the warning was coming from our plugin. The notice (Attempt to read property "post_content" on null) happened because one of our functions tried to read the current page’s content in situations where WordPress doesn’t have a “current post” available such as archive pages, search results, 404 pages, and a few editor/REST contexts. It was a harmless warning (nothing on your site was broken), but it shouldn’t have been logged, and we’ve now fixed it.
The fix adds a safety check so the function simply skips those contexts where no post is present. It’s included in version 2.0.2, which is now available.
Could you please update to 2.0.2 (Dashboard → Plugins → Update), then reload the pages where you saw the warning? It should no longer appear in your log. The existing entries you saw were recorded before the update and won’t be added to again.
If you happen to still see anything after updating, just let us know and we’ll look into it right away.
Thanks again for helping us improve the plugin!
Best regards, Md. Merajul Islam Sojib, Team bPlugins
