WC Vendors 2.0 and WC Vendors 1.5.0 Released

by

After about 3 weeks of delays they’re finally here! WC Vendors 2.0 was released today to WordPress.org along with WC Vendors Pro 1.5.0 via the my-account page. There are a lot of changes in both WC Vendors and WC Vendors Pro that will require that you do thorough testing on your staging server before updating to this latest release on your live website. There are a lot of internal changes so if you have any plugins or themes that were build for WC Vendors there is a chance that you may face issues until the developers catch up.

DO NOT BLINDLY UPDATE YOUR SITE.

Backups

Please be sure to make a complete backup of your site before continuing any upgrades.

How to Upgrade ?

WC Vendors

If you’re a user of only WC Vendors then your upgrade path is quite simple. After testing you can simply update the plugin via the plugins screen after the update is shown as available. You can read the complete upgrade guide for WC Vendors here.

https://docs.wcvendors.com/knowledge-base/upgrading-to-wc-vendors-2-0/

Please Note: Deactivate WC Vendors Pro BEFORE updating WC Vendors.

WC Vendors Pro

If you’re a WC Vendors Pro user than your upgrade path requires a few extra steps. This is because of the incompatibility of WC Vendors 2.0 and WC Vendors 1.4.6. You will have to manually upgrade WC Vendors Pro for this release. To ensure that your site doesn’t have any fatal errors on activation of WC Vendors it will disable WC Vendors Pro if it detects a version below 1.5.0. I’ve just finished a help document to outline how to perform this upgrade.

https://docs.wcvendors.com/knowledge-base/upgrading-to-wc-vendors-pro-1-5-0/

Questions or Feedback?

If you’ve got any questions please feel free to post them in the comments. If its related to WC Vendors Free you can also use our support forums on WordPress.org and if its related to WC Vendors Pro and you’ve got an active support license, create a ticket and we’ll be sure to help you as soon as we can.

 

