Getting fatal exceptions in the Zend_Gdata framework after setting up
the Community Mapping example described at
http://code.google.com/apis/maps/articles/communitymap.html

I built the Community Mapping example (2007, by Pamela Fox) htm and
php files.

I uploaded the Zend Gdata Framework v. 1.9.2 to my web host which is
running Apache 2.2.13 and php 5.2.9. and adjusted the include_path for
my webhost's file structures invoked using ini_set in the
communitymap_globals.php.

I created the User and Location worksheets in a Google Docs
Spreadsheet and have inserted my valid API key in the http: address
string to the Google Javascript API in mainmap.htm,
communitymap_register.htm and in communitymap_login.htm.and inserted
my spreadsheet ATOM for sheets od06 and od07 in
communitymap_globals.php and in mainmap.htm

I then manually populated several rows in the Location worksheet to
test mainmap.htm

user           place    lat              lng            date
Mike           RC Home  49.42255        -123.6451       12-Sep-2009
Mike           Van Home 49.261  -123.0865
Mary           home             49.43   -123.6658
TELUS     Boot          49.232757       -123.01936

and am successful in getting a valid Google Map accessing that data
under Firefox 3.5.3 at this URL:  http://scfruittree.org/maps/mainmap.htm

However, upon doing a button submit on the page register page at URL:

http://scfruittree.org/maps/communitymap_register.htm

which should setup and trigger the Zend Gdata framework to write the
$_POST['username] and $_POST['password' form data to the Google Docs
User worksheet and pass next to communitymap_login.htm.

But...I'm getting this response from the server:
***************************************************************************************************
Register for Community Map
Successfully registered.Proceed to Login.
Fatal error: Uncaught exception 'Zend_Gdata_App_HttpException' with
message 'Expected response code 200, got 400 Parse error: Encountered
"<EOF>" at line 1, column 5. Was expecting one of:
<DATE> ... <FLOAT> ... <BOOLEAN> ... "!
" ... <STRING> ... <NAME> ... "{" ... "
(" ... "$" ... ' in /home3/scfruitt/public_html/Zend/
library/Zend/Gdata/App.php:700 Stack trace: #0 /home3/scfruitt/
public_html/Zend/library/Zend/Gdata.php(219): Zend_Gdata_App-
>performHttpRequest('GET', 'http://spreadsh...', Array, NULL, NULL,
NULL) #1 /home3/scfruitt/public_html/Zend/library/Zend/Gdata/App.php
(861): Zend_Gdata->performHttpRequest('GET', 'http://spreadsh...',
Array) #2 /home3/scfruitt/public_html/Zend/library/Zend/Gdata/App.php
(754): Zend_Gdata_App->get('http://spreadsh...', NULL) #3 /home3/
scfruitt/public_html/Zend/library/Zend/Gdata/App.php(205):
Zend_Gdata_App->importUrl('http://spreadsh...', 'Zend_Gdata_Spre...',
N in /home3/scfruitt/public_html/Zend/library/Zend/Gdata/App.php on
line 700
200
******************************************************************************************************
Do I need different syntax/args in setupClient() which is defined in
communitymap_globals.php?

*****************************************************************************************************
function setupClient() {
  $email = "[email protected]";
  $password = "xxxxxxx";
  $client = Zend_Gdata_ClientLogin::getHttpClient($email, $password,
          Zend_Gdata_Spreadsheets::AUTH_SERVICE_NAME);
  $gdClient = new Zend_Gdata_Spreadsheets($client);
  return $gdClient;
}
*********************************************************************************
and which is called from communitymap_register.htm -->
communitymap_newuser.php

Has the syntax required by the Zend framework changed or ??

Many thanks in advance...
-Mike

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-maps-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to