Jump to:
| Project: | Node Profile |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Not sure how to explain this in a clear way as english isn't my native lang, but... I am looking at the user_import module, to extend it for own needs, using nodeprofile rather then the core profile module. I have a small problem though to find were to start pulling for tables and fields to import data to e.g. content_types set to use as nodeprofiles. Sure I could hardcode my own preset values, but then my work would be useless to others...
I have an idea of what I am looking for, but not sure how to pull it together. I got it that far as in Admin->Content Man.->Content Types the type is set to be used as Nodeprofile, so that's obviously were to start. But as far as I been able to uderstand this setting is only saved in a variable type nodeprofile_contenttypemachinename = i:1 (or i:0 if not nodeprofile) - is this correct or is there a more "convenient" storage of this data?
I am aware of Nodefamily and Usernode etc. as well being a potential part in this, but right now I am more at the stage to find the best start angle to attack this, so to speak.
Comments
#1
hm, perhaps have a look at the functions is_nodeprofile() and nodeprofile_get_types() to get the content types, that are uses as profiles. It would be great if you could share your solution, as importing profile data to nodeprofile is often wanted by people!
#2
Ok that seem to be what I am looking for... I am just thinking now though if the best wouldn't be to make a new module, as making an import to a node profile probably differs that much from a core profile that the two together will complicate things. There has been requests for this in User Import and the maintainer has said he will do it (long time ago) but I am a bit worried it never is going to happen as there are many issues with status Active, and very few fixed/closed. It would be my first module in such case, and I need this functionality so better make it happen...
Of course I will share my work ;-)
#3
Have you gotten around to making this work? I'm very interested in such integration.
#4
Any progress on this?
#5
See http://drupal.org/node/197796