MM Aurangajeb
Forum Replies Created
-
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.
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 @cokamonga ,
We haven’t heard back from you in a couple of days. I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.
Thanks!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 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_DEBUGandWP_DEBUG_LOGenabled inwp-config.php, you can disable warning logging on production by adding this line right after the existingWP_DEBUGdefinition: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 @ibiza69
I found your ticket #88540 and also noticed that your issue has been resolved there. Please feel free to reply there if you need further assistance. We’d be happy to help.
Thanks!
Hi @kortney2 ,
Thanks for reaching out!
AIOSEO definitely handles Facebook (Open Graph) images, and there are a couple of ways to set this up depending on what you prefer.
Out of the box, the plugin’s default image source is set to “Default Image,” which means it looks for a global fallback image you can upload in the settings. It doesn’t automatically pull the featured image unless you tell it to.
To have it automatically use your featured image for Facebook sharing:
- Go to All in One SEO > Social Networks > Facebook.
- Find the Default Post Image Source dropdown.
- Change it from Default Image (Set Below) to Featured Image. Screenshot reference: https://a.supportally.com/i/KnxkHF.
- Click Save Changes.
That’s it! From that point on, any post or page with a featured image will automatically use it as the Facebook sharing thumbnail, without you having to set anything per post.
A couple of tips:
- If a particular post doesn’t have a featured image set, AIOSEO will fall back to whatever you’ve uploaded as the Default Post Facebook Image (the image field right below that dropdown). So it’s a good idea to upload a general site image there as a safety net. Screenshot reference: https://a.supportally.com/i/YTTGM8.
- You can also override the Facebook image on any individual post by scrolling down to the AIOSEO Settings > Social tab when editing that post.
- There’s also a First Available Image option in that same dropdown. It cycles through the featured image, the first attached image, and the first image in the content until it finds one. Handy if not all your posts have a featured image set. Here’s a screenshot for reference: https://a.supportally.com/i/PpzS3J
Here’s our doc that walks through this with screenshots:
https://aioseo.com/docs/setting-a-default-image-for-facebook/
I hope this helps.
Thanks!
Hi @cokamonga,
Thanks for reaching out with such a detailed description of the issue.
Could you please provide a screenshot (https://snipboard.io/) or screencast (https://www.loom.com/screen-recorder) of the issue, including the URL of the product category, so that I can look into it and better assist you?
I want to clarify a couple of things about how AIOSEO handles taxonomy terms (like WooCommerce product categories) on the free version, because that should explain both symptoms you’re seeing.
About the “frozen” AIOSEO panel on product categories:
In the free version of AIOSEO, the settings panel that appears on taxonomy term edit screens (categories, product categories, tags, etc.) is a preview/upsell panel. It’s intentionally non-interactive and shows a blurred overlay with an “Unlock Custom Taxonomies” prompt. This isn’t a freeze or bug. Custom per-term SEO settings (title, meta description, social meta, etc.) are a Pro feature.
About meta descriptions on product category archives:
On the free version, AIOSEO generates meta descriptions for taxonomy archives using the default format configured in All in One SEO > Search Appearance > Taxonomies > Product Categories. By default, this format uses the
#taxonomy_descriptionsmart tag (https://a.supportally.com/i/STzqpo), which pulls directly from the WordPress native category description field (the “Description” field you see when editing a product category in WooCommerce > Categories).So if you’ve written descriptions in that native WordPress description field, those descriptions are being used in the frontend meta description output. What the free version doesn’t support is writing a separate, custom meta description specifically for SEO that overrides the default format on a per-term basis. That’s the Pro feature the upsell panel is referring to.
What you can do right now (free version):
- Go to All in One SEO > Search Appearance > Taxonomies > Product Categories.
- In the Meta Description field, you’ll see the default format (likely
#taxonomy_description). This controls what gets output on all product category archive pages. - Make sure the WordPress native description field on each product category contains the text you want used as the meta description.
If you need individual, per-category custom meta descriptions that are separate from the WordPress category description field, that would require upgrading to AIOSEO Pro.
Quick check you can do:
View the page source of one of your product category archive pages and search for
<meta name="description". This will show you exactly what AIOSEO is currently outputting. Compare it against the content in the WordPress native description field for that category.Let me know if you have any questions or if something doesn’t match what I’ve described. Happy to dig deeper.
However, if this is a Pro-related topic, you will need to contact us using our contact form at https://aioseo.com/contact/.
The guidelines for these forums state that you shouldn’t post about commercial products in these forums – https://ww.wp.xz.cn/support/guidelines/#do-not-post-about-commercial-products
Our customer support team will be happy to help you via the contact form on our site.Thanks!
Hi @ibiza69 , could you please provide the ticket number for our native support, so that I can check and follow up on it?
Hi @ibiza69 ,
We haven’t heard back from you in a couple of days. I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.
Thanks!We haven’t heard back from you in a couple of days. I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.
Thanks!Hello @aislinndooley,
Thank you for your awesome review! It’s fantastic to hear that you noticed a positive impact on your rankings after switching to our plugin. We’re glad you appreciate how Meta, sitemap, and schema tasks are managed and that you find the dashboard clean and efficient. It’s great to know that the free version exceeded your expectations.
Keep enjoying the features. Cheers!
Hello @matoufrancemyk,
Thank you for your fantastic review! We’re thrilled to hear that you find our All in One SEO plugin easy to use and user-friendly, even for non-professionals. It’s wonderful to know that the tool meets your needs. We are committed to making SEO accessible for everyone, and your feedback inspires us to keep improving.
Happy optimizing!
Hi @camilla859,
Thanks for reaching out!
You can change the breadcrumb separator directly from the AIOSEO UI.
Change the default site-wide
This sets the separator for all breadcrumbs (block, shortcode, widget, theme integration).
- Go to All in One SEO > General Settings > Breadcrumbs.
- In the Separator field, type whatever symbol you’d like (for example, an arrow like
→,›,»,▸). - Click Save Changes.
Here’s a screencast for reference: https://a.supportally.com/v/vabDOi
Here’s our related doc on Breadcrumbs settings here: https://aioseo.com/docs/displaying-breadcrumbs-on-your-site/
I hope this helps.
Thanks!