bug between Yoast and Divi

I can confirm two issues generated by the basic Yoast SEO plugin and DIVI.
1. Editing a Product Post (WooCommerce), causes DIVI to spawn a blank preview page.
2. Exiting any Editing Mode spawns a “Your changes will not be saved…” warning.

All plugins on this site reflect the latest versions. The issue was tested by unplugging almost all plugins other than WooCommerce and WordFence after checking the operation of the website in “Safe Mode”.

Disabling Yoast solved the issues.

Hello Stephane,

We are sorry about the conflict between Yoast SEO, Divi and WooCommerce. The latest version of WooCommerce is v5.9.0. Have you considered updating and checking if the problem persists?

Do keep us updated.

Hi Maybellyne (@maybellyne),

I just updated WooCommerce too (every plugin and theme is up to date now on this website), and still the same problem. I double checked: if Yoast is active, I get the error 500 (something calls the /wp-admin/admin-ajax.php file)

If it’s inactive, no problem, I can revert to the classic editor.

I had to deactivate Yoast a while back because of the exact issues @wudman mentioned.

@mollyann1,
I am starting a new thread with some additional information related to WordPress and DIVI.

Versions: Yoast 17.7, WordPress 5.8.2, DIVI 4.14.2 & WooCommerce 5.9.0. My additional information may be specific to your issue and meet WP posting rules (therefore get a response.)

• This reply was modified 2 years, 11 months ago by Wudman.
• This reply was modified 2 years, 11 months ago by Wudman.

Hi @stefanp44

Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict, is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Twenty.

Please test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin has a troubleshooting mode, which does not affect normal visitors to your site.

If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts

Could you check and perform a conflict check with a default WP theme (such as TwentyTwenty) and only Divi, WooCommerce, and Yoast SEO as the plugins activated and see if this issue still occurs when editing product pages?

Hi Michael (@mikes41720),

First of all, if I deactivate Divi and use TwentyTwenty instead, the test will just be useless, as Divi is a theme, and the function I’d like to use (described in this post) would not be there at all.

I did that testing before posting here. Here are the steps I took beofre coming here:
– renaming the mu-plugins folder to mu-plugins-test, so they become inactive
– use Divi parent theme instead of the child theme
– deactivate all plugins, except WooCommerce
=> the button “revert to standard editor” works

and then, one step at a time:
– restoring the proper name for mu-plugins folder => the button works
– switching back to the child-theme => the button works
– at that point, I knew that it was a plugin creating a conflict, and to be honest, my money was on either on Wordfence or Wp-Rocket.
– the website uses 21 plugins, 19 were deactivated so I started to activate them one by one and test each time => the button works, except when Yoast SEO is active

After that, I installed a blank installation of WordPress, with Divi, Woocommerce and Yoast. I tried to activate the Divi Builder on one product: couldn’t save it. I deactivated Yoast SEO, it worked fine.
After reactivating Yoast, I went back to edit the product and click on the “revert to standard editor” button, the dev console showed an error 500. I deactivated Yoast again, no problem using that button.
Hence my post here and my suspicion of a conflict between Yoast and Divi

Hi @stefanp44

Thanks for this information.

I’ve tried to recreate this on a test site with just the Divi Theme 4.14.2, WooCommerce 5.9.0, and Yoast SEO 17.7.1, and when I tried to create a new product in the Divi Builder and tried to ‘save draft’, it did result in the ‘Your save has failed’ with a 500 internal server error in the browser’s console, and that this didn’t occur when the Yoast SEO plugin was deactivated.

Would it be possible for you to share a screenshot from your server’s logs for any relevant error messages related to the 500 error at around the same timestamp when creating the new product? You can use snipboard.io or imgur.com or a similar site to upload a screenshot and share a link here.

Thank you for bringing this issue to our attention!

We apologize?for the trouble you are currently experiencing with our plugin. I’ve created an internal bug report for our product team.

What’s next?
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report.

If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic.

—

We recommend that you also reach out to WooCommerce and Divi/Elegant Themes, as having all teams involved will help in possibly a quicker resolution for this issue.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Hi @devnihil

The issue is nowhere near resolved at the time being, as stated by @mikes41720. I will get in touch with both Divi and Woocommerce support, probably tonight.

I just had one more question beofre you can actually close this issue: where do you need me to send the screenshot of the server logs?

Hi @stefanp44

We’ve created an internal report. But if possible, if you could also create a public issue on GitHub (by following the steps here), you can add screenshots in the GitHub issue for the 500 errors in the server logs. That would be useful information that would help. You can also reference this forum thread in your report.

Yes, please do reach out to Divi and WooCommerce, as having those other teams will also help in the resolution of this issue.

Hi,

Were you able to create the public issue on GitHub regarding this potential issue with Yoast SEO, Divi, and WooCommerce> And to provide the 500 server error logs as well in the details?

Hi Michael (@mikes41720),

Not yet, didn’t find the time yet; I’ve been in touch with the Divi team on a daily basis though, and it is strange: they did 2 clones of the installation : on one of them they were not able to replicate the error, and they could on the second one.

Besides, even with the debug mode on and the error displayed in public (just for the duration of the test, not the whole time of course), no errors are logged in the debug.log fle, which is a major drag. I can only see it on the server logs, but it doesn’t specify the source of the error, just that it occurred.

I will compile this data and create a public issue on GitHub as soon as I can.

Hi,

Thanks for providing this update. Please do let us know once you’ve been able to log the public issue on GitHub as well.

Hey Stephane,

Any updates on this? Just checking in as we normally close down forum tickets after a week of inactivity.