Anyone with the specific php.ini or .htaccess setting? Just the details please so I can explain to my web host system admin :wink2:Quote:
Originally Posted by birdoasis
Woody
Printable View
Anyone with the specific php.ini or .htaccess setting? Just the details please so I can explain to my web host system admin :wink2:Quote:
Originally Posted by birdoasis
Woody
Forgive me if this has been addressed previously, but there are so many pages.
My googlefroogle feed is working just fine, except it only creates a file with 12 products, not the 153 that are in the store. This started with one of the recent updates to adhere to Google's new standards.
Any ideas on what I need to fix?
Haha, I am having the same issue, and it still has not been resolved.
Zen Cart merchants with Froogle feeds
GoogleBase posted this tidbit on their help site.
Keep in mind that Andrew's feed generator is a "Froogle feed" generator, supporting old-style tab delimited feed format with an older schema. It is not a GoogleBase XML feed generator (see more below).Quote:
Is it enough to simply send the same data as I did for Froogle (name, description, price, product_url, and image_url)?
No. Unlike Froogle, our Google Base format will only be as good as the attributes that you send. Your chances of scoring higher on relevancy will be increased as you send more attributes. We're asking you to send us five additional attributes along with the basic ones you've submitted in the past. Because we think it's important to provide a consistent user experience, we will no longer list items that don't meet a minimal number of attributes by the end of February 2007.
Right now when you upload your Froogle feed you are not uploading to Froogle but are uploading to to GoogleBase. GoogleBase maps many of the older Froogle fields (attributes) to newer GoogleBase attributes (when the attribute names have changed). But sometimes that mapping can go haywire.
Note Andrews' latest Google Froogle Feed generator mod v.1.33 currently generates:
title + description + link + price + image_link + expiration_date + label + id + brand+ product_type + condition + currency
That is twelve attributes (not necessarily in above order)
GoogleBase now requires and "supports" all above but two. Currency and label are no longer "supported". It is unclear what "unsupported" means in this context.
See post here: http://googlebase.##########################/2007/...supported.html
From the Google post copied above it appears we all need to add five more attributes to our Froogle feeds. (Unsure if need to add two more than this to also replace currency and label).
Below are 'optional" attributes Google recommends:
And Google says it is best to customize you feed with and custom attributes or at least design your feed around popular "Item Types" (aka Information Types) which Google has assigned pre-set attributes, depending on the product.Quote:
Optional attributes
The following attributes are optional, but Google recommends including as many attributes as possible as it will increase your items' "exposure in search results".
* payment_accepted
* payment_notes
* pickup
* price_type
* quantity
* shipping
* tax_percent
* tax_region
Example:
Item Type: Books
- Specific Item Attributes:
For more info: http://www.google.com/base/products.htmlQuote:
Books
* author
* binding
* edition
* genre
* isbn
* pages
* publisher
Pretty much this means Zen Cart shopowners need a revamped mod to support additional attributes. Or hack Andrews latest mod version and hardcode in five more "static" attributes, at least temporarily to keep your Froogle feeds accepted for the short term (this only make sense if you have many products). But understand this will not mean your feed will be published to GoogleBase, only to Froogle (if accepted).
So what we really we need now is a mod designed for GoogleBase which exports XML supporting RSS2+GoogleBase namespace and extended attribute support.
It is possible Andrew's RSS2 mod could be hacked as such, as he has already updated it to support GoogleBase namesapce.
Hoping soon, a white knight developer will appear from the mist and release a GoogleBase for Zen Cart mod supporting the new required schema and optional attributes. And integrate a ZC admin interface so a shop-owner can update the mod output schema whenever Google updates their feed requirements.
Or even better create a "Store Connector" for Zen Cart.
A person can dream can't he?
Woody
If you upload a Froogle feed and observe an error for a specific product, such as:
You can see that error doesn't indicate exactly where in your product feed the invalid or disallowed character might reside. (it will tell you the product line number).Quote:
our bulk upload contains an invalid character for the current encoding setting or contains a disallowed character.
So try this:
In your GoogleBase admin (on Google Server) click on My Items tab, click Bulk upload files. If you received an GoogleBase error message you should also see a detail message with a "Change settings" link. Change your encoding to Latin-1 (from UTF-8). Then re-upload your feed.
Changing the encoding worked for me. I'm awaiting now to see how the published items show up on Froogle and GoogleBase and how it might affect search.
Woody
An older version of Andrew's Google Froogle feed mod (v1. 20?) generates old Froogle attribute names in the following format:
product_url name description price image_url category offer_id
Note the above feed format does NOT contain the label attribute and the attribute names are old Froogle attribute names, not the more recent GoogleBase attribute names. And with only seven attributes the feed from this older version feed format does not meet the new GoogleBase feed guidelines.
However I just used the older mod to generate a Froogle feed from Zen Cart and my uploaded feed was completely accepted by GoogleBase and all items are now published and searchable.
So it appears that Google is still mapping the old Froogle attributes to the newer GoogleBase attribute.
So if you're having issues with more recent googlefroogle mod you might consider trying an older version, at least temporarily. YMMV.
Woody
Quote:
Originally Posted by Woodymon
Woody,
This setting worked for me:
Please keep in mind that we only have about 12,000 products so it might not work for others.Code:max_execution_time = 300
max_input_time = 90
memory_limit = 32M
Basically what's happening is the new GoogleFroogle generator is using IH handler image now and the script needs to allow for IH2 to create all images needed if the image doesn't exist in bmz_cache. In our case because not all product pages has been visited prior to using the generator, the mod was timing out creating the need image and point to the IH2 url for image instead of the old way where it just uses url/images/large.
Hey that is major helpful info. Thanks!Quote:
Originally Posted by BlessIsaacola
Question: I was of understanding Andrew updated the mod for IH2 compatibility and the generated feed's image_link attribute referred to the large image files in the "standard" /images directory and that the feed does not include links to the small and medium images (which as you explain are created on the fly and thrown into bmzcache for futre reference). At least thats how I understand it. And my feeds image_link url's alwasy refer to the large images in /imagesQuote:
Originally Posted by BlessIsaacola
Or is that anytme the large image is referred to then that auto prompts the generation of the other two associated images?
GoogleBase/Froogle wants the large images.
Woody
Prior to the last version Andrew released (1.3.3) the image url generated was url/images/large/filename which of course doesn't exist if you have IH2 installed. In the past you have to make a code change to generate the right path when using IH2.Quote:
Originally Posted by Woodymon
The lastest mod generates url using IH2 url if installed. The only issue with this is small, medium and large images are ALL generated on the fly and stored in bmz_cache folders. IH2 doesn't use image/medium or image/large folders at all.
Woody,
Another interesting thing is I actually played around withWhen set to 90 googlefroogle generated 2MB worth of product listing, when set to 180 googlefroogle generated 8MB of product listing which represents 10,043 records/products. When set to 200 it generated all our records.Code:max_execution_time = 300
We are with a new host with a little fast processor and memory and perhaps that accounted for not needing it to be at 300 anymore to generate all the products.
I also noticed that as I ran googlefroogle, the more products created the more images are added to my bmz_cache folder. So the max_execution_time more than any other setting is the key to this thing.