There was a comma where there shouldn't have been, and a span without a closing bracket (>)
The span itself should have destroyed the script in any browser, but it didn't.
In your local TEST files from the v2.2 contribution, do the following and please post back if that fixes anything that you're experiencing.
Line 360:
.on('click', '#submitCreate, #submitGuest', function(){if ($('#NewAccount .required_icon:visible').size() > 0) alert('<?php echo MESSAGE_FIELDS_REQUIRED;?>');else if ($('#NewAccount .error_icon:visible').size() > 0) alert('<?php echo MESSAGE_FIELDS_ERROR;?>');else {$('#NewAccount').find('input, select, textarea').each(function(){if ($(this).val() == $(this).attr('title')) $(this).val('');});$.post(url,'action='+$(this).attr('id')+'&'+$('#NewAccount').find('input, select, textarea').serialize(),function(data){if (data.msg != '') alert(data.msg);if (data.status == 'success'){$('#Account').dialog('destroy');$('#checkout').show().find('#shippingAddress, #billingAddress').trigger('refresh').end().find('#cartContent').parent().load(url +' #cartContent', function(){$('#cartContent').trigger('refresh');});$('#NewAccount').dialog('destroy');}else alert('<?php echo MESSAGE_ACCOUNT_ERROR;?>');}, 'json');}});});},
Remove the comma from the end of that line.
Line 426:
<div class="cartRow6 cartDelete" data-pID="'.$products[$i]['id'].'"><span class="ui-icon ui-icon-trash"</span></div>
Change to:
<div class="cartRow6 cartDelete" data-pID="'.$products[$i]['id'].'"><span class="ui-icon ui-icon-trash"></span></div>
I am running this through an IE tester. I still have two issues from my end. The first is the cart delete button not working. The second is that shipping resets to cheapest method when payment is selected (but my radio buttons stay checked). The first works fine in other browsers that I've tested, but the second is across all browsers.
@
surrfman
I don't think anyone is interested in entertaining bogus workarounds. Let's get this thing fixed. The old OPC for 2.2 is how old now? I can tell you for a fact that the latest contribution STILL has bugs with fixes that have never been publicly posted. This was just contributed a few months ago. I am not about to leave it hanging with bugs and half cocked "fixes" that don't really fix anything.
@
ggrant3
Read one of my very first posts about the guest checkout. I wrote it that way and knew that I wrote it that way. When I've dealt with the bugs/browser issues, I will
consider providing instructions that take the "guest" checkout a step further. I still say if they come back, they aren't a guest. They are a client. At this point, that is not a bug. It was intentional.