Forum Replies Created
-
AuthorPosts
-
April 30, 2020 at 5:57 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1208587
Hi,
The topic can be closed.Regards,
Jos
April 27, 2020 at 9:52 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1207621Hi Ismael,
Thank you to determine the cause of the error.
The reason the version of the WordPress installation was unknown is that in the Shield Security plugin the ‘Mask WordPress Version’ configuration was set. Undoing this setting resolves this error.Thanks again.
JosApril 22, 2020 at 12:19 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1206159Hi,
Very strange that you can’t login. I have got a message form auditing system that you did login (see the private content).Keeping the lines of code disabled for now to keep the error from occurring is a temporary work around. It’s not a definite solution.
Please take a look again, to come to a solution. Thanks in advance.Regards,
JosApril 17, 2020 at 8:10 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1204770Hi Ismael,
The error still exists!
The previous time you edited the woo-loader.php commenting the following lines:if( ‘block’ == AviaGutenberg()->selected_editor() )
{
require_once( ‘class-avia-wc-block-editor.php’ );
}By uncommenting these lines the error is reintroduced:
2020-04-17T17:56:07+00:00 CRITICAL Uncaught Error: Call to undefined function AviaGutenberg() in /home/deb77506/domains/livelycollection.com/public_html/wp-content/themes/enfold/config-woocommerce/woo-loader.php:13
Stack trace:
#0 /home/deb77506/domains/livelycollection.com/public_html/wp-content/themes/enfold/functions.php(646): require_once()
#1 /home/deb77506/domains/livelycollection.com/public_html/wp-settings.php(514): include(‘/home/deb77506/…’)
#2 /home/deb77506/domains/livelycollection.com/public_html/wp-config.php(99): require_once(‘/home/deb77506/…’)
#3 /home/deb77506/domains/livelycollection.com/public_html/wp-load.php(37): require_once(‘/home/deb77506/…’)
#4 /home/deb77506/domains/livelycollection.com/public_html/wp-cron.php(44): require_once(‘/home/deb77506/…’)
#5 {main}
thrown in /home/deb77506/domains/livelycollection.com/public_html/wp-content/themes/enfold/config-woocommerce/woo-loader.php on line 13Please have a look again.
Regards,
JosApril 14, 2020 at 11:22 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1203818Hi,
The security configuration is disabled.
Regards.
JosApril 10, 2020 at 2:13 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1202675Hello,
Can somebody give me support on this subject??
Thanks,
JosApril 6, 2020 at 12:19 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1201203Hi Ismael,
Sorry for that.
Please add your IP address to the <Files wp-login.php> section in the .htaccess file in the public_html directory.Thank you,
Jos
April 1, 2020 at 8:44 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1199875Hi Ismael,
Thanks for your reply.
Temporarily removing the mentioned snippet in the parent theme’s functions.php doesn’t raise the fatal error anymore. However the shop page is now a little bit crunched and the landing page results now in an other error.After installation of Enfold 4.7.4 I got still the fatal error in the server logging. The WP health check says now:
The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.
The REST API call gave the following unexpected result: (500)
There has been a critical error on your website.March 30, 2020 at 9:55 am in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1199025Hi Ismael,
Yes, see me previous message! I placed the snippet in the child theme’s functions.php.
What are other options to solve this problem?Kind regards,
JosMarch 27, 2020 at 12:50 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1198316Yes i am sure. I first updated Enfold , put the snippets in the functions.php (child theme) and afterwards still got the following error:
[Fri Mar 27 11:36:58.893706 2020] [lsapi:error] [pid 3828650:tid 139979007055616] [client 141.138.168.124:42668] [host http://www.livelycollection.com] Backend fatal error: PHP Fatal error: Uncaught Error: Call to undefined function AviaGutenberg() in /home/deb77506/domains/livelycollection.com/public_html/wp-content/themes/enfold/config-woocommerce/woo-loader.php:13
March 25, 2020 at 1:31 am in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1197535Hi,
Updating from Enfold 4.6.3.1 to 4.7.3 is now without an error in the frontend but de host errorlog still list:
Backend fatal error: PHP Fatal error: Uncaught Error: Call to undefined function AviaGutenberg() in /home/deb77506/domains/livelycollection.com/public_html/wp-content/themes/enfold/config-woocommerce/woo-loader.php:13When the twenty twenty theme is activated or woocommerce is disabled this error isn’t raise
Kind regards,
JosMarch 18, 2020 at 3:35 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1194135Hi Ismael,
As mentioned before the ‘use WP classic editor’ in the theme options doesn’t make a difference.
I downgraded Enfold to version 4.6.3.1 and for now is there no fatal error anymore. But after upgrading Enfold it keeps resulting in the fatal error.Best Regards,
JosMarch 16, 2020 at 11:47 am in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1193444Hello,
Is still get the error! WordPress notifies me too:
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with your theme, Enfold.
What can I do??
Greats,
JpsMarch 11, 2020 at 5:40 pm in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1192382Hi Ricard,
I installed the perfmatters plugin and disabled the woocommerce cart fragments. The logging on the server mentions stille the same: PHP Fatal error: Uncaught Error: Call to undefined function AviaGutenberg().
Don’t know how futher.Greats,
JosMarch 11, 2020 at 10:12 am in reply to: Fatal error caused in enfold/config-woocommerce/woo-loader.php #1192178This reply has been marked as private.Yes the issue is resolved with the css i posted.
Thanks for your support!Jos
After some trial and error I have the add-to-card-button disabled. The standard woocommerce tooltip will still displayed on hover.
Thanks for your suggestion Vinay!div.single_variation_wrap.woocommerce-variation-add-to-cart button[disabled]:active, button[disabled],
input[type=”button”][disabled]:active,
input[type=”button”][disabled],
input[type=”submit”][disabled]:active,
input[type=”submit”][disabled],
button[disabled]:hover,
input[type=”button”][disabled]:hover,
input[type=”submit”][disabled]:hover
{
pointer-events:hover;
opacity: .3;
}Hi Vinnie,
I could not find the solution. I will contact you again when the site is online.
thanks,
JosHi Rikard,
I’m still developing local on the website, so I haven’t the site online. May be within a couple of weeks. The behavior is the same as all the plugins (except WooCommerce itself) are disabled.
I tested the woocommerce update also with the Enfold Shop Demo. The behaviour is there the same with variable products.Regards,
Jos -
AuthorPosts