Forum Replies Created
-
Hi,
I understand this solution but this does not fix the above problem.
This only removes the ‘outdated message’ and does not upgrade changes from the core woocommerce to the theme right?For example I still have double custom fields…
Regards,
Michielin reply to: Outdated woocommerce files in Theme?Great news, thank you for the quick reply.
Will you also be including the “accept policy” checkbox on the checkout page as an addition to the accept T&C checkbox?This is also part of the new GDPR requirements.
Regards,
MichielHi Junnie, you are checking the wrong site… Alexiefa is from a different site.
I do not have that problem.
Gr. Michiel
in reply to: Compatibility problems Woocommerce 3.0 >Hi, still the deprecated functional is called from the payment page. I’m trying to find the code as well but I cannot find it.
So the error is still there…
in reply to: Get Country depricated functionThis reply has been marked as private.in reply to: Get Country depricated functionThis reply has been marked as private.in reply to: Compatibility problems Woocommerce 3.0 >This reply has been marked as private.in reply to: Compatibility problems Woocommerce 3.0 >I have downloaded the files, updated the theme by uploading it via FTP.
But the version number of the theme has not been updated, it still says 1.1.30.And I still have the above errors in our log.
Normally Envato Market is showing an update of the DMCS theme and I can easily update – now it seems to be more of a struggle…
Regards,
Michielin reply to: Compatibility problems Woocommerce 3.0 >Then probably the most stupid question of today, how do I update?
Normally a new theme update appears in wordpress and I can easily update.
I’m not sure how to update with files only that I can download from Themeforrest?Sorry for asking.
Regards,
Michielin reply to: Compatibility problems Woocommerce 3.0 >Hi,
Our theme is already up to date? There appear no new updates from theme-updates.
Regards,
Michielin reply to: Compatibility problems Woocommerce 3.0 >Thank you for the support, I really appreciate your help.
If I look at the log after the time you’ve sent the reply that you’ve fixed it.The below 2 errors still appeared:
[Tue Aug 22 18:27:01.170894 2017] [proxy_fcgi:error] [pid 455:tid 139646885394176] [client 62.140.132.25:19953] AH01071: Got error ‘PHP message: The WC_Customer::get_country function is deprecated since version 3.0. Replace with WC_Customer::get_billing_country.\n’, referer: https://www.klerenmakendebaby.nl/afrekenen/
[Tue Aug 22 18:28:00.510957 2017] [proxy_fcgi:error] [pid 455:tid 139646696576768] [client 62.140.132.25:12473] AH01071: Got error ‘PHP message: The WC_Customer::get_country function is deprecated since version 3.0. Replace with WC_Customer::get_billing_country.\nPHP message: The WC_Customer::get_country function is deprecated since version 3.0. Replace with WC_Customer::get_billing_country.\nPHP message: The WC_Customer::get_country function is deprecated since version 3.0. Replace with WC_Customer::get_billing_country.\nPHP message: The woocommerce_clean function is deprecated since version 3.0. Replace with wc_clean.\nPHP message: The woocommerce_clean function is deprecated since version 3.0. Replace with wc_clean.\nPHP message: The woocommerce_clean function is deprecated since version 3.0. Replace with wc_clean.\nPHP message: The woocommerce_clean function is deprecated since version 3.0. Replace with wc_clean.\nPHP message: billing_phone was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_address_1 was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: shipping_address_1 was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: id was called incorrectly. Producteigenschappen mogen niet rechtstreeks aangeroepen worden. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: order_discount was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: order_shipping was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_city was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_country was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_postcode was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_email was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_first_name was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_Afterpay_Default->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.\nPHP message: billing_last_name was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_use
Regards,
Michielin reply to: Compatibility problems Woocommerce 3.0 >This reply has been marked as private.in reply to: Compatibility problems Woocommerce 3.0 >This reply has been marked as private.in reply to: Compatibility problems Woocommerce 3.0 >I can provide access again, but with every update of Woocommerce new deprecated issues appear. When will there be an update of the theme that will solve most of them and we can continue from there?
Regards,
Michielin reply to: Compatibility problems Woocommerce 3.0 >This reply has been marked as private.in reply to: Get_product & _get_product_schema depricated funtion
