-
Posts
-
Hi Enfold team,
a few days ago after the WordPress core update to 6.3.2 an issue started on the backend, when editing Woocommerce products using the classic editor. I have done several tests on my staging site and it is clear, the issue comes from the Avia framework (Enfold 5.6.6). If I switch to another theme like twentytwenty, the issue is gone. Having that said, here are the specifics:On Woo product pages the classic editor (visual editor) is not accessible. The editor field is stuck on the “code editor” but at the same time the html code is displayed WHITE, so that at first it seems there is nothing. Only when highlighting text, one can see it. At the same time the Layout-Architect button does not work anymore.
Here is what I have tested so far:
* Theme: switching to another theme resolves the issue
* Theme: switching between Enfold child and Enfold does NOT resolve the issue -> no child-theme issue …
* Plugins involved: I have deactivated all plugins aside from Woo and then activated them sequentially. The test revealed that the conflict between core 6.3.2 and Avia occurs, when Gridbuilder plus WP Mail SMTP or Yaost Duplicate Post are active. I have rolled back those plugins, to test recent changes, but that’s not doing anything. Also, the problem dissapears with all those plugins active, when standard themes are use. Thus, all points to the Avia framework.I have gotten support from Gridbuilder. They tested all from their side and also did not find any issue in other themes. They suggested to look nto conflicts between Enfold and the latest WP Core update …
Strange fact: While it is impossible to work with the editor for WordPress products, the editor behaves normally for posts, pages, etc. It is a very specific issue for WordPress products only.
Here are some screenshots:
Additional info: I ran error display while testing and got no error massages. There is no issue on the frontend …
Could you please look into that issue? For now, I can work around it when I need to edit products. However, it needs to be fixed. What I fear is that the issue spreads to other classic editor input fields like for pages and posts when wp core further evolves.
Thank you and kind regards
MichaelHi there,
additional issues on the Woo product setting/creation backend page:* also the top sliders “help” and “custumize view” do not react on Woo backend product page. However all works fine on backend pages for posts and pages …
* In addition, “add new category” does also not work for the woo product on the product creation backend page …
* In addition, the “product tags” section does not open on the product setting backend pageIt clearly affects something fundament with respect to this specific post type (which a Woo product is simply, I guess, but I may be wrong).
Hi there again,
additional infos on the issue:
On the production site (in A Multisite Network), the workaround to deactivate the plugins I found working on the single staging site involved does not work. The issue persists there, which makes it very hard to change or add Woocomerce products.
Additonal issues (in all instances) are:
* adding product gallery images does not work
* quick edit in the Woocommerce product list does not work
in both cases, nothing happens upon clicking.Hope there is a solution to this.
Thank you for your efforts and kind regards
MichaelHi Michael,
Thanks for the updates. Which version of the theme are you running? If you could give us step-by-step instructions on how to reproduce the problem, then that would be appreciated.
Best regards,
RikardHi Rikard,
theme version is 5.6.6. as I have told. However, I have solved the problem just now myself, since I was in exploration mode since this morning … It was a PHP issue. Until now I was running the site network on PHP8.0.30. Upgrading PHP to 8.1 removed the issue.
I still have this issue one one independent single site which runs on PHP 7.4, which deploys a critical error when switched to PHP 8.0 or 8.1. – However, I will have to find a solution to switching that site to PHP 8 anyway, so there is no more need to find a solution for the Woo product backend issue from my side …
Anyway, the issue might come up for other users below PHP 8.1, since I was able to reproduce it on two different sites.
Best
MichaelHi,
Great, I’m glad that you found a solution, and thanks for sharing. Please let us know if you should need any further help on the topic, or if we can close it.
Best regards,
Rikard
- The topic ‘Classic editor issue created by Avia framework after WordPress update to 6.3.2’ is closed to new replies.