Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It appears that fixDumperFieldIncompatibility method is causing a warning:
Warning: preg_match() expects parameter 2 to be string, array given in DumperPluginManager.php on line 87
On inspecting the value of $dumper_result, this is what it contains for me:
Array
(
[lat] => <REDACTED>
[lng] => <REDACTED>
[lat_sin] => <REDACTED>
[lat_cos] => <REDACTED>
[lng_rad] => <REDACTED>
[data] => Array
(
[streetNumber] => <REDACTED>
[streetName] => <REDACTED>
[postalCode] => <REDACTED>
[locality] =>
[subLocality] =>
[adminLevels] => Array
(
[1] => Array
(
[name] => England
[code] => England
)
[2] => Array
(
[name] => <REDACTED>
[code] => <REDACTED>
)
)
[country] => United Kingdom
[countryCode] => GB
[timezone] =>
)
)
I'm geocoding from an address field. I've created a patch so I can geocode my addresses but I suspect this might not be entirely suitable for all cases. I've not really fully grokked the code for this module so not entirely sure under what circumstances only a string would appear in the $dumper_results variable.
Comment | File | Size | Author |
---|---|---|---|
#2 | geocoder-dumperpluginmanager-warning-2937323.patch | 840 bytes | welly |
Comments
Comment #2
welly CreditAttribution: welly at Fat Beehive commentedComment #3
welly CreditAttribution: welly at Fat Beehive commentedComment #4
boshtian CreditAttribution: boshtian at Agiledrop - Your Trusted Drupal Teammates commentedWe were just investigating this issue and when we wanted to file an issue, we saw that you already did the work. :)
I confirm that after applying patch, the geocoding is now working again.
Comment #5
maaty388 CreditAttribution: maaty388 commentedThis patch is working.
Thanks
Comment #7
Pol