Hostinger Panel | WordPress.org

Hi @maportugal

Uncaught Error: Call to undefined function WC_Autocomplete_Address\is_checkout() in /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-content/plugins/autocomplete-address-for-woocommerce/includes/class-wc-checkout-scripts.php:17 Stack trace: #0 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/class-wp-hook.php(324): WC_Autocomplete_Address\Checkout_Scripts->load_scripts() #1 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/script-loader.php(2265): do_action() #4 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/class-wp-hook.php(324): wp_enqueue_scripts() #5 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #6 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/plugin.php(517): WP_Hook->do_action() #7 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/general-template.php(3050): do_action() #8 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-content/themes/superio/header.php(18): wp_head() #9 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/template.php(810): require_once(‘/home/u16268693…’) #10 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/template.php(745): load_template() #11 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/general-template.php(48): locate_template() #12 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-content/themes/superio/page.php(14): get_header() #13 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-includes/template-loader.php(106): include(‘/home/u16268693…’) #14 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-blog-header.php(19): require_once(‘/home/u16268693…’) #15 /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/index.php(17): require(‘/home/u16268693…’) #16 {main} thrown in /home/u162686931/domains/t1e1.com.br/public_html/pressrelease/wp-content/plugins/autocomplete-address-for-woocommerce/includes/class-wc-checkout-scripts.php on line 17

After checking the error log and your chat details with Hostinger support (I had to translate to grasp fully), it appears that the Autocomplete Address for WooCommerce plugin is causing the issue, rather than the WooCommerce core plugin.

This is a third-party plugin, and we don’t provide help & support for 3rd-party plugins or themes as they’re outside our support scope. It would be best to reach out to the plugin developer for further assistance.

I hope this provides some clarity. Please let us know if you have any other questions!

Thank you for translating the conversation, I had forgotten about that.
Well, this log in the conversation only occurred because the plugin you referred to remained active after Hostinger deactivated WooCommerce. When this plugin was also deactivated, the specific error disappeared.
Now the main error remains. When I try to access the Hostinger panel for two subdomains, this message appears, which does not happen with WooCommerce disabled.

“Oops! The WordPress Control Panel is not working properly due to unforeseen errors.”

Direct access via the WordPress login page is normal.

I did the following, I installed the WooCommerce plugin on a third website and the same error happened. In other words, the installed plugin actually causes this error on the Hostinger panel.

I discovered one detail, this problem occurs in conjunction with the All-In-One Security (AIOS) – Security and Firewall plugin. In other words, the Hostinger panel stops working if both are installed. If either of the two is installed without the other, the problem does not occur. Hostinger does not provide logs and claims that the problem is with the plugins, which together make the WordPress installation unrecognizable

Hi @maportugal

Thanks for sharing further details. Although I tried to replicate the error on my testing site hosted on Hostinger, where I installed both WooCommerce and All-In-One Security, but I couldn’t. However, there seems to be a conflict between both on your Hostinger panel.

While WooCommerce is designed to work seamlessly with most plugins, conflicts can occasionally occur, especially with security plugins that may have strict rules that can interfere with the functionality of other plugins.

However, could you please disable AIOS to investigate the issue further? Then, see if the error still appears when WooCommerce is active. If not, the next step is to restore AIOS’s default settings and see what happens. Should the error persist even with the default settings, it would be best to contact the All-In-One Security plugin’s developers. They may be able to shed some light on why their plugin might be clashing with WooCommerce.

I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight/information.

Disable AIOS, restore plugin default settings, already done that. In short, the Hostinger panel only works if one of the plugins is installed, it doesn’t work with both.
I tested it on a new, completely original, initial installation and on another site. Still the error occurred.
Now, from what you said, this error did not occur in your installation. Perhaps then looking for AIOS will not lead to a solution, which could be a specific Hostinger server problem, or even the translation of its portal, or something else specific.

Hi @maportugal

Given the steps you’ve taken, the issue may be specific to your Hostinger server or another unique factor, as you’ve suggested. You can see my testing site, which is hosted on Hotinger, working fine:

At this point, I would recommend contacting Hostinger’s support team. They may be able to provide insights into server-specific issues that could be causing this conflict. Additionally, they can check if any server logs might point to what’s going wrong when both plugins are active.

In the meantime, you could also try to temporarily switch to a default WordPress theme (like Twenty Twenty-Four) and disable all other plugins except for WooCommerce and AIOS to see if the issue persists. This could help to rule out any theme or plugin conflicts.

You can also enable WP Debug mode which might gives you further insights about the error.

I’m sorry I can’t provide a more definitive solution at this time, but I hope these suggestions help you troubleshoot this issue.

If you have any other questions, feel free to ask.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer