Google Checkout module for ZC 1.3.x (beta)

[limelites]

I was refering to my clicking on the url you gave for responsehandler.php. I've never seen it redirect to google.com as yours did. Generally you would see a login box asking for a user id and password. That's the expected action when the responsehandler.php url is working correctly. Or you would see various 404 and 405 messages that the page or server could not be found.

Of course you are correct you can still get the money. If your responsehandler was working, though, you could complete the sale entirely from within your zen cart, without having to go to your Google account. And your sale info would automatically be registered in your admin. Your choice, though...

Granted, it would sure be useful if Google sales went through ZC Admin area, then I could print off invoices and such like. I have no idea why my responsehandler redirects to Google, I've not edited it or anything so how could it have a redirect script in it? Weird!! Apart from uninstalling and reinstalling GC, how would you recommend I get responsehandler acting normal?

Is there a possibility that it has something to do with my GoDaddy SSL certificate and my hosting provider being two defferent entities?

I believe I said I was NOT seeing the big blue button on the login page.

In a successful standard installation of the GCO module you would have the big blue Google Checkout button in two places: the login page and in your shopping cart page when there's something in the cart. You will NOT have radiobuttons with Google Checkout as an option. You will NOT have to change code to remove the radiobutton.

Ahhhh, I see what you're saying now, sorry. I didn't want the Big Blue button on my login page, unless something was in the cart. If something is in cart then indeed, the big blue button will appear on the login page... try it and see :-) Clever eh?

The original use agreement with Google was to have it behave as a full-service checkout that did not require a user to have an account with you before they could purchase. It was deliberately designed NOT to be simply a payment method, per Google.

I understand this now, but I don't think it's very clever and perhaps even misleading? The customer would've had the chance to checkout using Google prior to logging into the site. As above, the big blue button appears when there's something in your cart at the login page, so is that not compliance enough with the original user agreement?

If what you're saying is right, then after the customer chooses to log in anyway, why is the big blue button option still there at all?

It doesn't make sense to me to say a radio button option at the final confirm order page is violating the GoogleCheckout user agreement, but a big blue button on the exact same page is not? If the radio button was to do the exact same thing as the big blue button then how can that be a violation?

Surely you can see that yourself?