Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • June 4, 2020 at 11:58 pm #1219627
    liukdesign

    Hi guys, i have a big problem when i install woocommerce on my site.
    These writings (i want put the attachment but i don’t know how) are for debugging, when the screen is generic for woocommerce products. Many times the writing “critical error” comes out.

    The model version is updated (4.7.5), wordpress also (5.4.1) and woocommerce as well (4.2.0).

    Can you help me?

    Tks

    June 5, 2020 at 7:52 am #1219693
    liukdesign

    Someone can help me? This is the error
    http://liukdesign.net/Screen%20Shot%202020-06-05%20at%2007.39.32.png

    June 6, 2020 at 6:27 am #1219990
    Rikard

    Hi,

    Thanks for the screenshot. Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    June 7, 2020 at 12:21 pm #1220176
    mensmaximus

    This issue is caused by Enfold loading some assets on some WooCommerce Admin Screens (e.g. Dashboard, Orders, Coupons) without solved dependencies.

    The assets in question are:

    /enfold/config-templatebuilder/avia-template-builder/assets/js/avia-tab-section.js
/enfold/config-templatebuilder/avia-template-builder/assets/js/avia-table.js
/enfold/config-templatebuilder/avia-template-builder/assets/js/avia-tab-toggle.js
/enfold/config-gutenberg/js/avia_gutenberg.js
/enfold/config-gutenberg/css/avia_gutenberg.css
/enfold/config-templatebuilder/avia-template-builder/assets/js/avia-media.js

    Theese javascript and css files have the following dependencies:

    avia_builder_js
avia_modal_js
avia-modal-style
avia-builder-style
avia_element_js

    The problem occurs because the dependencies don’t get loaded on the WooCommerce Admin Screens. Therefore the handles are not registered.
    Enfold has always loaded those assets in various places where they are not needed at all (i reported that at least two times). With version 4.2 WooCommerce introduced a script preloader which checks for dependencies.

    Enfold has either to stop loading assets where they are not needed or to make sure the dependencies get loaded if an asset is needed.

    As for now the only thing you can do is to switch of debug mode to get rid of the php notices. But you have to life with tons of error log entries until Enfold fixes the bug.

    June 15, 2020 at 1:51 pm #1222645
    Yigit

    Hi,


    @mensmaximus     Thanks a lot for your help identifying the issue! I just reported it to our devs and shared your post as reference :)

    Best regards,
    Yigit

    June 15, 2020 at 2:20 pm #1222653
    liukdesign

    Thank you @mensmaximus.

    So @Yigit it’s a default problem? I cannot fix it for now?

    June 15, 2020 at 2:39 pm #1222660
    Yigit

    Hi,

    I will gladly share the solution with you here once our devs confirm one. For now, please consider setting WP debug to false in wp-config.php file.

    Regards,
    Yigit

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.