arnaudbroes

Hey @ohstereza,

You can disable that meta record by adding this filter snippet to your theme functions.php file or through a plugin like WP Code.

add_filter( 'aioseo_author_meta', '__return_false' );

I’m afraid that the meta tag with the itemprop="author" attribute that you’re seeing at the bottom of your screenshot is not coming from our plugin, so we can’t help you with that one. I recommend temporarily disabling plugins one-by-one and switching to a different theme to figure out which plugin/theme is outputting it.

Hey everyone,

First of all, thank you all for pitching in. Please know that we take all of your feedback seriously and highly appreciate you sharing your opinion with us.

After internal discussion, we have decided to disable SEO Email Reports in our next update for all users, and it will be disabled by default for new users going forward. This should fully eliminate the friction that this feature has been causing.

We will also issue a notification inside the plugin’s Notification Center so that users are made aware they need to reenable the setting manually if they’d like to continue receiving e-mail reports.

This change will take effect in our next update, AIOSEO 4.7.7, which is scheduled for release next week.

If you have any questions or additional feedback for us, please let us know!

Hey @superthin,

This issue has been addressed in the latest update. If you have any questions, please let us know.

Hey @superthin,

Please disregard my previous reply – it looks like this is a different security vulnerability. We’ll look into this and address it ASAP.

Thanks for letting us know, we’ll keep you updated.

Hey @superthin,

Our team at AIOSEO have adopted the Table of Contents Plus plugin and we have already submitted a patch for the security vulnerability. If you update to the latest version, then this issue will be resolved for you.

If you have any other questions, please let us know!

We’re aiming for our 4.7.7 release with this one (December 12) since the next one is already undergoing QA at the moment.

Hey @johnh10,

I just tested this and it’s still working fine. It’s possible your theme might be conflicting with AIOSEO. Fortunately we added a filter hook to disable this feature.

Can you try adding this code snippet to your theme’s functions.php file to see if that helps?

add_filter( 'aioseo_remove_reply_to_com', '__return_false' );

Hey @dmarin, I responded here with a beta build that you can try out if you like.

Hey @levismodding,

We just released a small update that should address this issue. Can you try pulling in the latest update to see if that resolves this error?

Thanks!

Hey @josklever,

We just released a hotfix release for this issue. I’ll mark this thread as resolved now, but if you have any other questions, please let me know.

Hey @josklever,

We may issue a hotfix release for this, but that’s a decision I typically take in discussion with my colleagues and not something we do over the weekend, so TBD basically.

I completely agree with you, but there’s a thin balance because people tend to get upset if we issue too many updates in a short period of time as we already put out a new release every two weeks.

This specific issue may cause terms to be excluded from the sitemap, but obviously only if your table prefix is different from the default (not the case for the large majority of our users).

In any case, I already uploaded the fix to SVN so anyone who’d update the plugin (or reinstall it) would get the fix.

Hey Jos,

Thank you for reporting this. You’re completely right – that shouldn’t have slipped past us, but it happens to the best of us I guess. ?? I’ve gone ahead and fixed this for our next release, which will be released in two weeks from now.

If you’d like a beta fix in the meanwhile, please let me know!

Hey @carloscruz02,

Thank you for reporting this issue.

This is a harmless warning that we have already fixed in our next release which is due in two weeks from now. If you’d like, feel free to reach out to us via our Basic Question form here if you’d like to get a beta build in the meantime.

@knomaze @darklightlaser this has already been resolved. If you’re still experiencing any issues, please reach out to our support team directly via our free Basic Question form here so they can take a look for you. The issue you’re experiencing is likely to be specific to your site (e.g. plugin conflict).

Hey @nico23,

I’ve responded to you here. Let me know when you’ve had a chance to review my reply.

Thanks!