17 messages in com.googlegroups.google-base-data-api[Google-Base-API] Adding payment_acce...
FromSent OnAttachments
jksmith22 Jul 2008 18:00 
jksmith23 Jul 2008 10:42 
Tom Wilson23 Jul 2008 12:39 
jksmith23 Jul 2008 14:43 
jksmith23 Jul 2008 15:39 
Marcos Oliva23 Jul 2008 15:52 
jksmith23 Jul 2008 16:23 
Tom Wilson24 Jul 2008 02:48 
jksmith25 Jul 2008 14:29 
jksmith25 Jul 2008 14:35 
Celebird26 Jul 2008 01:42 
Celebird26 Jul 2008 01:44 
jksmith28 Jul 2008 13:40 
Celebird29 Jul 2008 05:28 
jksmith29 Jul 2008 12:03 
Celebird29 Jul 2008 13:38 
jksmith29 Jul 2008 14:50 
Subject:[Google-Base-API] Adding payment_accepted attribute causes response code 400
From:jksmith (neon@gmail.com)
Date:07/22/2008 06:00:48 PM
List:com.googlegroups.google-base-data-api

I have a batch of, say, 25 items from my store. My app detects which ones aren't yet on Base, and adds them to an array ($to_add). Finally, there's a foreach loop that actually adds them to Base. One of the attributes added in the foreach loop is payment_accepted:

$newEntry->addGbaseAttribute("payment_accepted", "Google Checkout", "text");

I recently started getting "Expected response code 200, got 400". By commenting out selected parts of my code, I was finally able to narrow the problem down to this line -- if I comment it out, the error goes away. With further testing I figured out that of the 25 parts that get added, only one actually triggers the error. All of the rest go through fine. Comment out the payment_accepted attribute, and all go through.

How in the world can a static attribute be causing me so many headaches!? If all of the items go through fine without this attribute, then it can't be a problem with any of the other attributes... right?