Checkout / Google Checkout Error

You're using an old version of checkout. Please update your installation to checkout 0.4.0.

LOL! it's actually a typo in checkoutgoogle, my bad, sorry.

I'll get the revised code into the repository later today, I hope.

Thanks for pointing out the problem.

A fix is uploaded - it should be downloadable from the 'get more plugins' page in three hours. Look for code revision 1643.

You're not out of the woods yet though - you only get the effect of that bug if the google website returns an error, so I shall wait with interest to find out what happens next!

Edward,

if you have checkout administrative notifications enabled you should get an email saying "GoogleCheckout: there was a problem preparing an order when a user tried to use Google Checkout." and going on to list the response from the Google website, which will help identify the error.

Alec,

This is what I receive back from google...

You must use HTTP Basic Authentication for API calls (username=Seller ID, password=Merchant Key)

Not sure what this means, I would think this would be transmitted with the initial transmission.

Yes, I have double-checked that already. I was thinking along the same lines so My next step will be to contact google support and see why authentication could be failing.

This was the result of adding the print_r statement above:

Array
(
[Authorization] => Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
[Content-Length] => 1522
)

It appears to not contain my merchant id and key...strange, this information is readily visible on the Google Checkout Configuration screen.

Hi,

I'm having the exact same problem with my installation.

Any help or update on this situation would be greatly appreciated.

Thanks.

Gallery version = 2.3-rc-2 core 1.2.37
API = Core 7.54, Module 3.9, Theme 2.6, Embed 1.5
PHP version = 5.2.4 apache2handler
Webserver = Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.8b FrontPage/5.0.2.2635 mod_bwlimited/1.4 mod_auth_passthrough/2.1 PHP/5.2.4
Database = mysqlt 4.1.22-standard, lock.system=flock
Toolkits = NetPBM, Gd, jpegtran, Ffmpeg, ImageMagick, Dcraw, SquareThumb
Operating system = Linux ns1.myhosting.com 2.6.18-92.1.13.el5 #1 SMP Thu Sep 4 03:51:01 EDT 2008 i686
Browser = Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I'll look into it further. Bear in mind that checkoutgoogle is only being used by about 4 people on the planet, at the moment, with you at numbers 3 and 4. (I got no response when I asked for volunteers to help test it, so I uploaded the code as-is, for people to try out.) It uses various parts of the Gallery installation that other checkout modules don't, particularly regarding encryption, authentication, ssl access etc, so I'm not surprised it's not a straightforward install at this stage. Please be patient while we learn where the problems are on different installations.

Alec, have you had any time to look at this issue?

No problem, I am actually doing well with paypal orders right now as well...but would like to revisit Google Checkout in the future. The whole checkout module has been awesome, no more wasting gas for proofing and ordering!!!

When I try the test button I get

It doesn't help that my host has not yet updated the certificate and it has expired, but even prior to this it was giving the same error message.

Hmmm, my test is failing now as well. But it was working (the test button at least), prior to the last build you released I believe. I do not think the callback url is anywhere my problem yet...I am not getting near that far. The initial post to Google is failing Basic HTTP Auth.

It is required for Level 2 Integration...which is receiving Order Payment, Shipping, and Completion notices from Google. Theoretically, with just Level 1 Integration you could verify the order completion in the Google Interface and update your order status in Gallery Site Admin. But I very much would like to have Level 2 Integration working.

@edwardtn & winkypicker: the test button also tests the http authentication data. If you put your regular gallery url up to and including the main.php part in the box (not HTTPS, just HTTP) then you should be able to get a positive test result, if your website is correctly encoding and decoding your merchant id and key as the authorisation data. Please try this and report the results.

Incidentally, if you don't have http:// access you can "lose" orders in the system - Google can't contact your site to confirm the order, and if the customer doesn't return to your website after payment then the transaction will never ever show up in the orders table for you to be able to update its status. I strongly recommend you *don't* use checkoutgoogle unless and until you can arrange HTTPS access. I'll update the module documentation to make that clear, tomorrow.

