Stephane PISKORZ

Hi Pawel (@wpmudev-support9)

Thanks for the reply. Yes, I tried that but couldn’t go much further than the first row with the first three images (left, center and right). The center image does not change. The right and left images change according to the value of the previous select field.

If I pile up the HTML fields (each one having a different visiblity condition), the three images are not horizontally aligned, which is the goal here (at least on desktop).

I hope this explanation is clear enough. Otherwise I could send you a screencast of the form.

Hi Patrick (@wpmudevsupport12),

It’s great already that the related problem has been found. I can wait for the update regarding this issue as the bypass works, I am actually glad that I could help point it out.

Best regards,

Hi Adam (@wpmudev-support8),

Thanks for the trick, it works indeed. Faster than rebuilding the form too! ??
Still, it would be interesting to understand why it acted like this.

Best regards,

Hi Adam (@wpmudev-support8),

Thank you for your reply. Indeed, it is strange. I hope the dev team will find a solution, because I don’t see myself rebuild all the forms from scratch after an update ;-).

Best regards,

Hi Kasia (@wpmudev-support2),

Yes, I did downgrade on this prod website, but went on testing on a staging website, same issue.
Here’s the pastebin link: https://pastebin.com/eDhE58S9
Please check the nubmer-6 field, you’ll see the problem (also works with number-11, number-12 and number-16 fields): there’s an indication text filled and a default value as well, set to 0.

Kind regards,

Hi Jeroen (@jeroenrotty),

I was actually preparing to post the issue on Github when I got notified of an update for Divi (in its latest version).
I took a look at the changelog and the first line caught my attention: “Fixed auto-opening preview tab when Divi Woo Product page is loaded w/ Rank Math plugin enabled.”

Before posting anything, I decided to test it, so I pushed the update and repeat the process again, and it worked: I was able to revert back to the standard editor without a 500 error.

Funny thing is, this website never had RankMath installed on it, but I guess they share common language with Yoast.

Anyway, thanks everyone for your help, and I can now mark this issue as resolved.

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 @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 @wfphil ,

Oh my, I feel ashamed, I didn’t even check the IP and therefore didn’t know it belonged to WP Rocket. So sorry for all the fuss. It’s still better to be safe than sorry. Anyway thanks a lot for our time and patience (and for the WP Rocket documentation link, I actually completely missed that one!).
I’ll mark this post as resolved and go hide somewhere ??

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 @wfphil,

You will find 2 IP addresses :
109.234.162.90 and 135.125.83.227

135.125.83.227 is the that keeps coming back and that I would like to remove.

Hi @wfphil,

I just reinstalled it now, from scratch (disconnected form Wordfence Central, deactivated the plugin and then deleted it, and finally deleted all tables from the database). The whitelisted IP was there ??

I just sent the report from the diagnostics tab.

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.

Hi @wfphil,

I ran the search, and nothing regarding the function you mentioned.
Indeed, I was referring to the IPs that bypass all rules, and that’s exactly the problem: even after deleting all tables starting with wf, and installing again from scratch, the IP I entered in the first place comes back.

It doesn’t hurt, it is just weird, I mean, it just shouldn’t be there ??

Hi Phil (@wfphil)

I never used that function; still I doubled checked the child theme files and didn’t find anything related to that function.
Is there anything else that I could try?