Skip Navigation

[Resolved] Problem after installation

This thread is resolved. Here is a description of the problem and solution.

Problem:
I have a message A critical error has occurred on this site.

Solution:
Upon further review and by enabling the debug mode I was able to see that the issue was coming from a different plugin.
I advised the customer and shared the logs.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 5 replies, has 2 voices.

Last updated by Mateus Getulio 11 months, 1 week ago.

Assisted by: Mateus Getulio.

Author
Posts
#2678886

I installed the plugin and now I don't have access to the site
I have a message A critical error has occurred on this site
hidden link

#2678907

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello there,

We're sorry to hear about your issue. Can you please enable the debug mode so we can figure out what's causing this issue?

Please add the following code to the wp-config.php file of your site:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 ); 
define( 'SCRIPT_DEBUG', true );

Please check following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, please reproduce the error again and check if you'll find a debug.log file inside the wp-content folder.

If you locate it there, please send us the last lines here in the ticket.

After that, please rename the toolset plugin folder available in the wp-content/plugins so your site gets accessible again.

Thank you, please let me know.

#2679007

Now nothing costs me, neither troubleshooting nor anything, and I was also blocked from the storage server
Why?
what am I doing now?
Urgently waiting for an answer!
Younes

#2679017

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello,

I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Please notice that the FTP access is important here since the site seems to be down as per your replies. If you're able to access it, please ask your hosting provider to review it. With the FTP access we'll be able to deactivate the plugin and bring the site up in case there's a plugin causing a fatal error and locking you out the wp-admin dashboard.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link

Please, let me know if you need any additional details. Have a nice day.

#2679023

This is the IP 81.199.151.61
I don't know where I get my ETP from

#2679024

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello,

Thank you for providing us with those details.

Upon reviewing the situation, it appears that even after deactivating Toolset, the site continued to experience a fatal error. To dig deeper into the issue, I enabled debug mode and discovered some critical errors in the logs related to the 'woocommerce-views' plugin.

Here are the details from the log:

[18-Jan-2024 20:44:40 UTC] PHP Fatal error:  Uncaught Error: Call to a member function make() on bool in /wp-content/plugins/woocommerce-views/application/Bootstrap.php:128
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): WooViews\Bootstrap->register_legacy_hooks()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-settings.php(643): do_action()
#4 /wp-config.php(102): require_once('...')
#5 /wp-load.php(50): require_once('...')
#6 /wp-admin/admin.php(34): require_once('...')
#7 /wp-admin/index.php(10): require_once('...')
#8 {main}
  thrown in /wp-content/plugins/woocommerce-views/application/Bootstrap.php on line 128
[18-Jan-2024 20:44:41 UTC] PHP Fatal error:  Uncaught Error: Call to a member function make() on bool in /wp-content/plugins/woocommerce-views/application/Bootstrap.php:80
Stack trace:
#0 /wp-includes/class-wp-hook.php(324): WooViews\Bootstrap->init_template_loader()
#1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /wp-settings.php(643): do_action()
#4 /wp-config.php(102): require_once('...')
#5 /wp-load.php(50): require_once('...')
#6 /wp-blog-header.php(13): require_once('...')
#7 /index.php(17): require('...')
#8 {main}
  thrown in /wp-content/plugins/woocommerce-views/application/Bootstrap.php on line 80

In light of this, I temporarily disabled the 'woocommerce-views' plugin, which resulted in your site functioning properly again. Based on these findings and my tests, it seems that the issue isn't related to Toolset.

Your site is now up and running, but please note that the 'woocommerce-views' plugin has been disabled for the time being. To resolve issues specific to this plugin, I recommend reaching out to the plugin's author or support team for specialized assistance.

I understand the challenges of navigating these technical aspects and appreciate your patience in this matter. If you have any more questions or need further assistance, please don't hesitate to ask.

Thank you,
Mateus

#2679272

Thank you very much for the treatment, I have no words, you saved me
PS I haven't answered until now, I live in Israel and because of the time difference and a weekend I didn't check after the last time I sent you
And again thank you very much