Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter reventor

    (@reventor)

    i guess now we found the problem: OxiPNG. it works also really hard on the squoosh.app, takes about 30 seconds to process this image.

    5000x4000px, 1,59MB with 21% compression to 1.25MB

    I tried also https://caesium.app/ (for comparison) and it took only 5 seconds and compressed to 735 kB (-54%). The desktop app can do it in just 1s, so i guess a browser can not multithread outside of a tab.

    I guess we can close the case, you did a great job with the WP Plugin, its just that the PNG compression algorithm seems to have a problem with high res PNGs.

    Thread Starter reventor

    (@reventor)

    it seems to be a problem with a few large pngs. i tested them on the https://squoosh.app/ but there they worked just fine, both in as browserpng (+32% size) and mozjpeg (-47% size)

    Thread Starter reventor

    (@reventor)

    sorry, updated the link.

    Thread Starter reventor

    (@reventor)

    i would like to but it seems that the compression process completely blocks/crashes the tab and there is no console information. very strange.

    here you can see the problem as a video recording: https://cloud.reventor.eu/s/JCnWGSaZZPD78Rr

    never had such a behavior before. tried it with a completely fresh chrome install too. same behavior.

    • This reply was modified 6 months ago by reventor. Reason: updated link
    Thread Starter reventor

    (@reventor)

    Issue has been found. Now all lines have been imported correctly.
    Solution: When editing the CSV file with LIBREOFFICE or any other Suite recommended by WooCommerce it’s important to define the whole Worksheet as TEXT.

    This step is not mentioned anywhere on the WooCommerce website so i didn’t think it was necessary, but maybe it should be added as an recommendation: https://woocommerce.com/document/product-csv-importer-exporter/#what-csv-editors-do-you-recommend

    We are working with German Language Settings, both in WooCommerce and Windows, so maybe the language settings cause a falsely formatted CSV file. But also changing the language settings to English, with USA regional settings, didn’t make a difference in my test.

    Comparing the working CSV file with the failing one i couldn’t see a difference in NotePad++, but i guess WooCommerce has a certain way of interpreting the file and if not all parameters match, the import fails, even thow it shows as successful in WordPress.

    There is no error message or errolog that would tell the user that something went wrong.

    Thread Starter reventor

    (@reventor)

    That’s precisely the bizarr thing: ID 12202 has not been changed in the CSV, still when import25test.csv gets reimported Woocommerce sets this item to 0 (out of stock).

    This does not happen, when last_part_import.csv gets imported. Both files include the same data, only the top part has been deleted from the file using LibreOffice Calc.

    The only difference i see when opening the CSV files in a text editor is a different use of “” for column descriptions. But WooCommerce labels and previews the correct import values, hence I don’t think this is the issue.

    UTF-8 Formatting etc. remained the same using LibreOffice.
    I also tried editing the CSV with KingOffice and OnlyOffice. Even though the file size was different, the imported result was the same.

    • This reply was modified 2 years, 12 months ago by reventor.
    Thread Starter reventor

    (@reventor)

    Yes I Export the products as usual, open the file in LibreOffice, change the product sales price of ID 12229 to 25.99 and import the file again.

    Then this error occurs. If i import only the very last section of the CSV by deleting a bunch of rows (3rd attachement), the import works fine.

    Thread Starter reventor

    (@reventor)

    We deleted the plugin and reinstalled it, but the error remains the same.

    correction: the update did solve the issue.
    when using booster make sure your php “open base dir” settings are set to “none”.

    The Update did not solve the issue for me.

Viewing 10 replies - 1 through 10 (of 10 total)