Hi @redepiabanha
Thank you for bringing this to our attention and for sharing the error log details.
We understand how frustrating it can be to see your logs fill up with repeated warnings. The specific warning you’ve reported occurs when the code tries to access a property that doesn’t exist for certain objects. The good news is that this type of warning is harmless in terms of site functionality, your website and Aggregator should continue to operate normally. However, we agree it’s important to keep error logs clean and avoid unnecessary entries.
We will be releasing Aggregator 5.0 soon, and this update will resolve the issue permanently.
As a temporary and quick workaround, you can modify the file mentioned in the warning. You can replace the following code:
if (!is_object($post) || $post->post_type !== $this->cpt) {
return;
}
with
if (!is_object($post) || !property_exists($post, 'post_type') || $post->post_type !== $this->cpt) {
return;
}
This change ensures the warning no longer appears in your logs.
If you need any help applying this change or have any other questions, please let us know, we’re always happy to help further.
Thank you for your patience and for helping us improve Aggregator!
Thank you very much for the quick support. I’m testing it and report back here.
You’re very welcome @redepiabanha ! 🙂
Please go ahead and test it whenever you’re ready, and just let us know how it goes. If you run into anything else or have further questions along the way, we’re here and happy to assist.
Looking forward to hearing back from you!