11 thoughts on “WC Vendors 2.0 and WC Vendors 1.5.0 Released”

  1. Hi
    Quick question
    In which order do I update
    1 – WCV 2.0 first then Pro 1.5
    Or
    2 – Pro 1.5 then WCv 2.0
    The 2 x Docs state what to do for each update but not in which order

  2. Apologies, My mistake – I missed
    ‘Please ensure that you are running the latest version of WC Vendors 2.0 and above before performing these steps.’
    Doh
    So WCV 2.0 1st, Then 1.5 Pro

  3. Well too late. The update was available and I blindly launched it, no warning attached to the update. You need to be on your site to realized what you needed to do before. Kid of counter productive?
    Now the site has crashed with a fatal error and a result. What to do? solutions?

    Fatal error: Uncaught Error: Call to a member function get_option() on null in /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-content/plugins/wc-vendors-pro/includes/class-wcvendors-pro.php:1402 Stack trace: #0 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-content/plugins/wc-vendors-pro/admin/class-wcvendors-pro-admin.php(162): WCVendors_Pro::get_option(‘disable_wp_admi…’) #1 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-includes/class-wp-hook.php(286): WCVendors_Pro_Admin->admin_lockout(”) #2 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #3 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #4 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-settings.php(450): do_action(‘init’) #5 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-config.php(80): require_once(‘/nfs/c04/h07/mn…’) #6 /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-load.php(37): require_once(‘/nfs/c04/h07/mn.. in /nfs/c04/h07/mnt/63597/domains/jmamuse.com/html/wp-content/plugins/wc-vendors-pro/includes/class-wcvendors-pro.php on line 1402

    • Some code I added in free that should have disabled WC Vendors Pro if 1.4.6 is enabled doesn’t seem to be firing. I’ve almost fixed this issue but in the mean time, you’ll need to rename the wc-vendors-pro folder via FTP. That’ll get your site responding again. Then you can run the WC Vendors 2.0 Update. Once this is completed you can download WC Vendors Pro 1.5.0 and upload this to your site, then activate and run the update prompt.

  4. Hi , Quick question. How long does the update prompt take to complete? I have updated wc vendors than wc vendors pro and it has been running the data update for over an hour.

    Thank you!

  5. Hi, My upgrade button is still stuck. I click “Run the Update”, the screen changes and the message goes to “WC Vendors data update – Your database is being updated in the background. Taking a while? Click here to run it now.”. I wait for 2 minutes, nothing happens. I click “Save changes” button, the screen is refreshed and…. the button is back there. As recommended, pro is disabled. I disabled before the update.

    The only thing I have in apache’s error.log is:

    [Sat May 19 14:55:19.319897 2018] [:error] [pid 18643] [client 173.71.97.201:50427] PHP Warning: include(../../../../wp-load.php): failed to open stream: No such file or directory in /var/www/devservmkt.consultingquest.co/public_html/wp-content/plugins/bp-custom.php on line 8, referer: https://devservmkt.consultingquest.co/wp-admin/admin.php?page=wc-settings&tab=email
    [Sat May 19 14:55:19.319945 2018] [:error] [pid 18643] [client 173.71.97.201:50427] PHP Warning: include(): Failed opening ‘../../../../wp-load.php’ for inclusion (include_path=’.:/usr/share/php’) in /var/www/devservmkt.consultingquest.co/public_html/wp-content/plugins/bp-custom.php on line 8, referer: https://devservmkt.consultingquest.co/wp-admin/admin.php?page=wc-settings&tab=email
    [Sat May 19 14:55:20.241141 2018] [:error] [pid 18766] [client 173.71.97.201:50428] PHP Warning: include(../../../../wp-load.php): failed to open stream: No such file or directory in /var/www/devservmkt.consultingquest.co/public_html/wp-content/plugins/bp-custom.php on line 8, referer: https://devservmkt.consultingquest.co/wp-admin/admin.php?page=wcv-settings&do_update_wcvendors=true
    [Sat May 19 14:55:20.241196 2018] [:error] [pid 18766] [client 173.71.97.201:50428] PHP Warning: include(): Failed opening ‘../../../../wp-load.php’ for inclusion (include_path=’.:/usr/share/php’) in /var/www/devservmkt.consultingquest.co/public_html/wp-content/plugins/bp-custom.php on line 8, referer: https://devservmkt.consultingquest.co/wp-admin/admin.php?page=wcv-settings&do_update_wcvendors=true
    [Sat May 19 14:55:20.281694 2018] [:error] [pid 18650] [client 173.71.97.201:50432] PHP Warning: include(../../../../wp-load.php): failed to open stream: No such file or directory in /var/www/devservmkt.consultingquest.co/public_html/wp-content/plugins/bp-custom.php on line 8, referer: https://devservmkt.consultingquest.co/wp-admin/admin.php?page=wcv-settings&do_update_wcvendors=true

    Thank you.

    Daniel

    • Hello,

      The upgrade has completed, there is a bug that I’m working on that will stop the dialog box from disappearing. I hope to have a fix to this released today.

      thanks

  6. I’ve tracked down the issue with this “WC Vendors Update Required. – We need to upgrade your configuration to the latest version.” message from continually appearing after running the updater.

    Seems that the version number in the database for wc_vendors [wcvendors_db_version under the ‘wp-options’ table] is being saved as 2.0.3 but should be saving as 2.0.4 (as this is the latest version #) and manually changing it to this will fix the issue.

    The issue stems from this update_notice function in the /classes/admin/class-wcv-admin-notices.php file where it checks the wcvendors_db_version string: if ( version_compare( get_option( ‘wcvendors_db_version’ ), WCV_VERSION, ‘<' ) ) {

    And the update_db_version function in the /classes/class-install.php file seems to be where it is saving the wcvendors_db_version after the update, but alas is saving with an older version # than the most recent plugin version number.

    So to fix, just manually edit the wcvendors_db_version record under the wp_options table in your WordPress database and change it to match that of the latest version of the plugin (ie: change from 2.0.3 to 2.0.4); The upgrade notice will disappear after this change and refreshing the page.

    Hope this helps.

    • Hello,

      Thanks for your debugging work! I managed to fix this issue yesterday and will be releasing an update today that includes this fix.

      cheers,

      Jamie

Comments are closed.