Viewing 15 replies - 1 through 15 (of 44 total)
  • Same here. If you are signed in it will populate the state field but even with FF & Chrome it will throw an error that state is necessary for checkout. Not logged in users simply get stuck on the checkout page without being able to enter any information.

    I’m experiencing the same problem.. Finally made the leap from 2.2. to 2.3 haha… bad timing ??

    Is there a way to regress to 2.3.5 without messing stuff up?

    Same issue here…

    Same issue here.

    Thread Starter sneader

    (@sneader)

    I have opened a ticket with WooThemes about this bug. Ticket #270929

    – Scott

    Is there a way to install an earlier version of WooCommerce? I can restore my backup but I’d prefer to install 2.3.5?

    I am also having this same issue…any solutions yet?

    The quickest solution is:

    https://downloads.www.ads-software.com/plugin/woocommerce.2.3.5.zip

    Revert to 2.3.5. I just reverted our sites to 2.3.5 and all works fine again.

    Can I just overwrite the 2.3.6 files via FTP or does it need to make DB changes and all that?

    Vagore: Just upload, overwrite, and you’re good to go. There are no database changes.

    Can verify: rolling back to 2.3.5 fixed the issue. Simply FTP the old folder overwriting the 2.3.6 folder and it’s all good.

    Thanks so much!! Testing install now.. ??

    Hi,

    The recent upgrade was to address in part an injection vulnerability. Rolling back reintroduces that vulnerability. An option while waiting on the next fix is comment out the script responsible for the select overlay.

    In the woocommerce plugin folder:
    includes/class-wc-frontend-scripts.php
    approx. line 118 – comment out

    //self::register_script( 'select2', $assets_path . 'js/select2/select2' . $suffix . '.js', array( 'jquery' ), '3.5.2' );

    Or edit this file:
    /wp-content/plugins/woocommerce/includes/class-wc-countries.php

    And for all countries you sell to – comment out the placeholder tag in the state section. I only sell in US so it was easy for me.

    For example in line 861, for US:

    This:

    'US' => array(
    	'postcode'  => array(
    		'label'       => __( 'Zip', 'woocommerce' ),
    		'placeholder' => __( 'Zip', 'woocommerce' ),
    	),
    	'state'     => array(
    		'label'       => __( 'State', 'woocommerce' ),
    		'placeholder' => __( 'State', 'woocommerce' ),
    	)
    ),

    becomes

    'US' => array(
    		'postcode'  => array(
    		'label'       => __( 'Zip', 'woocommerce' ),
    		'placeholder' => __( 'Zip', 'woocommerce' ),
    	),
    	'state'     => array(
    		'label'       => __( 'State', 'woocommerce' ),
    		/*'placeholder' => __( 'State', 'woocommerce' ),*/
    	)
    ),

    Thread Starter sneader

    (@sneader)

    Abland, beautiful fix — thanks very much!!

    Still no response from WooCommerce. The auto response to my ticket request (as a paying customer) says their normal support is Monday-Friday. I think it’s time for WooCommerce to step-up their support game.

    – Scott

Viewing 15 replies - 1 through 15 (of 44 total)
  • The topic ‘State Selector not working in 2.3.6, in Internet Explorer’ is closed to new replies.