4.1 update issues
-
The plugin is automatically deactivated on update to version 4.x. Nothing wrong with that. Just activate it again and it will continue working well.
If you have other issues related to the latest update please post them below.
https://www.ads-software.com/plugins/weight-based-shipping-for-woocommerce/
-
Hi there,
I have just updated all plugins and also WP to WP 4.4.1.
I noticed that Weight Based Shipping was deactivated and so went to reactivate it. But I then noticed that it no longer seems to be compatible with Woothemes Role Based Methods plugin. I was using combination of yours and theirs to create certain shipping methods for logged in users (‘customer’ role) and different ones for ‘guest’ users.
The bug seems to be when I try to assign the methods that I have created using your plugin in their plugin settings to a user role, it doesn’t save and the checkbox is unchecked after refreshing. I can send you a screenshot if you can let me know where to send it if that helps? I tried checking a few of the other checkbox for the standard methods and they worked fine.
Also, I don’t know if this helps. But I noticed the ID under Woocommerce, Settings, Shipping, Shipping Methods seems to have changed from.
” WC_Weight_Based_Shipping_main ” to just ” main “
Do you have any idea what this could be?
Really looking forward to hearing from you and thanks in advance!
Ralph
Hi there,
I’ve done a bit more research into this so wanted to let you know what I’ve found.
I reverted back to before I updated to WP 4.4.1 and all plugins and just updated yours. I still then found that after your plugin updated it was deactivated. I then reactivated it and checked the settings in Role Based Methods which were lost on the methods I had created with your plugin. I tried resaving them but again the settings weren’t being saved.
I am running Role Based Methods 2.0.8 (latest version) and can see in their changelog the below which looks as though it could be connected as they have recently added more validation to the settings page.
2015.10.27 – version 2.0.8
* Adding in wc_clean for additional sanitization.2015.04.28 – version 2.0.7
* Settings update sanitizationWhat I also found that was interesting is that I have create two methods with your plugin. The first one with the ID of ” main ” ( formally ” WC_Weight_Based_Shipping_main ” before the update ) does actually save when saving it on its own or with some of the other methods. However when saving the settings with the second shipping method I created with your plugin the whole form fails validation and so the settings aren’t saved. I also tried just saving the second method on its own but it failed validation again.
The second shipping method had an ID of ” WC_Weight_Based_Shipping_1407310776 ” before I updated it and is now just ” 1407310776 “
To sum up it seems to be failing validation only when the second method is trying to be used in the settings. I think this might have something to do with the ID as it only accepts the first one but you’ll know better than me!
Cheers
Ralph
Hi,
Thanks for details.
Unfortunately, it’s hard to say what’s going wrong without the Role Based Methods plugin. What I’d suggest to do is to reset its settings somehow. There should be rows in the wp_options table related to the plugin, try to delete them. It seems the plugin refers to obsolete WBS rule ids which were renamed during update to 4.1.1, and fails on settings save due to that.
Another way is to temporary roll back to previous plugin versions including WBS and RBM, and delete references to WBS rules from RBM’s settings.
Hi Dan,
Thanks very much for your helpful response, much appreciated.
I tried deactivating and delete RBS to delete all data. Which seemed to reset the settings as when re-uploading and reactivating the settings seemed to be back to the default ones. However this did not fix the issue.
I also look into the RBS code and saw a couple of options being set as below.
update_option( ‘woocommerce_shipping_roles’,
update_option( ‘woocommerce_role_methods_options’,
However when searching for “woocommerce_shipping_roles” or “woocommerce_role_methods_options” in wp_options I could not find them at all. Also when doing a var_export($options) after it does a get_option before serving up the page it returns false. However still manages to save and show the other settings that are set. Weird.
I tried creating a duplicate Shipping method in your plugin which would obviously have a new ID but that didn’t work either.
I have emailed woothemes in the hope of some support! Not quite sure where to go from here.
Thanks for your help. I you have any further thoughts it would be much appreciated!
Cheers
Ralph
Hi Ralph,
Could you check if WBS works after deactivating RBS?
Hi Dan,
Sorry for the delay getting back to you.
I’ve just tested it and yes it does, perfectly. I guess that means it might be something wrong with RBS? I’ve had a response from them saying that they can not help with third party integration.
It’s odd that it saves the first method that I created with your plugin with the ID of “main” but not the one with the ID of “1453107824”. It doesn’t give any error message either it just says “Settings Saved”.
Do you have any further suggestions by any chance?
Cheers
Ralph
Yep, seems so. Could you share RBS so I can try to figure out what’s happening there?
Hi Dan,
That would be great if you don’t mind. I can’t make it publicly available as Woothemes wouldn’t be too happy but I can give you login details to the staging site which you may be able to debug on? You’re welcome to take a backup if you’d prefer to debug on your local.
Can you give me an email address or a way I can send you login info privately?
Please send me a plugin backup then, to dan at gravyzzap dot com. It would be easier to debug it on my local staging.
Do you know when en why the plugin was deactivated, today a customer warned me that she could not order on one of my webshops.
So i checked all my webshops and found the plugin was deactivated in all my shops.Plugin deactivates on update to 4.x version from a pre-4.x one. The reason is main/entry plugin file rename in the new version.
That could be an issue if only you update your plugins automatically, without testing changes after that. Is that the case?
A workaround for issue with Role Based Methods: https://www.ads-software.com/support/topic/compatibility-with-woocommerce-role-based-methods.
Hi Dan,
I have just re-activated the plugin but am having some difficulty opening the settings. I am getting this message when I try to open:
Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘WbsProgressiveRate: invalid argument value(s): ”9.95”, ”0-20”, ‘0’.’ in /websites/123reg/LinuxPackage21/pe/el/ab/peelableprotectivecoatings.co.uk/public_html/PeeCO/wp-content/plugins/weight-based-shipping-for-woocommerce/Model/WbsProgressiveRate.php:11 Stack trace: #0 /websites/123reg/LinuxPackage21/pe/el/ab/peelableprotectivecoatings.co.uk/public_html/PeeCO/wp-content/plugins/weight-based-shipping-for-woocommerce/Model/WbsProgressiveRate.php(28): WbsProgressiveRate->__construct(‘9.95’, ‘0-20’, NULL) #1 /websites/123reg/LinuxPackage21/pe/el/ab/peelableprotectivecoatings.co.uk/public_html/PeeCO/wp-content/plugins/weight-based-shipping-for-woocommerce/WC_Weight_Based_Shipping.php(471): WbsProgressiveRate::fromArray(Array) #2 /websites/123reg/LinuxPackage21/pe/el/ab/peelableprotectivecoatings.co.uk/public_html/PeeCO/wp-content/plugins/weight-based-shipping-for-woocommerce/WC_Weight_Based_Shipping.php(46): WC_Weight_Based_Shipping->init() #3 /website in /websites/123reg/LinuxPackage21/pe/el/ab/peelableprotectivecoatings.co.uk/public_html/PeeCO/wp-content/plugins/weight-based-shipping-for-woocommerce/Model/WbsProgressiveRate.php on line 11
I am not a webdesigner, I just thought I may be able to design a website myself so any help in laymans terms will be very appreciated
regards
PaulHi Paul,
According to the error message you have invalid data in the plugin settings. That ‘0-20’ value is supposed to be a decimal weight step value.
You can either remove plugin data from your database manually and confiure it from scratch, or use the paid plugin version which would allow you to fix the settings.
- The topic ‘4.1 update issues’ is closed to new replies.