Hi,

after updating to the latest release 8.x-1.4 we're getting an error in the status report, saying our address media using a geofield have mismatched configurations.

Indeed the database table still has the old, longer column definitions, causing the mismatch error.

Since Drupal has done away with automatic entity updates, shouldn't this module not have provided an update hook, changing the schema for preexisting installations?

Comments

marcoliver created an issue. See original summary.

teddyvermeulin’s picture

teddyvermeulin
Primary language French
commented

I have the same mistake. It seems that the update has no ID.

itamair’s picture

itamair commented
Status: Active » Fixed

ah ok ok ..., you are right, but sorry actually I don't have time to implement the hook_update for this.
Better to revert to the previous state of precision = 18 and scale = 10.

The just deployed new 1.5 release reverts to that state.

proxiss’s picture

proxiss commented

I am using a geofield field in my custom content type. It has 18/12 in DB while schema() in GeofiledItem.php 1.5 has 18/10. So I also get the mismatch reporting. I will change my db field by hand.

itamair’s picture

itamair commented

Argghhhh ... I am super sorry guys. Rush is always a bad advisor, and I am making a super mess here on this.
The new new 1.5 release reverts to the original state of 18/12 (not to have many other people previous to 1.4 having this warning/bug).

Status: Fixed » Closed (fixed)

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