- This topic has 7 replies, 4 voices, and was last updated 4 hours, 46 minutes ago by
.
-
Posts
-
When I enable the plugin I get the following error:
PHP Fatal error: Uncaught Error: Call to undefined method Porto_Woo::load_packages() in /srv/htdocs/wp-content/plugins/porto-functionality/porto-woo.php:27This field is Private Content.
I have updated the plug-ins and themes to the latest versions, but the problem still exists.
Hello, @myhigrow,
Kindly consider switching the theme to the Parent Theme temporarily, as the current activation on your site is set to the Child Theme.
Additionally, deactivate all third-party plugins on your site and reattempt the task. If this resolves the issue, kindly reactivate each third-party plugin one at a time to identify which one is causing the problem on your site.
Please note: Before proceeding, it’s advisable to take a complete backup of your site or clone it to a test environment. This precaution ensures that any changes made can be tested without affecting the live site.
Best Regards,
PThemes Team.Hello, I have the same problem, but i dont have access to admin panel. I recived this msg, but this recovery link dont work. What can I do?
WordPress версия 6.4.2
Текуща тема: Porto (версия 7.0.1)
Текущо разширение: Porto Theme – Functionality (версия 2.11.1)
PHP версия 7.4.33Данни за грешката
================================
Грешка от вид E_ERROR беше причинена от ред 27 от файла /home/bp***/public_html/wp-content/plugins/porto-functionality/porto-woo.php. Грешка: Uncaught Error: Call to undefined method Porto_Woo::load_packages() in /home/bp***/public_html/wp-content/plugins/porto-functionality/porto-woo.php:27
Stack trace:
#0 /home/bp***/public_html/wp-content/plugins/porto-functionality/porto-woo.php(30): Porto_Woo->__construct()
#1 /home/bp***/public_html/wp-content/plugins/porto-functionality/porto-functionality.php(287): require_once(‘/home/bp***/…’)
#2 /home/bp***/public_html/wp-includes/class-wp-hook.php(324): Porto_Functionality->load_woo(”)
#3 /home/bp***/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#4 /home/bp***/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#5 /home/bp***/public_html/wp-settings.php(506): do_action(‘plugins_loaded’)
#6 /home/bp***/public_html/wp-config.php(96): require_once(‘/home/bp***/…’)
#7 /home/bp***/public_html/wp-load.php(50): require_once(‘/home/bp***2/…’)
#8 /home/bp***/public_html/wp-admin/admin.php(34): require_once(‘/home/bp***Must have been from a recent auto update. porto_woo.php code shows no such “load_packages()” method. I had to rem out ‘self::load_packages();’ to get my site back up.
use Automattic\WooCommerce\Packages;
defined(‘ABSPATH’) || exit;
/**
* Remove woo gutenberg blocks.
*
* @since 2.7.0
*/
class Porto_Woo extends Packages
{
/**
* The Constructor
*
* @since 2.7.0
*/
public function __construct()
{remove_action(‘plugins_loaded’, array(‘Packages’, ‘on_init’));
if (!is_admin() && get_option(‘porto_disable_woo_blocks’, false)) {
unset(self::$packages[‘woocommerce-blocks’]); // woocommerce block
if (function_exists(‘yit_maybe_plugin_fw_loader’)) {
function yith_plugin_fw_is_gutenberg_enabled()
{
return false;
}
}
}
//self::load_packages();
}
}
new Porto_Woo();Hello, @everyone,
Sorry for the inconvenience but we have fixed this compatibility issue.
Please check our theme changelog: https://themeforest.net/item/porto-responsive-wordpress-ecommerce-theme/9207399#item-description__change_logs
Please update the theme and core plugin again manually by redownloading from Themeforest and it will solve your issue.
Please try to update the theme and porto functionality plugin via FTP or Cpanel. https://www.portotheme.com/wordpress/porto/documentation/update-theme/
After that, please should apply the patches in Porto > Patcher: https://www.portotheme.com/wordpress/porto/documentation/porto-patcher/
Best Regards,
PThemes Team.Thanks for the fast reply. I just grabbed the plugin from ThemeForest and now I can see the bug fix and it works. Still showing the same version for the plugin, though (3.0.2), but we’re up and running. Thanks.
Hello, @dfrey,
Great to hear that the bug fix is working for you! I appreciate your prompt response in resolving the issue.
Regarding the version display, it’s not uncommon for the version number to remain the same after a bug fix. So yes the version of the plugin is the same.
If you have any further questions or encounter any issues, feel free to reach out. Thanks again for your patience!
Best Regards,
PThemes Team.
- You must be logged in to reply to this topic.