CiviCRM Community Forums (archive)

There seem to be quite a few posts on this topic in the forums already, however none highlight the issue I seem to have found.

Booking process for paid events using Google Checkout as a payment processor is all great, takes you through to Google Checkout and processes payments in the sandbox with no problem. However, upon returning to CiviCRM, all bookings are given the payment status "Pending from incomplete transaction". This seemed like an issue with Google Checkout not getting the correct data sent to the API callback URL, and therefore not changing the payment status to "Registered" once the payment actually does go through.

API callback URL is correct in Google checkout settings - http://www.mysite.com/sites/all/modules/civicrm/extern/googleNotify.php, and that file exists on the server in that location.

Google Checkout's integration console reports a Send Failed with code: 404, followed by the HTML for my Drupal error 404 page - and an error 404 is recorded in the Apache server logs:
74.125.154.80 - - [04/Jan/2011:22:35:13 +0000] "POST /sites/all/modules/civicrm/extern/googleNotify.php HTTP/1.1" 404 6144 "-" "Google Checkout Notification Agent 1.0"

Nothing that seems at all of use is recorded in the civicrm.[long alphanumeric code].log file.

When I try to point my browser to the googleNotify.php file, I get the Drupal "Page Not Found" error message, and the server log reads:

80.46.144.9 - - [04/Jan/2011:22:29:14 +0000] "GET /sites/all/modules/civicrm/extern/googleNotify.php HTTP/1.1" 404 48212 "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13"

This got me playing around - pointing a browser to the url:  http://drupal.demo.civicrm.org//sites/drupal.demo.civicrm.org/modules/civicrm/extern/googleNotify.php for the Civicrm Drupal Sandbox does NOT give me a Drupal-handled 404 error, just a blank screen - which I would expect given the nature of the googleNotify.php file and the fact that no variables have been passed into it. A fresh sandbox install of my own of Drupal 6.19 and CiviCRM 3.3.1 does exactly the same, as expected.

Some simple tests revealed that in fact all .php scripts inside the /sites/all/modules/civicrm directory aren't being served correctly for my install if their location is just typed into a browser - instead of being handled as expected by Apache, Drupal seems to take over and give the Drupal 404 page. With the result that when Google Checkout tries to hit the googleNotify.php script, it gets the Drupal 404 error page instead.

The overall problem is obviously to get payments updating on the CiviCRM install - but the problem seems to be that Drupal's not allowing access to the googleNotify.php script that's necessary.

First thought: htaccess? I played around a little with a .htaccess file in the .../extern directory to see if I could override the default Drupal .htaccess file in the document root, but had no luck, as I'm not particularly up to speed with htaccess rules. Any suggestions?

Second thought: why is this different to a clean install? Anyone have any idea what modules/settings would cause Drupal to cut in and serve up an error when the url points to a valid file, but seemingly only in the sites/all/modules/civicrm directory?

I've made no changes to the default Drupal .htaccess file.

I'm pretty stuck - any ideas?

Hello
   We recently upgraded to Civi 4.2 and Drupal 7.  At the same time we added google checkout and are experiecing this same problem.  Did you get this fixed? If so, how?

Thanks, Holly