You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not the wooCommerce they don't make silly mistakes like Paytm's dumb developers.
I don't think they test it before publishing the release.
There is only one release on GitHub that was in 2020 with no change-log or any explanation and the same with the WordPress releases. You will find absolutely nothing useful in case of any major error like this one. A lot of people are losing customers and sales because of this kind of silly error in the paytm.
To quick fix, the problem Go to class.paytm.php and inside the __construct method uncomment the //$this->title and change to $this-> title = 'some string or leave it empty ' <--- should be line number 27. This will fix the fetal problem that you have.
To quick fix other minor errors
inside the class.paytm.php there is method init_form_fields() and inside this method there is$getPaytmSetting = get_option('woocommerce_paytm_settings'); Which gives bool false if there is no woocommerce_paytm_settings which cause an error on line number 77 $getPaytmSetting['website'] So just add check there $website = !empty($getPaytmSetting) ? $getPaytmSetting['website'] : '';
Another one is in the woo-paytm.php on line number 167$settings = get_option("woocommerce_paytm_settings");
Quick fix if (!empty($settings)) { // paytm enabled and order is exists with paym_order_data if ($settings['enabled'] == 'yes' && !empty($results)) { add_meta_box( '_paytm_response_table', __('Paytm Payments'), '_paytm_response_table', 'shop_order', 'normal', 'default', array('results' => $results) ); } }
Hope that fixes the problems and your site will be up and running.
And paytm developers you should test everything thoroughly before releasing it.
After updating with Woocommerce to 6.6.0, i had this error.
Am able to use it after downgrading to 6.5.1
Not sure if it's Paytm plugin or Woo
Please look into it.
The text was updated successfully, but these errors were encountered: