database going back to 2.5.5 after 2..6.x update

  • rajackar

    (@rajackar)


    7 years, 9 months ago

    Hi,

    I was using version 2.5.5 on my wp site without issue.
    I updated to 2.6 and after that the checkout now fails. When this happens all sessions to the wordpress site are reset and when I check system status for the plugin it now says 2.5.5 even though is said 2.6.x before. From that moment on I also get a notification that my database needs to be upgraded. This happens even if I install 2.6.x directly. Tested with 2.6.1 and 2.6.2 too and it makes no difference. I deleted the plugin using the setting under tools that wipes all data and reïnstalled. This however makes no difference. I also tried a wipe and reinstall after disabling all other plugins and I still have the same problem.
    Any help here would be greatly appreciated. Please let me know what other info is needed.
    Thanks!

    https://wordpress.org/plugins/woocommerce/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter rajackar

    (@rajackar)

    7 years, 9 months ago

    `WordPress Environment
    Home URL: http://www.grindpad.com
    Site URL: http://www.grindpad.com
    WC Version: 2.6.2
    Log Directory Writable: /home/kruijf22/domains/grindpad.com/public_html/wp-content/uploads/wc-logs/
    WP Version: 4.5.3
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode:
    WP Cron:
    Language: en_US
    Server Environment
    Server Info: Apache
    PHP Version: 5.6.22
    PHP Post Max Size: 8 MB
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    cURL Version: 7.36.0, OpenSSL/1.0.1e
    SUHOSIN Installed: –
    Max Upload Size: 2 MB
    Default Timezone is UTC:
    fsockopen/cURL:
    SoapClient:
    DOMDocument:
    GZip:
    Multibyte String:
    Remote Post:
    Remote Get:
    Database
    WC Database Version: 2.5.5
    woocommerce_sessions
    woocommerce_api_keys
    woocommerce_attribute_taxonomies
    woocommerce_downloadable_product_permissions
    woocommerce_order_items
    woocommerce_order_itemmeta
    woocommerce_tax_rates
    woocommerce_tax_rate_locations
    woocommerce_shipping_zones
    woocommerce_shipping_zone_locations
    woocommerce_shipping_zone_methods
    woocommerce_payment_tokens
    woocommerce_payment_tokenmeta
    MaxMind GeoIP Database: /home/kruijf22/domains/grindpad.com/public_html/wp-content/uploads/GeoIP.dat
    Active Plugins (2)
    WooCommerce PayPal Express Checkout Gateway by Automattic/WooCommerce – 1.0.4
    WooCommerce by WooThemes – 2.6.2
    Settings
    Force SSL: –
    Currency EUR (€)
    Currency Position left
    Thousand Separator ,
    Decimal Separator .
    Number of Decimals 2
    API
    API Enabled:
    WC Pages
    Shop Base: #450 – /shop/
    Cart: #402 – /cart/
    Checkout: #403 – /checkout/
    My Account: #404 – /my-account/
    Taxonomies
    Product Types: external (external), grouped (grouped), simple (simple), variable (variable)
    Theme
    Name: Twenty Eleven
    Version: 2.4
    Author URL: https://wordpress.org/
    Child Theme: – If you’re modifying WooCommerce on a parent theme you didn’t build personally, then we recommend using a child theme. See: How to create a child theme
    WooCommerce Support:
    Templates
    Overrides: –’

    Plugin Contributor Claudio Sanches

    (@claudiosanches)

    7 years, 9 months ago

    You need to run the updater, but something can goes wrong.
    Try to update, wait for while and go to WooCommerce > System Status > Logs and select the wc_db_updates-* file. Show me here what you find in this log file, so we can see what is going wrong for you.

    Thread Starter rajackar

    (@rajackar)

    7 years, 9 months ago

    I’ll check the log but please note that I’ve completely removed woocommerce from my site using the option in the tools and directly installed the latest version. I’m guessing the DB updater is not needed then. Is that correct?

    Plugin Contributor Claudio Sanches

    (@claudiosanches)

    7 years, 9 months ago

    @rajackar not sure if you removed completely, if removed should display the correct version.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘database going back to 2.5.5 after 2..6.x update’ is closed to new replies.