Adding extra node fields to the export
NancyDru - September 16, 2009 - 14:13
| Project: | Node Export |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Wow, it turns out that a node module can not only make its extra fields available to NE easily, it SHOULD be doing it. I stumbled upon http://www.lullabot.com/articles/great-pretender-making-your-data-act-field and tried it in Web Links, and the extra fields are now being exported. I have not yet tried an import.
If you add this link to your project page you could save a lot of developers a lot of time. Doing what you should be doing anyway can make things a lot easier.
#1
I just did an import and the extra fields seemed to be handled fine. (I would like to see some improvements to the import settings form though.)
#2
+1 I dig this idea! How about having a compatibility chart, wiki? Maybe a documentation page?
#3
Probably a good idea.
#4
I don't understand this issue one bit. I don't see why this is a node export problem. I don't think this is the place for tutorials on how to make a node module.
#5
How come this function is not documented on drupal.org? I think this should start with the drupal.org documentation team and the popular node modules. I don't want to be responsible for keeping this info up to date, and I'm uncomfortable about linking to 3rd party companies like lullabot.
I think we need some answers from the documentation people about this before we even try to point people towards such a solution anyway.
#6
I agree that this is certainly outside the scope of this module. And I agree that there needs to be documentation on DO, probably on both DO itself and on api.drupal.org (at least as part of the example module). Everyone on DO is a "documentation people." I will try to get something written up in the next few days. I wanted to mention this here until I can do that and let people know that there is a relatively easy (and "right") way to make their modules work with NE.
#7
OK let me know if you post about this anywhere I would love to see the discussion.
I was under the impression there was a documentation authority of some kind we could turn to - but perhaps the broader D.O. community in general should be aware of this, such as the people who frequent this queue: http://drupal.org/project/issues/documentation?categories=All
#8
I've been know to visit that queue and am a member of the Docs team. Pretty much anyone can join the Docs team. The primary benefit is that you get a less restrictive input filter.
#9
Just realised why this isn't documented anywhere - this hook depends on the CCK module so whilst CCK does give you an easy way to attach data to a node, it's not the official drupal api native way of doing so and I can't recommend it as the way this is to be done - most people wouldn't make their module rely on CCK if they didn't have to, but I will keep it in mind as an option if this sort of issue comes up. Hopefully by drupal 7 this will be a different story.
#10
You are correct, it does depend on CCK in 6.x (should not in 7.x). I posted this not to be a recommendation, but to let people know that there is a simple way to add exportable fields if they have CCK.