Back again :-)
Over on http://drupal.org/node/274742#comment-895756 I mentioned that the 'trackfield_datasets' table was empty for the nodes I was adding trackfield data to. I have now discovered why. When I create a new content type and add trackfield to it, it works fine. But I initially started by adding trackfield to an *existing* content type and adding trackfield data to *existing nodes*.

The logic in trackfield_field, op=update only checks to see if the node has old vid and doesn't check to see if the dataset for that node has been added to the database. The db update fails silently and although the trackfield data exists in node, no map is rendered because no dataset rows exist.

I don't have a patch right now though I could probably put one together - please let me know if you want more from me.

Comments

raintonr’s picture

raintonr commented

Thanks for the input on this.

I have noticed myself that things are not quiet right when you add fields to content types and am not quiet sure how one is supposed to handle this.

Eg:

Let's say a site admin adds a vanilla 'Track' field to the blog content type. Users can now enter data along with their blog entry but they cannot see it because no visualisation field has been added.

Several users create blog entries and attach data, but they cannot see it.

Now if the site admin adds the 'Track Graph' field one would like to have existing data show up automatically. However it does not.

In this example, although the CCK module handles creation of the dummy 'Track Graph' storage when the admin adds that field it is not populated and therefore the field formatter isn't called. Users have to edit their content and simply re-save in order for the 'Track Graph' field to show up as this causes a value to be saved in the dummy storage.

I'm not sure if this is a related issue, but it's certainly one I would like to fix.

Either way, if you can give a clue (or patch - even better) for the original issue here that would be very useful, thanks.