Amazon onebox issue


#1

For some reason, the onebox doesn’t actually fill anything out
http://www.amazon.com/gp/product/B00H4SSB02

Doesn’t appear limited to just .com either:
http://www.amazon.co.uk/gp/product/B00H4SSB02

Edit: It seems the Amazon side is working OK:


(Apparently Archetype) #2

Hmm. Testing full link (for a different product):

Stripping parameters:

Stripping ref:

huh. it seems to be something about the onebox information for that product.


(Alan Tan) #3

Test…


(Alan Tan) #4

I think I fixed it for most of the products.

https://github.com/discourse/onebox/pull/304

http://www.amazon.com/gp/product/B00H4SSB02 seems to be a special case.


(Michael Downey) #5

Just a thought: It would be nice if this code also matched the smile.amazon.com domain (the rest of the URL is always the same) which allows non-profits to get a cut of the revenue.


(Kane York) #6

Submit a PR to expand the URL matching:


(Alan Tan) #7

Is there a reason we try to scrape using mobile pages from Amazon? The desktop pages contains a description meta tag that we can use to improve reliability and avoid breaking Amazon onebox everytime they change their HTML.


(Jeff Atwood) #8

The idea was that mobile would have less cruft to sort through, if desktop is easier, go for it.


(Alan Tan) #9

Hmm the description meta tag is pretty good but I’m not sure if on Amazon.com. *Free* shipping on qualifying offers is too much of a distraction. I would like to find out your thoughts on this :smiley_cat:


(Alan Tan) #10

Hmm I tried out using the description in the meta tag and I think it feels too much like an advertisement rather than providing more information about the product.

I’ll stick with the mobile pages.

cc/ @sam


(Jeff Atwood) #11

Have we pulled in the updated onebox @eviltrout?


(Robin Ward) #12

I just bumped it. I can’t say for sure if we were on the latest because our gemfile referenced a version that was pushed to Rubygems that wasn’t also set in our repo. I can confirm that now we are on the very latest onebox code.

https://github.com/discourse/discourse/commit/bcaad5282b890be290785773d42af2fc492ebefc


(Neil Lalonde) #13

Test again:

Looks like this bug isn’t fixed, or we still aren’t deploying the latest version of onebox.


(Alan Tan) #14

The PR hasn’t been merged yet :wink:

https://github.com/discourse/onebox/pull/304


(Jeff Atwood) #15

Ok can we please merge that @neil? And merge in onebox version update too.


(Jeff Atwood) #16

I think it is working now at last, thank you very much @tgxworld!


(Jeff Atwood) #17

(Arpit Jalan) #18

This is done now.