CiviCRM Community Forums (archive)

Hey,

Basically, it's great that you can now determine which statuses are counted so on the registration form you ask people if they are a "yes, no, maybe" status. But when you expose the participant status field within a profile, every status appears to the registrant. This is not ideal since some statuses are only for administrative purposes.

What would be your suggestion? Marking statuses with public/backend flag and exposing only those public ones in profile participant field?

Also, it would be great to be able to rename some of the core statuses to call "registered" something like "yes, i'll be there."

This can be done directly in the database: find all the participant statuses (select * from civicrm_option_value where option_group_id = (select id from civicrm_option_group where name like 'participant_status')) and modify the label for appropriate one.

Thx,
m

Yes. That is what I propose. Similar to within manage groups you can set a group's visibility as public user pages or user and user admin only. And if the groups' field is within a profile, only those groups with the appropriate visibility will show to anonymous users.

I drill down some more, since I would like to understand the suggestion well before we file an issue: did you mention "anonymous" user only to underline the use of profile, or do you have something more in mind? If this feature gets accepted, I would keep it down to simple rule for now - if participant status field is exposed via profile, only public statuses are displayed, doesn't matter if the profile is accessed by anonymous user or registered user. Would you agree?

Ok. I propose here status names be configurable in a future version to make it easier for non-techies (our clients)

Ok - assuming you agree with my suggestion above, could you file two "Improvement" issues in our issue tracker, describing wanted outcome briefly and referring to this forum thread? :-)

Thx,
m

Great, thanks. Of course, as always - since I forgot to mention this earlier - patches and contributions most welcome. :-)

Thx,
m

Wonderful. That would be very helpful, since we just decided to make 2.2 a quick release (scheduled for Dec/Jan), so we won't be able to fit in too many new features in it by ourselves.

Thx,
m