The module uses, for the fid database field, a data type that can contain more values than the delta field used from filter.module. As consequence, the module could pass to filter.module a value that the module is not able to save in its own database table.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Priority: Normal » Minor

This bug is not evident, until the user doesn't create enough filters that the field primary key contains a value Drupal core core is not able to preserve into the filters table.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: Miscellaneous » Database schema
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed
Issue tags: +6.x-1.0-beta7

The code has been changed, and committed in CVS (for both the branches).

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue tags: +6.x-2.0-beta3

I am correcting the issue tags.

Status: Fixed » Closed (fixed)
Issue tags: -6.x-1.0-beta7, -6.x-2.0-beta3

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +6.x-1.0-beta7, +6.x-2.0-beta3

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.