Yoast SEO causing UpdraftPlus conflict after 5.6 update?

We are sorry to hear that you are having trouble between Yoast SEO and UpdraftPlus. Unfortunately, we were unable to reproduce the issue on our end.

We were able to run the manual database backup from the 3rd party UpdraftPlus plugin when Yoast SEO v14.6 was active with WordPress v5.6. In addition, we couldn’t reproduce the UI issue either.

Therefore, we’d like you to please perform a full conflict check while all the non-Yoast+UpdraftPlus are disabled and switching the theme to the default 2020 theme.

Can you please confirm what happens after performing the full conflict check?

Okay, this is bizarre. After turning everything off and selectively reenabling, now the problem occurs only when I activate a different plugin (WP Accessibility Helper). When I tested this before, tonight, on this same site, the issue did NOT occur with that plugin enabled, but did occur with Yoast SEO enabled. Now it’s the other way around.

In this case, we highly recommend you please reach out to the 3rd party UpdraftPlus plugin to make sure the relevant plugin is compatible with WordPress v5.6.

I have, as indicated in my original post.

We know that you have already reached out to the UpdraftPlus support about the issue. We also see the issue you are now experiencing occurs when another 3rd party plugin “WP Accessibility Helper” is active.

In this case, you’ll need either of the relevant plugin support for further assistance on this as the issue now seems specific to another plugin.

Or the issue still occurs when Yoast SEO is active on your site instead of the 3rd party WP Accessibility Helper plugin?

On one of my sites, and the one I just tested when I originally tested earlier today, the issue occurred only when Yoast SEO was active, regardless of whether WP Accessibility Helper was activated or not. On the latter site, after I once again deactivated and slowly reactivated the plugins and briefly switched to the default theme as you asked, the issue did not occur when Yoast SEO was activated (which it did before), but did occur when WAH was activated (which it previously did not). On the other site, the issue recurs when I activate Yoast SEO and stops if I deactivate Yoast SEO.

(I realize this is a little confusing, but it is a bizarre, inconsistent issue.)

Due to the nature of the issue, we think it’s specific to your setup as we were also unable to reproduce it on our end. So, we’ll need to take a look at your setup but we can’t do it here as this is a public forum.

So, if you’d like us to investigate the issue further for you, you can get the Yoast SEO Premium subscription that will grant you access to our premium support where we can provide support through email privately. This will allow us to take a look at your setup.

I have the same problem – but I don’t have any accessibility plugins installed: I deactivate Yoast and Updraft manual backups are no longer blocked.

Hi @biancaseda

We are sorry to hear you are experiencing something similar.

Per the forum guidelines, we ask that you please create separate topics for the issues you are experiencing. That way it’s easier to track issues and provide assistance on your specific concerns on your specific site. Plus, you will get your own alerts for the issue rather than someone else’s.

You can open a new topic here: https://www.ads-software.com/support/plugin/wordpress-seo/#new-post.

@mazedulislamkhan: Attempting to use my support request to solicit for your paid product strikes me as a sign of bad faith. I freely admit that this is a complex issue, and how much it actually has to do with the Yoast SEO plugin remains unclear, but I thought these forums were not supposed to be used for commercial solicitation.

@ate-up-with-motor We can certainly understand why you might feel that way, but that isn’t our intention. Your issue just requires further investigation that would require us logging into the site to check into it further, which can’t be done within this support channel.

Hi @ate-up-with-motor,

It looks like we’ve provided the next steps for this issue. If you find a conflict and you can provide the steps to reproduce it, you can create a new GitHub bug report for our developers.

In the meantime, we’re marking this issue as resolved due to inactivity. You’re welcome to create a new forum topic if you have any other questions.

It now seems to have resolved; it was a very weird thing.