I can't figure out what is this Content module required ? Is this a typo or where to find it ?

Comments

tmcw’s picture

Category: bug » support

OpenLayers CCK for Drupal 7 is deprecated, and will not be upgraded. Please read the release notes.

okokokok’s picture

I was also a bit confused by dependency on Content. It could be good to add the word "deprecated" to the module description.
(Currently "Provides CCK fields and widgets through an OpenLayers interface.")

tmcw’s picture

The module will be simply removed in the future.

zzolo’s picture

Title: OpenLayers CCK requires Content module » OpenLayers CCK deprecated in Drupal 7
Category: support » task

So, I think this a good direction. Hopefully this will be picked up in another module just to support people going forward and upgrading from Drupal 6.

I have changed the title so that people looking into this (and I am sure lots of people will) can tell the action from the title. Also, I have updated the project page with this information since it is pretty important for people possibly upgrading from D6.

So, the current To Do is to actually remove it form the D7 codebase.

mcaden’s picture

Why is OpenLayers CCK still in the 7 branch at all? I'm surprised removing it wasn't one of the first things done as a part of the port in order to avoid confusion.

I would like to know if there will be a replacement field though. I'm looking into using OpenLayers and OpenLayers Geocoder on a current project. I've started porting geocoder but it relies on the wkt field in CCK. Will there be a field module to replace the wkt field or will I need to make this myself? My knowledge of D7 fields/widgets is quite limited and my knowledge of geocoding, openlayers, maps APIs is even more so at this time.

tmcw’s picture

@mcaden: I simply forgot to remove it and haven't worked on Drupal much since.

There will be a replacement field module if someone writes it, but it should be handled in a different project. OpenLayers CCK has been popular but it's architecturally weak and CCK is not a very good API to build anything serious upon.

And, it won't be written by me. My time on Drupal is very limited because I'm no longer regularly doing Drupal work of any kind, and when I did have time in the space, I never once used OpenLayers CCK myself.

mcaden’s picture

I need it and would write it myself but I've never worked with CCK so I'd be hard pressed to duplicate the functionality.

I worked some on porting the geocoder module but all I ended up with is a text field that does autocomplete from google maps and stuffs lat/long data into a hidden field on form submission. I have no idea how to interface with the mapping.

spydmobile’s picture

Well, it is my understanding that the only way to use Openlayers as a data input, is to have CCK, OL CCK, now that OLCCK is deprecated, Openlayers is no longer any use to us who used it or need it for input. What are you suggesting folks do to input data?

@ mcaden maybe dont use CCK if you dont know it, instead perhaps add another kind of field and make Geocoder use it.. just a thought

tmcw’s picture

Well, it is my understanding that the only way to use Openlayers as a data input, is to have CCK, OL CCK, now that OLCCK is deprecated, Openlayers is no longer any use to us who used it or need it for input. What are you suggesting folks do to input data?

Contribute to the module? The maintainers are all quite busy and have never been avid users of the OpenLayers CCK module. It's an unfortunate scenario, but the only solution is contributions: this is an open source module that readily accepts patches and adds maintainers.

zzolo’s picture

And just to reiterate. We are not opposed to someone taking the code, porting to D7, and putting into a new module. We just feel that data input is not in the scope of this module. We understand this is a bit of an inconvenience for a lot of people, but we feel its important to push geo data input mechanisms to other projects, as this module focuses on visualization and display.

mcaden’s picture

@spydmobile - by not knowing CCK what I meant was I don't know how the CCK module does what it does, and I don't know OpenLayers enough to start from scratch. What I did for the openlayers geocoder module was to make a text field that autocompletes and does the geocoding, but without any actual mapping or storing the address as anything other than a simple lat/long and an address it's pretty useless.

zzolo’s picture

Status: Active » Fixed

I have finally removed the openlayers_cck module from CVS.

phayes’s picture

Hi all,

I'm going to need CCK in D7, so i'll do the port and start a new project for it. However, I would like to have a co-maintainer as I don't have the time to give such a module the love and attention needed to fully maintain it. If anyone would like to be a co-maintainer let me know. I'll post the link to the project once I get it going (hopefully later today).

Karsten.S’s picture

Not sure what OpenLayers CCK offert that is not doable in GeoField (github). What about joining that project, which is already useful to a degree?

phayes’s picture

Thanks for the link karsten. I will see if the devseed is interested in adding wkt support to geofield.

phayes’s picture

For anyone who is interested, I've taken karsten's advice and expanded geofield: https://github.com/phayes/geofield

Thanks everyone

zzolo’s picture

Hey @phayes. Awesome work. Just wanted to ask if this means there is an upgrade path from OpenLayers CCK 6.x to Geofield 7.x? Not that there needs to be, but I am sure people will ask.

phayes’s picture

Thanks @zzolo. An upgrade path is not on the radar for me at the moment. But yes, with the wkt now in the mix, it should be totally possible.

michaelsilverman’s picture

Downloaded the Geofield module and have it working with Open Layers to capture a point on a map. The map displays fine in Edit mode but I cannot get it to work in View mode. Also trying to work with views and cannot get the locations to display on a map.

Not should if I am doing something wrong or if these features are just not available in the version 7 modules yet.

zzolo’s picture

Hi @michaelsilverman. If this is a specific issue with Geofield, you should use the issue queue (or equivalent) for that, as this is for Drupal OpenLayers, and specifically just to discuss how CCK is leaving this module. If you find that it is something wrong with this module, please feel free to add to or create new issues.

phayes’s picture

Hi @michaelsilverman,

I've added an issue tracker to my github repository. https://github.com/phayes/geofield/issues

Please use that to post issues related to this module for the time being (until we are far enough along to create a d.o project for it)

aristeides’s picture

Subscribing

phayes’s picture

Hi all,

We've sprinted on this at Drupalcon and will be sprinting more tomorrow. But here's the new geofield module: http://drupal.org/project/geofield

Tada!

This new field will also be forming the base of the new location module (maintained by bdragon)

aristeides’s picture

perfect.... :)

Status: Fixed » Closed (fixed)

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

batje’s picture

Component: OpenLayers CCK » OL API

If you come here via google: there is now a migrate module to move your data from openlayers_cck to geofield

http://drupal.org/project/openlayers_cck_migrate