Multiple PHP warnings

Hi Ron,

Thanks for the detailed report and for sharing the error log. I can see exactly what’s happening here.

The PHP warnings you’re seeing are caused by an issue in how AIOSEO generates Schema breadcrumb markup on certain archive pages. Specifically, when The Event Calendar registers its custom post types and taxonomies, there are situations where AIOSEO’s breadcrumb code receives a post type object when it’s expecting a taxonomy term object. This causes it to try accessing properties (like taxonomy, slug, parent) that don’t exist on that object type, which generates the warnings.

That’s why the warnings are tied to your sites running The Event Calendar, and why the volume is so high — every page load that triggers AIOSEO’s Schema output for those archive pages generates a cluster of warnings.

To be clear: these are PHP warnings, not fatal errors, so your site’s functionality isn’t broken. However, I completely understand the concern about 2,000+ log entries in 14 hours — that kind of log bloat makes it harder to spot real issues.

Immediate steps you can take to stop the log spam:

If your site has WP_DEBUG and WP_DEBUG_LOG enabled in wp-config.php, you can disable warning logging on production by adding this line right after the existing WP_DEBUG definition:

define( 'WP_DEBUG', false );

Or, if you want to keep error logging active but only for actual errors (not warnings), you can add this snippet via the free WPCode plugin:

add_action( 'init', function() {
	error_reporting( E_ALL & ~E_WARNING & ~E_NOTICE & ~E_DEPRECATED );
}, 1 );

This will stop the warnings from filling your logs while keeping genuine errors visible.

On our end: I’m filing this as an internal issue with our Development team. I hope this will be addressed in an upcoming release.

I appreciate you sticking with AIOSEO and taking the time to report this.

Thank you again for bringing this to our attention.

Hi @donniepeters ,

Thank you for following up. I completely understand your frustration, especially with aggressive bots putting extra strain on your websites and filling up your logs.

Even when WordPress debugging is turned off, your web hosting server has its own separate settings that log these messages. You can ask your hosting provider to adjust your server settings so it only records critical errors instead of minor warnings. Setting up a free firewall like Cloudflare can also help block those bad bots and stop them from triggering these warnings in the first place.

Our developers are actively working on a fix for the conflict with The Events Calendar. However, since your other sites do not use that plugin, we may need to investigate them separately to see exactly what is causing those specific errors.

Please feel free to reach out to us directly so we can investigate further. You can contact us using the Basic Question form on this page: https://aioseo.com/contact/

Thank you, and have a wonderful weekend.

Hi @donniepeters ,

Thanks for the additional context and for linking to your older thread about the event date.

On the event date smart tag: I’ve read through your previous thread (https://ww.wp.xz.cn/support/topic/event-date-variable-displays-incorrectly/) and I can see this has been a pain point for a long time. That tag is actually the WordPress post publish date, dynamically renamed based on the post type. For events, that’s almost never the date you want in your SEO title or Schema output.

I can see Arnaud acknowledged this two years ago. I’m filing a separate enhancement request to add smart tags that pull the actual event start and end dates from The Events Calendar’s data, saving you from manually editing over a thousand events.

On your other sites (without The Events Calendar): The fix we’re working on for the PHP warnings isn’t limited to The Events Calendar. The root issue is a missing type check in AIOSEO’s code that can be triggered by any plugin that registers custom post types with taxonomy archives. So the upcoming fix will cover all of those cases, not just TEC.

If you’d like us to investigate the specific errors on your non-TEC sites, feel free to reach out directly through our contact form (https://aioseo.com/contact/) and share the error log from one of those sites. That way we can confirm whether it’s the same underlying issue or something different.

Thank you for your patience and for continuing to use and advocate for AIOSEO across your 13+ sites. We want to make sure the plugin works well for your event-heavy workflow.

Hi @donniepeters ,

Thanks for the update. 912 events on one site and 368 on the other is a serious workload, and I can only imagine the effort of manually adjusting dates on all of those.

6,384 warnings in under two days is definitely not acceptable, and I understand your urgency. Both the breadcrumb warnings fix and the Event Calendar date integration are actively being worked on. I can’t give an exact release date yet, but they’re in the pipeline and moving forward.

In the meantime, if you’d like to stop the log from growing while waiting for the update, the quickest option is to add this one line to your site’s wp-config.php (right before the line that says /* That's all, stop editing! */):

define( 'WP_DISABLE_FATAL_ERROR_HANDLER', false );
ini_set( 'log_errors', '0' );

Or if you’d rather keep logging but filter out these specific warnings, the WPCode snippet from my earlier reply will do that without hiding real errors.

Glad the other sites are running clean now. We’ll make sure to update this thread once the fixes are released. Thank you for your patience, Ron.