Forum Replies Created

Viewing 15 replies - 61 through 75 (of 120 total)
  • Thread Starter DensitySK

    (@densitysk)

    Woocommerce support has responded with the following

    Our developers did come back to us regarding your issue and this was what was mentioned:
    ? When calculating the bundled item discounts, Product Bundles uses the wc_get_rounding_precision() core function to decide how many decimals to use in the calculation. According to the function’s documentation
    ? So, if your price precision is set to 2 digits in the WooCommerce settings, this function will use 4 digits for calculation.

    They have also asked the following>
    Our developers are asking following information to point you in the right direction:
    ? Do you get 2-digit bundled item prices when you use a 2-digit discount? Is this an approach you would consider following?

    I have tried it and have seen some changes, but the FEED output was still too long

    Using bundle component discount with two decimals still does not fixes the issue and the bundle products still output XML data incorrectly without respecting the rounding. 
    
    So when the bundle component discount had 4 decimals
    
    The XML output was this
    <item>
    <g:id>2255</g:id>
    <g:availability>in stock</g:availability>
    <g:condition>New</g:condition>
    <g:price>EUR 85,000029</g:price>
    <g:brand>Linkup,Sliger Designs</g:brand>
    <g:google_product_category>296</g:google_product_category>
    <g:shipping_weight>0.14</g:shipping_weight>
    <g:identifier_exists>yes</g:identifier_exists>
    </item>
    
    When I use only 2 decimals in bundle component discount the output is still too long
    
    <item>
    <g:id>2255</g:id>
    <g:availability>in stock</g:availability>
    <g:condition>New</g:condition>
    <g:price>EUR 85,0031</g:price>
    <g:brand>Linkup,Sliger Designs</g:brand>
    <g:google_product_category>296</g:google_product_category>
    <g:shipping_weight>0.14</g:shipping_weight>
    <g:identifier_exists>yes</g:identifier_exists>
    </item>
    Thread Starter DensitySK

    (@densitysk)

    tried and it is not working. I have created a copy and tried to create the first feed, but it is simply stuck in processing at 0%. Caching is disabled and I have followed your tutorial here:
    https://adtribes.io/help-my-feed-processing-is-stuck/

    I have found out, that as soon as I try to refresh any product feed, I get a fatal errors in my logs:

    2022-03-22T14:33:08+00:00 CRITICAL Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php:2939
    Stack trace:
    #0 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php(2939): round('', 2)
    #1 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(4556): WooSEA_Get_Products->woosea_get_products(Array)
    #2 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-content/plugins/woo-product-feed-pro/woocommerce-sea.php(2189): woosea_continue_batch('eCrcNfm5tJrmgFV...')
    #3 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-includes/class-wp-hook.php(307): woosea_project_refresh('')
    #4 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
    #5 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
    #6 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-admin/admin-ajax.php(187): do_action('wp_ajax_woosea_...')
    #7 {main}
      thrown in /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/xxxxxx/web/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 2939
    Thread Starter DensitySK

    (@densitysk)

    Not yet. i can give it a try. But I have had this issue in general with refreshing the feed. Even when I disable my caching plugin completely. Not sure why that is.

    Thread Starter DensitySK

    (@densitysk)

    Hi,

    Kindly check below:

    Screenshot of the product edit page of your component product?

    https://ibb.co/vjSjV8X
    https://ibb.co/0yLmV0r
    https://ibb.co/9gHxzDg
    https://ibb.co/85S4xT2
    https://ibb.co/FwMT5wM
    https://ibb.co/LRK0kQC

    Screenshot of the product edit pages (prices) of the products that are part of the component product?
    Individual components are bundles made out of simple products. These components are priced individually and do not have any discount applied.

    https://ibb.co/FBMjDFf
    https://ibb.co/JtrSW2Q
    https://ibb.co/3BF5MKD
    https://ibb.co/Dp8cPPP
    https://ibb.co/TL6H3s0

    The field mapping you are using for your feed?
    https://ibb.co/bPc5dZc

    I hope it helps.

    Thread Starter DensitySK

    (@densitysk)

    Hi,

    I have noticed it and have already updated. But the weird decimals are still there. I tried to manually refresh the product feed multiple times as well as disabled caching plugin, but the feed still includes those

    <item>
    <g:id>2255</g:id>
    <g:availability>in stock</g:availability>
    <g:condition>New</g:condition>
    <g:price>EUR 85,000029</g:price>
    <g:brand>Linkup,Sliger Designs</g:brand>
    <g:google_product_category>296</g:google_product_category>
    <g:shipping_weight>0.14</g:shipping_weight>
    <g:identifier_exists>yes</g:identifier_exists>
    </item>
    Thread Starter DensitySK

    (@densitysk)

    HI,

    unfortunately woocommerce is very unwilling to help in this and insists that the issue is with the feed export plugin. Would you be able to check for a possible future fix?

    Thread Starter DensitySK

    (@densitysk)

    HI,

    Are you perhaps using another 3th party plugin that does things with sale / discount prices that could be causing this?
    No – I do not use any kind of plugin that could affect the price calculation or similar.
    Here is the screenshot of plugins that I use if that can help you: https://ibb.co/sH68s96

    Can you share with us screenshots of your WooCommerce decimal settings configuration and screenshots of the product edit pages of the above bundled product so we can try reproducing everything at our end?
    Here is the screenshot of the decimal settings
    https://ibb.co/K6LmShk
    Here is the link to an example product where the price has correct 2 decimals on the website:
    https://www.density.sk/product/standard-pci-e-3-0-riser-cable-with-bracket-v2/

    Here is the link to the product settings in the backend:
    https://ibb.co/mrjTkHs

    Here is the excerpt from the Facebook Feed with the incorrect price with a lot of decimals

    <item>
    <g:id>2253</g:id>
    <g:availability>in stock</g:availability>
    <g:condition>New</g:condition>
    <g:description>ADT-Link PCIe 3.0 16x riser cable V2 in 23cm length, improved shielding and mounting bracket</g:description>
    <g:image_link>https://www.density.sk/wp-content/uploads/R33SL-23CM-Gen3-Standard-Bracket-Riser-Cable-2.jpg</g:image_link>
    <g:link>https://www.density.sk/product/standard-pci-e-3-0-riser-cable-with-bracket-v2/?utm_source=Facebook Catalog Feed / Instagram&utm_campaign=Facebook Feed&utm_medium=cpc&utm_term=2253</g:link>
    <g:title>Standard PCIe 3.0 Riser Cable with Bracket V2</g:title>
    <g:price>EUR 29,000015</g:price>
    <g:brand>ADT-Link,Sliger Designs</g:brand>
    <g:google_product_category>296</g:google_product_category>
    <g:mpn>PCIE-SINGLE-GEN3-V2</g:mpn>
    <g:shipping_weight>0.14</g:shipping_weight>
    <g:identifier_exists>yes</g:identifier_exists>
    </item>

    A screenshot of your field mapping page
    Screenshot of field mapping for facebook feed https://ibb.co/g78jHxQ

    Here is also the screenshot from Facebook Commerce manager with related visible error https://ibb.co/7NB8jBj

    • This reply was modified 2 years, 11 months ago by DensitySK.
    Thread Starter DensitySK

    (@densitysk)

    I have contacted the Woocommerce support and they have confirmed, that it should not be related to their bundle product plugin. The product bundle plugins generate a price with decimals based on the woocommerce settings. Even if I export the product data in a regular CSV file (i.e. I export orders with these products, etc) than they always have a price with two decimal spaces as set in the woocommerce settings. Therefore please check again. Here the answer from Woocommerce:

    Things we’ve tested:
    During the chat we tried to export the products in a CSV file however, you mentioned that your issue was with the XML format.
    Also, you shared the link to your conversation with the developers of Product Feed PRO for WooCommerce here: https://www.ads-software.com/support/topic/change-decimal-separator-2/
    After the chat, I forwarded your question to our developers and they got back to me with the following answer:
    Product Bundles doesn’t include any code that determines how many decimals should be used in an XML context.
    In general, Product Bundles falls back to the WooCommerce core decimal precision settings: https://d.pr/i/BqidA4. From the data they shared, I understand that all decimals show up in the XML export. So, there is a high chance that the plugin used to do this export, doesn’t respect the WooCommerce core settings and uses its own decimal precision settings.
    Next steps:
    As Product Bundles just respects the rules set by the core WooCommerce Decimal settings I’d suggest checking whether something is overwriting that setting. Possibly another plugin.
    Finally, please forward this information to the developers of Product Feed PRO for WooCommerce so that they can further test this issue.

    • This reply was modified 2 years, 11 months ago by Jan Dembowski. Reason: Formatting
    Thread Starter DensitySK

    (@densitysk)

    no, I did not try it yet (did not wanted to do trial and error). But I have already found a different plugin that works out of the box. Therefore closing this thread. Thank you.

    Thread Starter DensitySK

    (@densitysk)

    after checking, your plugin still shows fatal errors all over again. It has been purged from the website and database completely and still after installing it again now I start to see the same fatal errors again.

    There were no database or backup restorations, migrations, or any kind of switch to a different theme.

    2022-01-22T10:57:48+00:00 CRITICAL Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, array given in /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woo-backorder-manager-pro/woo-backorder-manager-pro.php:669
    Stack trace:
    #0 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woo-backorder-manager-pro/woo-backorder-manager-pro.php(669): strpos(Array, '%available%')
    #1 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-includes/class-wp-hook.php(303): WooBackorderManagerPro->wcbm_get_availability_text('', Object(WC_Product_Variable))
    #2 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-includes/plugin.php(189): WP_Hook->apply_filters('', Array)
    #3 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-product.php(2082): apply_filters('woocommerce_get...', '', Object(WC_Product_Variable))
    #4 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-product.php(2058): WC_Product->get_availability_text()
    #5 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woocommerce/includes/wc-template-functions.php(3515): WC_Product->get_availability()
    #6 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/et-core-plugin/app/models/customizer/class-ajax-search.php(313): wc_get_stock_html(Object(WC_Product_Variable))
    #7 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-includes/class-wp-hook.php(303): Etheme_ajax_search->search_results('')
    #8 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
    #9 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
    #10 /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-admin/admin-ajax.php(202): do_action('wp_ajax_nopriv_...')
    #11 {main}
      thrown in /data/f/c/fc2fe6bd-5916-44b4-b9c0-13c5319e4e79/XXXXX/web/wp-content/plugins/woo-backorder-manager-pro/woo-backorder-manager-pro.php on line 669
    Thread Starter DensitySK

    (@densitysk)

    thank you. I have removed the database rows and reinstalled the plugin. I will now wait for the next orders with backordered items and check if it shows any fatal errors.

    Thread Starter DensitySK

    (@densitysk)

    correct. I do use Updraft Plus Backup plugin. Before every plugin update I always do a backup and if I notice anything strange, I always restore back until the problem has been solved. So there is definitely a restore from time to time.

    Do you have a solution on how this can be solved? Or how can I completely remove your plugin from my website and all database entries, so I can cleanly re-install it again?

    Thread Starter DensitySK

    (@densitysk)

    check email

    Thread Starter DensitySK

    (@densitysk)

    Thread Starter DensitySK

    (@densitysk)

    Thank you. I have already reached out to them. I had thought since the error is happening directly in Woocommerce, that it is realted to this plugin and not theirs.

Viewing 15 replies - 61 through 75 (of 120 total)