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 would be nice if node import supported the Geo Field from the geo project (http://drupal.org/project/geo) out of the box.
Comment | File | Size | Author |
---|---|---|---|
#3 | node_import-707760.patch | 3.25 KB | ahtih |
Comments
Comment #1
NoahPollock CreditAttribution: NoahPollock commentedCan the Geo Field be added manually after import?
Comment #2
Doud CreditAttribution: Doud commented+1 subscribe
This feature would be very nice !
Comment #3
ahtih CreditAttribution: ahtih commentedI added functionality to import Geo Field. Here is a patch for DRUPAL-6--1 branch, including updated documentation.
It supports input as WKT or Lon/Lat, as specified in CCK settings for the field (configured in /admin/content/types , not when importing).
Multiple values per field are not supported; I'm not sure if this should be done, as many other supported/*.inc files have no special support for multiples either and are still marked as "fully supported" in node_import docs.
Node preview phase does not work (get warning messages instead of data), this is due to Geo module's own bugs (Geo Field preview does not work even without Node Import); but ignore the preview warnings, actual import works fine.
Pls test&review, I am fairly new to Drupal so perhaps did not implement everything correctly.
Comment #4
salvatore_severo CreditAttribution: salvatore_severo commentedI think there is a limit on wkt over 128 chars. There is a way to up this limit?
Comment #5
ahtih CreditAttribution: ahtih commentedI'm not sure. There is no such limit explicitly in my patch above. But perhaps some other module is limiting WKT size. If someone has time to debug this, it would be nice. Myself I don't need longer than 128 chars WKTs and don't have time to work on it now.
Comment #6
ahtih CreditAttribution: ahtih commentedMaintainers, any chance of commiting this?