Alec,

I tried what you said and I got

(The URL I input disappears after I hit the test button)
As stated above I then copy and paste the URL into Google Checkout Settings but get

Which was expected. Then I thought well this is only needed for Level 2 integration as previously discussed and I try and make a purchase. I click the Google Checkout button and I get:

Alec,

Yes, I get the problem transferring you to Google message along with an email which says:

Plus a link which gives this result:

@winkypicker: can you please insert a line into your modules/core/classes/helpers/Webhelper_simple.class file at 248 so that it reads like this:

	foreach ($requestHeaders as $key => $value) {
	    $headerLines[] = $key . ': ' . $value;
	}
// new line here:
        echo'<pre>';print_r($headerlines);echo'</pre>';
	$success = $platform->fwrite($handle, sprintf("%s %s HTTP/1.0\r\n%s\r\n\r\n%s",
.
.
.

And report the result when you click on the pay-by-google link. Actually, better send the results to me by private message, as it should contain your merchant/key data (feel free to change a few digits if you like).

Ok, change it to this:

	foreach ($requestHeaders as $key => $value) {
	    $headerLines[] = $key . ': ' . $value;
	}
// new line here:
        echo'Here is the debugging information that Alec wants to see:<br><pre>';print_r($headerLines);echo'</pre></br>Debugging Info Ends.<br>';
	$success = $platform->fwrite($handle, sprintf("%s %s HTTP/1.0\r\n%s\r\n\r\n%s",
.
.
.

BTW you don't need to bother deleting the template cache.

Edit.. Aargh.. my mistake: headerLines should have a capital L in it.

Interesting...

OK, load up modules/checkoutgoogle/classes/CheckoutGoogleResponseHelper.class and add this at line 188:

    	$googleHeaders = array( 'Authorization' => 'Basic '.$authorizationKey, 'Content-Length' => strlen($data) );
        //add this line:
        echo 'About to execute requestWebPage with the following header data:<pre>'; print_r($googleHeaders); echo '</pre>';
	list ($returnStatus, $headers, $body) = GalleryCoreApi::requestWebPage($url, 'POST', $googleHeaders, $data); 
        .
        .
        

And try again!

Exactly that? That is, you didn't redact any characters in the [Authorization] field? OK, that's definitely incorrect, so I suspect we're getting somewhere.

Please add this line at 167 to the same file echo "<pre>Merchant Id is: $gcMerchantId, MerchantKey is $gcMerchantKey, and authorizationKey is $authorizationKey</pre>"; so it reads

}
	$authorizationKey = base64_encode($gcMerchantId.':'.$gcMerchantKey);
        echo "<pre>Merchant Id is: $gcMerchantId, MerchantKey is $gcMerchantKey, and authorizationKey is $authorizationKey</pre>";
	switch ($type) {
        .
        .

and report back.

If you get sensible output, please change some of the characters of each field to either random digits, or x's, but please leave the field lengths the same.

Are you in live or test mode? Can you just 100% confirm for me that in the Admin page you've filled in the Merchant Id and Merchant Key boxes that match the mode you're trying to work in (test or live)?

It's very peculiar - it looks like that piece of code isn't reading your Id and Key from the db, although why that might be I have no idea. Can you post as an attachment that entire modules/checkoutgoogle/classes/CheckoutGoogleResponseHelper.class file so I can have a look at it please?

Thanks

can you put some random characters into the test-mode Merchant Id and Key fields, and save them - then retry, and see what the debugging lines we added to the class file produce on screen?

Ok... now it looks like we're getting somewhere. Apparently your installation thinks it's in test mode, even when you've set it otherwise.

Do you have access to phpMyAdmin to have a look in your database? If so, can you run this query (with table names adjusted, should you need to):

SELECT  `g_parameterValue` 
FROM  `g2_PluginParameterMap` 
WHERE  `g_pluginId` LIKE  'checkoutgoogle'
AND  `g_parameterName` LIKE  'gcMode'

and let me know what the result is?