• Resolved Kian William

    (@kianwilliam)


    To whom it may concern:
    In wp-admin, I received a message to update woocommerce db in background, I clicked the button and stuff updated all. Yet later when I checked additional css under customize ,
    Some attributes updated to its older values, for instance before update I set url path of each background image as: background:url(./the path);, after launch I changed it to: background:url(websiteurl/the path). After woocommerce update it changed to its original: background:url(./the path) again. additional css data are kept in a separate table, does update of woocommerce db involves updating the complete database or just tables in connection with woocommerce?
    Kian William

Viewing 7 replies - 1 through 7 (of 7 total)
  • corsonr

    (@corsonr)

    Automattic Happiness Engineer

    Hi Kian,

    The database update is supposed to update the database format, not it’s content. There might be a glitch somewhere if that’s the case. If you, I’d suggest getting a version of the site/db before you updated it, and use it as a test site, to perform the update again, but this time with all addons disabled and with a default theme. If that still occurs, it means that something is wrong on our side, if that works it will mean that the issue is on your install and that it’s most likely a conflict.

    Thread Starter Kian William

    (@kianwilliam)

    Greetings,
    I have the site on my local server too and I shall test it. Thanks for the advice.
    Why woocommerce should update database format? And what do you mean by database format?
    Logic tells that the plugin should get involved with related tables of its own in case of any sort of woocommerce database update and makes its tables compatable with database in all aspects rather than interfere in the complete database which rules on all tables belong to all plugins
    Kian William

    Plugin Support mouli a11n

    (@mouli)

    @kianwilliam
    Generally the database updates might reorganize data but should not change the data itself. Sometimes, to increase efficiency, data is moved to new tables etc.
    In your case it appears that data is getting changed which is unlikely to be the result of a database update directly. Its more likely to be the result of a plugin or conflict between two plugins.
    Good luck with your testing, let us know how you get on.

    Thread Starter Kian William

    (@kianwilliam)

    1-“Generally the database updates might reorganize data”
    Under what circumstance database update reorganize data and what you mean by the word reorganization of data in a database?
    2-“Sometimes, to increase efficiency, data is moved to new tables ”
    when you say new tables you mean updating woocommerce could create new tables for other plugins or just woocommerce itself? and in both case why it does not update tables which could be handled with better performance and software engineering?
    ” Its more likely to be the result of a plugin or conflict between two plugins”
    This is possible but I did not view it on my local server
    Kian William

    Plugin Support mouli a11n

    (@mouli)

    @kianwilliam

    1. By this I mean that sometimes data is moved to new tables. For example, recently it was decided that moving a lot of product data to a product_meta_lookup table would make for greater efficiency in searching
    2. Updating WooCommerce will only update tables relating to WooCommerce. However if other plugins need to access these databases they might need to update their table references which is why it is important to update plugins as well.
    3.I suggest that you try a conflict test as follows:

    1. Temporarily switch your theme back to the Storefront (https://www.woocommerce.com/storefront/) or TwentyNineteen (https://www.ads-software.com/themes/twentynineteen/) Theme.
    2. Disable all plugins except for WooCommerce.
    3. Test to see if the issue has been resolved.

    If that resolves the issue, then one-by-one you can switch back your theme and re-enable your plugins, testing in between, until you find the one causing the conflict.

    I hope that helps you to figure it out.
    Feel free to get back to us if you have further questions.

    Thread Starter Kian William

    (@kianwilliam)

    1- I found the table wp_wc_product_meta_lookup in the database, then this table was not in the original package of woocommerce and in update it is added, responded completely
    2- Responded completely
    3- Yes this is a way to find the conflict between plugins , also error log could sometimes mention valuable hints
    Thanks for the support
    Kian William

    Thread Starter Kian William

    (@kianwilliam)

    Just one last thing, you said:
    “Generally the database updates might reorganize data but should not change the data itself. Sometimes, to increase efficiency, data is moved to new tables etc.”
    “By this I mean that sometimes data is moved to new tables. For example, recently it was decided that moving a lot of product data to a product_meta_lookup table would make for greater efficiency in searching”

    I also searched through the zip file, I mean the original woocommerce zip file before getting updated and I observed lots of queries to this table (product_meta_lookup) which proves this table was not added in the update of woocommerce and it was there originally, the zip file I downloaded belongs to 2020/4/20 and it is not recent time at all and the version of woocommerce is 4.0.1
    I only want to form a response based on logic and I do not find your response logical or may be there are other explanations
    Kian William

    • This reply was modified 3 years, 11 months ago by Kian William.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Update woocommerce database message’ is closed to new replies.