Handling for order changes

Hi Sean,

I can’t give you a URL, but I can say that the test I made was from the front end: a regular web order. I didn’t try anything on the backend with .14.

Good luck.

John

Hey John,

Did you by chance update your woocommerce? I updated the plugin to 0.15 to fix an issue I noticed with the new version. I don’t think the changes I made were breaking.

Anyway I was happy be able to reproduce so see if the fix works for you when you update.

Cheers,
Sean

Hi Sean,

Yes I had updated to the latest woo (2.0.20). I updated striper to .15 and the problem still existed. I am running wordpress framework 3.6.1 BTW.

So, I used Updraft to restore my plugins to the state they were Nov 21st and tried again and everything worked again. The only 2 plugins that changed since Nov 21 were striper and woocommerce. The working versions are striper .12 and woo 2.0.19

Then I updated striper to .15 and the system stopped working. Then I updated woo to 2.0.20 but it remained broken. I cleared cookies in the browser and restarted. No change.

Next I updated WP to 3.7.1 and reverted back to striper .12 and woo 2.0.19 and it works. Then I updated woo to 2.0.20 and it kept working. Lastly, I updated striper to .15 and it stopped working with the same error message as I noted above. I tried with a different browser on another computer and it still doesn’t work.

Conclusion is that .15 does not work for me regardless of woo or WP versions, whereas .12 works with all the combinations.

John

Cool, at least we can rule that out, so what I changed is that I’m now using an external JavaScript file now to interface with stripe.js which is a requirement.

The reason being some users seem to have a plugin which strips the js from the template.

If you cannot give me a URL, I only need to see your checkout form to debug, can you do we a favor and see if a request is being made for a striper.js on your checkout form?

Most likely the problem is that for some reason that file is not being delivered correctly or something along those lines.

What I may have to do is something tricky where I add js to the template and the external file to try and accommodate everyone.

So yea if you know how to use the chrome debugger and can look at the network section to see if that file is being requested that would be awesome in helping me try to debug.

Or if you know any reason why static resources I.e. JavaScript might have a hard time loading in your setup.

Alrighty, so added back in the code from 0.12 that seemed to work for you, directly in the template.

Try out 0.16. If that doesn’t work for you, I have one more angle of attack I can try.

Sorry for the delay. Since I don’t know the chrome debug stuff, the next best thing is that I give you the URL that will get you to the checkout:

northarmknives.com/product/test

I’ve left striper .12 in place until you can try this. Then I can try .16
if needed.

Thanks for all you are doing.

John

Cool, yea 0.12 is working great, let’s go ahead and update.

Curious to see what happens with the later ones where the external js is not being loaded, though 0.16 should work anyway since it has both.

Ok, I upgraded to .16 and it works. Let me know if you want me to downgrade to .15 so you can give that a try.

John

Hey John,

I’ve done some debugging on your site, it’s a strange situation, probably a race condition with the DOM loading, if none of this makes sense, don’t worry it’s all good, mostly for posterity.

Second, another symptom/cause I’m seeing, another JS error which you can see in the console and also Striper doesn’t work after that. (I have nothing to do with superfish) I imagine you might have installed this plugin.

Uncaught TypeError: Object [object Object] has no method 'superfish' superfish.js:123

So the Striper plugin seems to work around 50% of the time, I’m going to do that other ‘angle’ of attack to make it work 100%, which involves waiting until the click is made, using delegated events, then, checking if the bind to checkout is done correctly and assign if it is not. Look for that in the morning, I think it will be a final correct solution for installations like yours where the DOM is not guranteed on page load.

Sean

Hi Sean,

FYI
I ssh’d to my bluehost account and did a find command to look for superfish.js. It showed up under the wootique theme I am using.

John

Hi Sean,

How did you make out with that “other angle of attack?” I’ve rolled back to 0.12, which is a stable version the works for me until you tell me that you are comfortable you have the race condition and the “uncaught type error” issues under control.

Thanks,

John

Hey John,

getting real close, I will have something for you this evening. hopefully that error will be gone forever.

Alright, excited for you to try the 0.17.

I completely switched out how the system is working, I think it’s far superior. Ping me when it’s up if you have any issues before taking it down.

Also, if it works as expected double check the manual invoicing feature I built for you a month or so ago, as that was involved in this update.

Cheers,

Sean