Search the forum for gbase.php which is a manual workaround for Google Base uploading. It will send your products to a file which you will then have to manually upload to Google Base for processing. In my case, I also had to replace instances of gbase.php in the product URLs with index.php, but after that, it worked perfectly.
I’ve never submitted code to this particular project, but it all depends on how the devs like to receive patches. In this case, a dev might just implement the solution from the bug report comment since it’s small enough.
Something that should be guaranteed to work is if you check out the 1.2 stable Magento sources (see http://www.magentocommerce.com/svn ) and then apply your change, and submit a patch against the baseline. The only reference I found to patches in this site’s docs was this ancient post that says to email it: http://www.magentocommerce.com/boards/viewthread/223/ Perhaps the bug reporting software will let you post a patch there instead.
the problem is definately attribute mapping. make sure your are within the parameters of google base. specs
I am not sure, or at least don’t know how it explains the next: couple days ago I start getting that message (Expected response code 200, got 400) when try to upload to Google API ANY available product, while I did not do any changes in my attributes mapping. I tried products from different attribute sets and still have same problem. Something happened. And the worst thing is I did not change the mapping.
The other issue, I am not sure how synchronization works, I tried once and did not noticed any changes in a Google database, only noticed that my products become available to upload to Google again. I thought it will finish the operation. Also, after I start getting Error 200, I made auto upload change after editing the product, but didn’t notice any changes in Google.
It looks like working with Google API needs a more attention from magento team.
I guess I was thinking that the users can change the sku and they can’t change the id. The only way it would be an issue is if you started all over with a new database. If you move the database to a new server the ids will be the same.
Googlebase was working fine for me (relatively - since everytime i synced it deleted all but 14 products off top even though it left it in gbase - which means i duplicated products readding i think) until a couple weeks ago.
I was experimenting with how to add certain types of products to the site and decided to make an additional attribute set. When I realized that one wasnt getting added to gbase I created an additional mapping for google base. Ever since I did that I cannot get gbase to work. So I deleted the additional attribute set. Still not working. I (big big mistake) deleted everything off google base and tried again… still didnt work. I deleted the additional attribute set mapping. Stil not working. Error 200/400 constantly throughout. So I don’t understand if the additional attribute set broke the app, why didnt removing it fix it? I checked in the sql db and confirmed the additional attribute set is no longer in the google api base attributes mapping table. One thing I noticed was in the table for eav_attribute_set it has like 15 different versions of the default set. I would love to try deleting 14 of them and seeing if that fixes it, but I am not willing to screw everything up.
On a second note - I have tried gbase.php to little avail. It skips about 400 of my active products, so I am missing a huge portion of the products on my gbase feed. I increased my timeout times on php.ini and that shouldnt be affecting it.