Closed woodypeck closed 1 year ago
Hey @woodypeck,
Thank you for creating a second issue here - but we tried again to reproduce it to no avail. When we run the latest versions of the theme/plugins you mentioned: MailPoet 4.12.2, WooCommerce 7.6.0, WordFence 7.9.2 and Yoast SEO 20.5, eStore 1.6.1 - we don't have any issue updating or reading the production description content in the editor.
We believe that this is a specific issue to your site that needs further investigation - but we don't offer support on our GitHub repository here. On the forums we also give support, but that is also limited as long as we can't reproduce the issue. Please check if you can narrow it down or find the exact Javascript error(s) that occur and check with your site developer or web host.
Hi Jeroen
Thank you for your reply and I will do some more digging and interrogation. However, I posted the issue on the WordPress forums and there are a few other people who are having the same issues - so it is not just our website. It is an issue with the plugins somewhere. Just need to find out what it is.
Kind Regards Steve
Please give us a description of what happened
The latest upgrade in Yoast SEO has blanked out all the Product text blocks in Woo commerce. My whole site is upto date with latest releases of Wordpress, Woo Commerce and Yoast SEO! We use the eStore theme and this is up to date also. We have tried changing the Theme to Twenty Twenty-Three, but it doesn't make any difference - still the same.
If I deactivate Yoast SEO the WordPress and Woo Commerce site works OK. The Product page text blocks show the text view text correctly. But with Yoast SEO activated it doesn’t show up correctly and none of the pull down YOAST pull down tab lists are visible, however our website is still working and visible to the web? We just cannot use Yoast SEO for any new product launches or posts?
Now I submitted a Bug report 2 days ago relating to this and got a reply that you could not replicate the fault so closed the bug report prematurely. On further investigations I have found 2 plugins that Yoast is conflicting with. When they are BOTH activated together on our website - but individually they work with Yoast on our website -just not together with Yoast.
We went then into Troubleshooting mode and set all plugins to OFF, then we enabled just woo commerce and Yoast - all ok, then we enabled Mailpoet and all was OK as well? After many checks and re-checks it seem either Mailpoet or Wordfence Security - when 1 is deleted the other works fine with Yoast and the product page show up fine. If they are both active then it causes the original error we reported? So it is the combined position of both of these plugins being active that causes Yoast SEO to affect the product page to not work and show the SEO boxes correctly. Either plugin on its own will not cause the problem with Yoast SEO
So Yoast, Mailpoet & Wordfence Security all active causes and error with Yoast showing the page correctly. Which one has the conflict I am not sure - but the common error is what Yoast is activated with either of the other plugins. If that makes sense?
Finally I did notice that in Troubleshoot mode Yoast SEO on the top bar shows "No Index" when you hover your mouse over it? If that means anything?
I have tried this on 3 different computers and laptops as well as my Android phone. I have used the incognito mode, removed all the cache, and even used an old windows 10 operating system to see if it is any different. And it is all the same. I have taken some screen shots where I can highlight the script text / which seems to be white on white after this problem / and then I can highlight the script text / but it still does not who the product text box correctly if Yoast SEO is activated.
Before the latest YOAST update install the product text always shows and the SEO pull down boxes work fine and allow you to chose the SEO name, site title, etc and readability score etc.
Here you can see the troubleshoot screen with each plugin deactivated and everything is working but if both are activated then the original error still occurs. |In the last few minutes there is a new update for Mailpoet which I have installed = 4.12.1. However it has not improved or changed the problem.
To Reproduce
Step-by-step reproduction instructions
Expected results
Actual results
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
Technical info
Used versions