Zack Philipps

Nice! Kinda begs the question: why doesn’t WooCommerce prefix all this data with wc_ ?

Created an issue here: https://github.com/woothemes/woocommerce/issues/9703

Yep, everything works just fine now. Thanks again! I donated today; I’ll be sure to leave a review. Your plugin rocks.

Wow. I’m a complete idiot. I can’t believe I didn’t think of this. I had a CPT slug “state”. Makes sense why changing the Billing State (passed as “state” in the data) screwed everything up.

Thanks for all your help!

Confirmed that it’s not the gateway’s fault. Tested with Simplify Commerce and still doesn’t work.

That still didn’t fix it. I know WooCommerce uses endpoints now instead of dedicated pages for some things… And this AJAX request that’s looking for an endpoint returns a success message but for some reason the code is 404 instead of 200. I’m wondering if it has something to do with permalinks/rewriting and the way CPT UI works with them?

And here are lines 241-293 of of checkout.js:

wc_checkout_form.xhr = $.ajax({
	type:		'POST',
	url:		wc_checkout_params.wc_ajax_url.toString().replace( '%%endpoint%%', 'update_order_review' ),
	data:		data,
	success:	function( data ) {
		// Always update the fragments
		if ( data && data.fragments ) {
			$.each( data.fragments, function ( key, value ) {
				$( key ).replaceWith( value );
				$( key ).unblock();
			} );
		}

		// Check for error
		if ( 'failure' === data.result ) {

			var $form = $( 'form.checkout' );

			if ( 'true' === data.reload ) {
				window.location.reload();
				return;
			}

			$( '.woocommerce-error, .woocommerce-message' ).remove();

			// Add new errors
			if ( data.messages ) {
				$form.prepend( data.messages );
			} else {
				$form.prepend( data );
			}

			// Lose focus for all fields
			$form.find( '.input-text, select' ).blur();

			// Scroll to top
			$( 'html, body' ).animate( {
				scrollTop: ( $( 'form.checkout' ).offset().top - 100 )
			}, 1000 );

		}

		// Trigger click e on selected payment method
		if ( $( '.woocommerce-checkout' ).find( 'input[name=payment_method]:checked' ).size() === 0 ) {
			$( '.woocommerce-checkout' ).find( 'input[name=payment_method]:eq(0)' ).attr( 'checked', 'checked' );
		}
		$( '.woocommerce-checkout' ).find( 'input[name=payment_method]:checked' ).eq(0).trigger( 'click' );

		// Fire updated_checkout e
		$( document.body ).trigger( 'updated_checkout' );
	}

});

Here’s the stack trace:

POST https://example.com/checkout/?wc-ajax=update_order_review 404 (Not Found)
send @ jquery.js?ver=1.11.3:5
m.extend.ajax @ jquery.js?ver=1.11.3:5
wc_checkout_form.update_checkout_action @ checkout.js?ver=2.4.10:241

Just in case this would affect anything, I’m using the Authorize.net CIM credit card gateway.

I guess I should specify that the error is in the JS console.

Well, I finally found the wp-stream.com website, read the announcements, and found the roadmap and everything. Now all the disjointed documentation on GitHub makes a lot more sense.

Looks like Notifications will be back with Stream 3.1. Can’t wait!

I agree, I think the default for the plugin should be the default for WordPress, which is newest at the top. This plugin would be perfect if it behaved in that way.

Done!

Dima,

Excellent!!! Thank you so much. If this helps anyone out, I had to to a hard reload cmd+shift+R to get the filters to work on the front end.

Thanks again, this plugin is perfect!

Dima,

Thanks! I really appreciate the effort. However, the filters now appear to not work on the front end. So when I’m checking the filters off, nothing happens, whereas before I got the AJAX spinner and then the results changed.

In addition, it looks like if the attributes were set to order by “Name” they are no longer in alphabetical order. Obviously I could correct this by setting the option to “Custom” and manually ordering them alphabetically, but I believe the plugin should just use whatever settings are set in the attributes.

If you decide to work on that stuff, great (and many thanks), but before you do, would you mind shipping an update that rolls back to the previous version? Because as it stands, I’d rather have that one since the filters are functional.

Thanks again!

I really need this feature ASAP! Do you think this could be accomplished with a filter/action hook?