I've downloaded the 5.x-1.x-dev version but the following errors still occur on one of my nodes:

warning: implode() [function.implode]: Bad arguments. in C:\xampp\htdocs\thrillus6\sites\all\modules\asin\asin.module on line 205.

I'm currently using the asin field with multiple values. The problem seems to be triggered for me when I get over 6 entries in the field. Also, the ORDER in which the values are displayed in the field changes from edit to edit. The order seems to be reversed each time. (see image)

CommentFileSizeAuthor
asin_reversed.jpg22.82 KBzoon_unit

Comments

zoon_unit’s picture

zoon_unit commented

This problem may be due to certain ASIN numbers that resolve to book listings missing critical data.

For instance, I found one of my listings that lacked an author's name, which probably invalidates the implode statement. So maybe if you test for values before imploding? Once I removed the ASIN lacking an author's name, the errors went away.

The issue of ASINs changing order between updates is still a big problem. When putting in multiple values, you usually have a specific order that you want the listings to appear in. But since you can only put in 3 values at a time (before submitting to obtain more entry fields on a multi value field) it becomes almost impossible to get a book listing to show up in a specific sequence.

ju.ri’s picture

ju.ri commented

I get the same error here, even with dev version. the ASIN in question is B000AU0XDO.

ekrispin’s picture

ekrispin commented

See my explanation and complete fix in http://drupal.org/node/126436

eaton’s picture

eaton commented
Status: Active » Closed (won't fix)

The issue of ASINs changing order between updates is still a big problem. When putting in multiple values, you usually have a specific order that you want the listings to appear in. But since you can only put in 3 values at a time (before submitting to obtain more entry fields on a multi value field) it becomes almost impossible to get a book listing to show up in a specific sequence.

This particular problem is an issue inherent in CCK -- there's no way to explicitly force the elements of a multivalue field to appear in a particular order, at least not cleanly. It's being worked on but will need to be solved outside of asin_field.