The setParam is the correct method to use, double check the raw xml
retrieved for the thumbnails attributes.

Try

getThumbnails() - Method in class
com.google.api.gbase.client.GoogleBaseAttribute
Gets the reference to the list of thumbnails for this attribute
(reference - http://code.google.com/apis/gdata/javadoc/index-all.html)

Tom Wilson
Freelance Google Base Developer and Consultant
www.tomthedeveloper.com

Google Base Tools - http://dev.tomthedeveloper.com/googlebase
Featured Project : 
http://google-code-featured.blogspot.com/2008/02/google-base-competitor-analysis.html

On Jan 17, 6:34 am, Jick <[email protected]> wrote:
> $entry->getThumbnailLink() also doesn't work.
>
> Error: Call to undefined method
> Zend_Gdata_Gbase_SnippetEntry::getThumbnailLink()
>
> On Jan 16, 5:00 pm, Jick <[email protected]> wrote:
>
> > I test the parameter using the demo in getting started using the same
> > search parameter in bq and it shows that it has the gm namespace.
>
> > <gm:thumbnail width='60' height='60'>http://base.googlehosted.com/
> > base_media?q=http%3A%2F%2Fthumbs.ebaystatic.com%2Fpict
> > %2F110336272472_1.jpg&amp;dhm=adaf084b&amp;size=5</gm:thumbnail>
>
> > although I'm not very sure if $query->setParam
> > ('content','thumbnails'); really work on my script.
>
> > I've been looking for the solution for two days now but still no
> > luck. :(
>
> > Thanks for the help I really appreciate it.
>
> > On Jan 16, 4:01 pm, Celebird <[email protected]> wrote:
>
> > > does the returned xml contain any
> > > gm namespace declaration or data?
>
> > > that is, try catching the raw xml
> > > outside the php via a packet-trace.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Base Data 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-Base-data-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to