Submit Order does not show processing

[Brewhaus]

We have noticed this before, but have actually had a customer specifically bring it to our attention, which now gets us working toward a solution. When a customer click on the 'submit' button to submit their order, there is nothing to show them that the order is being processed. There is no audible 'click', and no visual 'processing' indicator.

I have noticed this at a couple of stages, most noticeably when hitting 'continue' when confirming the billing and shipping address. This is something that I noticed early on (under original site testing), but shrugged it off as a quirk with the software.

Is there a simple way for us to put the processing indicator in where it is missing? Should it already be there, and there is possibly something more afoot with our files?

[AbleMods]

Man, I'd like that too.

I've seen that AJAX "Processing..." popup from time to time, but it seems as if there has to be several seconds pass before it pops up. I want to lower that timeframe because it seems...off. It waits too long to pop up imho.

[Brewhaus]

The customer today commented that she did not think it had taken her 'click', so she tried a second and third time before she realized that it was working.

[AbleMods]

Hmm wonder if it's a simple as a style change on the button so the button colors change when it's clicked. Then the visitor gets at least some sort of visual cue that the click was "seen" by the system......

[jmestep]

This might help:
I searched the files for Processing and one place I found it was in the Admin/Store/Security/EncryptionKey.as
<asp:Panel ID="ChangeProgressPanel" runat="server" Visible="false">
<ajax:Timer ID="ChangeProgressTimer" runat="server" Interval="10000" OnTick="ChangeProgressTimer_Tick"></ajax:Timer>

ChangeProgressTimer.Interval = 3000;
I'm going to experiment some because we have a client who has trouble in the Admin using a Mac and none of us are having that problem. When he edits something, the change will get saved, but the processing panel never stops

[dappy2]

client who has trouble in the Admin using a Mac and none of us are having that problem. When he edits something, the change will get saved, but the processing panel never stops

There is a bug in asp.net AJAX / modal popup and Safari (or more specifically the webkit rendering engine). This affects Safari both on a Mac and PC. I believe there is a fix but it is really complicated and involves digging into the ASP.NET ajax functions.

I've seen the processing popup in Able in Safari however - in both admin and the store side - so I'm not sure if Able found a fix or a way around it / created their own modal popup.

We have a web app for another company that has this issue with the modal popup and I had to pop-up a warning for Safari users.

You might suggest your client uses Firefox as at least a temporary fix. I've done all development / testing for my able on a Mac and it works great.

[Brewhaus]

Judy- did you find if this managed to bring up the 'processing' image at the checkout, or did you get the chance to try?

[jmestep]

I didn't get a chance to try yet.

[BryanWarmoth]

I am experiencing a slightly different problem but similar. When the customer clicks continue after inputing their billing and shipping address the processing image will not go away. The content behind has updated but customers can not continue because the pop up is still present. This is only in safari and chrome, both which are webkit browsers. Any ideas what may be causing this? I added address validation once the continue button is clicked but the validation appears to work because the page is updated but the pop up will not go away. Thanks!

[BryanWarmoth]

I found this fix: http://blog.lavablast.com/post/2008/10/ ... -AJAX.aspx

[jmestep]

I've been trying to troublshoot order checkout on a site and I haven't tried Chrome, but in Safari, I have run across several sites that have the problem. Input your billing address information and the payment form becomes visible, but the processing screen takes over.
I've checked on 6 different sites, three different builds and the only thing I can find in common with the sites that have the problem is that they are using PayPal Express checkout.
Can you all verify it on your problem sites?

[Brewhaus]

We do not use PayPal checkout. Of course, our problem appears to be limited to no notification going to the customer that they have actually hit the 'Submit' button.

[BryanWarmoth]

Nope, we do not use Paypal.

[jmestep]

Well, back to the drawing board....

[jmestep]

After more digging--
I don't have the problem on Able 7.0.2, so I started looking for changes. Able has created a new file called WebKitFix.js and put it into a js folder at the root of the site. The code in it is:

Code: Select all

Sys.Browser.WebKit = {}; //Safari 3 is considered WebKit
if( navigator.userAgent.indexOf( 'WebKit/' ) > -1 )
{
  Sys.Browser.agent = Sys.Browser.WebKit;
  Sys.Browser.version = parseFloat( navigator.userAgent.match(/WebKit\/(\d+(\.\d+)?)/)[1]);
  Sys.Browser.name = 'WebKit';
}

Then in the Layouts/Scriplet.master, they have changed

Code: Select all

   <ajax:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true"></ajax:ScriptManager>

to:

Code: Select all

<ajax:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true">
        <Scripts>
            <ajax:ScriptReference Path="~/js/WebKitFix.js" />
        </Scripts>
    </ajax:ScriptManager>

I made that change on an Able build 10863 site and the problem on the checkout went away!

[Brewhaus]

Is this fix for the Submit button not creating an action to show the customer that the order is processing, or is it for the processing indicator that would not disappear (I believe that both are discussed in this thread)?

[jmestep]

I think it is both. The processing indicator just flashes by. The code in Able has it set to show after a particular length of time, but if the Ajax doesn't take that long, the processing doesn't show.

[cwswebdesign]

After following these changes, I was able to get Google Chrome to work properly as well, in case anyone is wondering whether it works or not. I'm on a much older build (11659), but I'm sure it'll work on other versions as well. Thanks for the great tip jmestep!

After more digging--
I don't have the problem on Able 7.0.2, so I started looking for changes. Able has created a new file called WebKitFix.js and put it into a js folder at the root of the site. The code in it is:

Code: Select all

Sys.Browser.WebKit = {}; //Safari 3 is considered WebKit
if( navigator.userAgent.indexOf( 'WebKit/' ) > -1 )
{
  Sys.Browser.agent = Sys.Browser.WebKit;
  Sys.Browser.version = parseFloat( navigator.userAgent.match(/WebKit\/(\d+(\.\d+)?)/)[1]);
  Sys.Browser.name = 'WebKit';
}

Then in the Layouts/Scriplet.master, they have changed

Code: Select all

   <ajax:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true"></ajax:ScriptManager>

to:

Code: Select all

<ajax:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true">
        <Scripts>
            <ajax:ScriptReference Path="~/js/WebKitFix.js" />
        </Scripts>
    </ajax:ScriptManager>

I made that change on an Able build 10863 site and the problem on the checkout went away!