Hello there, since many years i'm using this feature "Disable Gutenberg Editor" on the Salient Builder's option theme (/wp-admin/admin.php?page=vc-general).
Since the last update of WooCommerce, today, the 8.0 i see a lot of files who are loaded for the WooCoommerce Blocks Editor (gutenberg) (see attached screenshot).
i try this snippet but that not working on the last update of WooC :
It looks like WooCommerce is loading a bunch of new stylesheets for v8 which are registered through the block.json for each block. Others have pointed this out here: https://github.com/woocommerce/woocommerce/issues/39658
There's no workaround from the developers yet, but i'm sure they will address it soon within that github issue.
Hello there, since many years i'm using this feature "Disable Gutenberg Editor" on the Salient Builder's option theme (/wp-admin/admin.php?page=vc-general).
Since the last update of WooCommerce, today, the 8.0 i see a lot of files who are loaded for the WooCoommerce Blocks Editor (gutenberg) (see attached screenshot).
i try this snippet but that not working on the last update of WooC :
Is this possible to fix that ? because the "Disable Gutenberg Editor" option still checked.
regards
Attached files: pastedImage.png
Hey Again,
Try using this field and check:
Thanks
ThemeNectar Support Team
Hello there, it's checked that remove the gutenberg for the posts and page but not for the news WooCommerce Block version
regards
Hey Again,
The new version seems to have added more . You can find all the handles using the "Query Monitor" Plugin:
Thanks.
ThemeNectar Support Team
Hi Tahir thanks for replying, so if i understand that will be fixed on futures updates ?
regards
Escalating this to the developer to check if a quick fix is available.
Thanks
ThemeNectar Support Team
Hey benoitfouc33,
It looks like WooCommerce is loading a bunch of new stylesheets for v8 which are registered through the block.json for each block. Others have pointed this out here: https://github.com/woocommerce/woocommerce/issues/39658
There's no workaround from the developers yet, but i'm sure they will address it soon within that github issue.
Kind regards