• Resolved demetrioffr

    (@demetrioffr)


    This just started this week – Been doing this for 8 months now..

    1. I go to Variations
    2. I go to Set Regular Prices
    3. I click GO
    4. I Enter in new Price $25
    – This is new Using Chrome SAVE CHANGES BEFORE CHANGING PAGE
    – I CLICK OK
    – The spinny circle come on
    5. I click SAVE CHANGES
    6. Some of my Prices change to $25 and some still stay the same at $42

    The only thing I have updated was to WP 5.4 from 5.3 I’m using WooCommerce 3.9

    If I do it like 3 to 4 times it might take or I have to go look under each variation and set it – so time-consuming

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    Hey there,

    It sounds like something is stopping the updated price from being applied to all of the variations.

    To start off, how many variations are you updating in one go?

    Can you please try making that change, then check the browser console to see if there are any errors?

    Using Your Browser to Diagnose JavaScript Errors

    Thread Starter demetrioffr

    (@demetrioffr)

    Im doing about 24 variants.

    But I have been doing the same products this way for 8 months. As i’m using Art of where tshirt drop shipper. they make up my products and make the product up and the varients up.

    Then I go in and do the price change like I have for over 500 plus products..

    I have tried both Chrome and FireFox

    This is all I get for the Console in Chomre

    JQMIGRATE: Migrate is installed, version 1.4.1
    post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wp.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #body_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"body_bg_image" id=?"body_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"body_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"body_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #breadcrumbs_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"breadcrumbs_bg_image" id=?"breadcrumbs_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"breadcrumbs_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"breadcrumbs_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #content_bottom_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"content_bottom_bg_image" id=?"content_bottom_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"content_bottom_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"content_bottom_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 2 elements with non-unique id #current-page-selector-1: (More info: https://goo.gl/9p2vKq) <select class=?"page-selector" id=?"current-page-selector-1" title=?"Current page">?…?</select>? <select class=?"page-selector" id=?"current-page-selector-1" title=?"Current page">?…?</select>?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_bg_image" id=?"footer_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_bottom_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_bottom_bg_image" id=?"footer_bottom_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_bottom_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_bottom_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_main_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_main_bg_image" id=?"footer_main_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_main_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_main_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_top_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_top_bg_image" id=?"footer_top_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_top_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_top_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #header_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"header_bg_image" id=?"header_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"header_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"header_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #page_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"page_bg_image" id=?"page_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"page_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"page_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #sticky_header_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"sticky_header_bg_image" id=?"sticky_header_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"sticky_header_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"sticky_header_bg_image" type=?"button" value=?"Remove Image">?
    post.php?post=87371&action=edit:1 [DOM] Found 2 elements with non-unique id #woocommerce_meta_nonce: (More info: https://goo.gl/9p2vKq) <input type=?"hidden" id=?"woocommerce_meta_nonce" name=?"woocommerce_meta_nonce" value=?"735c9ddaad">? <input type=?"hidden" id=?"woocommerce_meta_nonce" name=?"woocommerce_meta_nonce" value=?"735c9ddaad">?
    post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wordpress.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
    post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wordpress.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
    post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://widgets.wp.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
    
    
    Thread Starter demetrioffr

    (@demetrioffr)

    This is Firefox

    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
    TypeError: e is undefined 2 Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined 2 Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-response-listener.js:84
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
    Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
    TypeError: e is undefined Grammarly-bg.js:1:1062837
    
    Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    Thanks for that info!

    Checking through the browser console, there isn’t anything too strange happening, though those content security policy warnings might cause some difficulties if anything is being blocked.

    Im doing about 24 variants.

    That shouldn’t cause any trouble – sometimes strange behavior can come up with hundreds or thousands of variations.

    But I have been doing the same products this way for 8 months.

    Hmm – this is sounding more and more like a plugin or possibly your theme updated and created a conflict. That’s typically what happened when things were working fine and then they stopped working.

    ?
    The best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    Please do let me know how that goes!

    Plugin Support EtienneP a11n

    (@etiennep)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Variatiion PRicing Won’t set to new Price – Sest some to new and keeps some old’ is closed to new replies.