Closed zulfgani closed 5 years ago
That's spot. We removed that function because it was calling server updates checks with woocommerce.com. We don't intend to manage that for the customer currently. So it would be prudent to remove the particular $count_html
variable.
Would you mind opening a PR for this?
public function addons_menu() {
/* translators*/
$menu_title = sprintf( __( 'Extensions %s', 'classic-commerce' ), $count_html );
add_submenu_page( 'woocommerce', __( 'Classic Commerce extensions', 'classic-commerce' ), $menu_title, 'manage_woocommerce', 'wc-addons', array( $this, 'addons_page' ) );
}
We could merge the variable needed to:
public function addons_menu() {
add_submenu_page( 'woocommerce', __( 'Classic Commerce extensions', 'classic-commerce' ), __( 'Extensions', 'classic-commerce' ), 'manage_woocommerce', 'wc-addons', array( $this, 'addons_page' ) );
}
Will take a stab at it when I get back in from work today.
Describe the bug The removal of
$count_html = WC_Helper_Updater::get_updates_count_html();
from includes/admin/class-wc-admin-menus.php is now throwing a PHP Notice on the dashboard as followNotice: Undefined variable: count_html in C:\Users\zulfn\Desktop\UniServerZ\www\featherlite\wp-content\plugins\classic-commerce\includes\admin\class-wc-admin-menus.php on line 131
To Reproduce Developing locally with
WP_DEBUG
set totrue
To continue developing with the latest version I've commented out line 31 of the same file for now.Expected behavior No PHP Errors, Notices or Warnings should be generated upon plugin activation.
Isolating the problem (mark completed items with an [x]):
ClassicPress Environment