unserialize() error in Kickstart 2 installation [#1893392]

In a Kickstart 2 installation, I got an error reading:

Warning: unserialize() expects parameter 1 to be string, array given in commerce_price_table_field_load() (line 171 of /.../htdocs/sites/all/modules/commerce_price_table/commerce_price_table.module).

because the object has been unserialized already.

The attached patch adds an extra is_array() check.

Comment	File	Size	Author
#5	commerce_price_table-7.x-1.1-remove-kickstart-2-error-v2.patch	657 bytes	Cybso
	commerce_price_table-7.x-1.1-remove-kickstart-2-error.patch	603 bytes	Cybso

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Cybso CreditAttribution: Cybso commented 20 January 2013 at 10:51

Same problem reported in http://drupal.org/node/1668260

Comment #2

Cybso CreditAttribution: Cybso commented 20 January 2013 at 10:56

(duplicate post - sorry)

Comment #3

pcambra

he/him

Spanish

Asturies

CreditAttribution: pcambra commented 20 January 2013 at 16:04

Shouldn't this be part of #1823012: Add IEF integration?

Comment #4

c.altosax CreditAttribution: c.altosax commented 22 January 2013 at 23:13

We use IEF on our site, and just installed the price table module yesterday. And, like you, we received this unserialize error. I do not understand completely what the error means, or if it is likely to cause problems down the road. Do you more experienced guys out there know whether it is safe to just ignore this error for now, until the maintainer updates his module?

Comment #5

Cybso CreditAttribution: Cybso commented 24 January 2013 at 15:45

File	Size
commerce_price_table-7.x-1.1-remove-kickstart-2-error-v2.patch	657 bytes

Apart from this bug Commerce Price Table works fine with IEF. The other ticket is about hiding the default price field and integrating the price table into the IEF summary table. So I would consider this as a separate bug.

I reviewed my patch, and noticed a problem: If '$items[$id][$delta]['data']' is an array, it would be emptied, because PHP would jump into the "else" condition. Problem fixed in the attached patch. Also, changed check from "!is_array(...)" into "is_string(...)".