Support for content_profile

VIEWS BONUS MODULE can export all views to various CVS formats (it produces a kind of feed).
Views can show and filter CONTENT PROFILE fields as well as fields of CORE PROFILE.

:-)
-ksc-

The Views_Bonus module's CSV exporter works perfectly. It might be worthwhile to add a comment on the project page to suggest using it?

Due to having all of the extra fields available, and being able to give non-experienced site editors access to this vs Views, this is still worthwhile. I'm working on a preliminary patch for a client, will upload later tonight.

Here's a patch to try out for size. I've tried to keep it flexible, able to support field groups, multiple profile nodes, and includes two hooks to allow other modules to extend.

One other change I made was to remove the requirement for the Profile module as it isn't needed. The module now works with the core Profile, the contrib Content_Profile module, both or neither.

Work sponsored by Bluespark Labs.

ToDo:

• Documentation for the hooks.
• Possible code cleanup.

See #894840: Support for profile_csv for why it might need some work.

Updated patch that changes all optionselect fields to be output as a comma-delimited string, e.g. "orange, banana, cumquat".

Updated patch that changes all optionselect fields to be output as a comma-delimited string, e.g. "orange, banana, cumquat".

I couldn't get this to work. I got the following errors though:

# warning: Invalid argument supplied for foreach() in profile_csv/profile_csv.module on line 599.
# warning: Invalid argument supplied for foreach() in profile_csv/profile_csv.module on line 599.
# warning: Invalid argument supplied for foreach() in profile_csv/profile_csv.module on line 610.
# warning: Invalid argument supplied for foreach() in profile_csv/profile_csv.module on line 648.
# warning: Invalid argument supplied for foreach() in profile_csv/profile_csv.module on line 599

You need to add a check to ensure $value is array before doing a foreach.

However the main reason it's not working is that $field['name'] is being using and that is set to something like 'profile_csv_param_profile_field_profile_phone' which doesn't exist in the node object.

Thanks for the review, Stella, I'll see about testing it some more and re-rolling.

FYI I'm rewriting this to be much cleaner, should have something in a few days.

subscribing

Hi Damien - did you ever complete the rewrite you mentioned? Thanks!

Haven't gotten back to work on it since October, am intending getting back to it in a few weeks.