The registration fields appear only when event details are viewed from the EventFinder search results (or my events, etc.). If registration is active for an event, these fields should appear when the event is viewed from the calendar, home page, or anywhere else it appears.

Comments

Anonymous’s picture

Anonymous (not verified) commented
Title: Registration fields do not appear unless found through EF » This is actually a feature request
Assigned: Unassigned »
Category: bug » feature
Priority: Critical » Normal

This is actually a feature request, EventFinder is built to work completely independently of the Event system. We have limited EventFinder's registration features to EventFinder views mostly as a way of limiting confusion with other modules such as volunteer.

I am thinking this could be done as something administrators could configure, but there are some usability issues involved. For instance, how does a user get back to the calendar view after registering for an event? There are a lot of things to think about in how this would be implemented, and I fear there are no simple solutions.

M

sleary’s picture

sleary commented

To me, it is a bug and not a feature request, but whatever. My issue is that all my organization's events happen in the same general location, so there's no need for the finder, but we DO need (desperately) the registration feature. Thus our people are going to the calendar to find events, but once there they don't see the registration details like we need them to.

Perhaps these should be separate modules?

bluejay’s picture

bluejay commented
Title: This is actually a feature request » I'm agreeing with sleary

I have an organization that will every so often have an event that registration is required for. All events are located in the place/buildling/room. I would think it would be great, fabulous, and easy on the eyes for them to be able to register for the event from the calender or blog entery or somethign where they don't have to go search for the event!

And I'm having my own issues with the Event Finder...

leoklein’s picture

leoklein commented
Title: I'm agreeing with sleary » Re: I'm agreeing with sleary

This is actually a feature request, EventFinder is built to work completely independently of the Event system. We have limited EventFinder's registration features to EventFinder views mostly as a way of limiting confusion with other modules such as volunteer.

See this is what I don't get. Looking at the page on "[EventFinder] Integration with CiviCRM...", it seems like almost as much effort is going into event registration as event-finding. It'd be great to see the features mentioned there built not around finding events but around the events themselves!

As things stand, there are at least three modules, EventFinder, Volunteer and RSVP, that attempt to handle people signing up for events. This can be frustrating for many of us who need this kind of function. While I'd personally like to see the RSVP function expanded out in this way, I think having three different, largely incompatible, ways to get people to sign up for an event is a bit much.

LEO

P.S. This isn't to criticize EventFinder which for example at a site like this is a joy for to behold.

Geary’s picture

Geary commented
Title: Re: I'm agreeing with sleary » Registration fields do not appear unless found through EF

Restoring original title.

Anonymous’s picture

Anonymous (not verified) commented

If I understand the issue properly, there are really 2 things people want to see here:

1) Global links to eventfinder registration

2) Some clarity around which registration system (eventfinder, volunteer, rsvp, etc.) should be used

Without trying to sound contrite, I really do stand behind my previous comment that EventFinder works correctly and adding links to events outside the eventfinder system is really a feature request. This was done on purpose so that it would not interfere / confuse people using other forms of registration. EventFinder itself includes a substantial number of themeable functions allowing users to override registration settings altogether so, for instance, you could replace registration links with links to the RSVP system. Beyond that, someone could easily include links via their theme to the eventfinder system for event-enabled nodes.

That said, the problem really is with out of the box functionality, not with eventfinder per-se. There is nothing special about registration links in eventfinder, and that logic could be easily duplicated at the theme level to allow users to subscribe to events from anywhere in the system. Perhaps it is worth looking into how more functionality could be added around event registration, and maybe ways of automagically configuring eventfinder to use the volunteer or rsvp systems. I am not certain, but it would seem to me there is nothing preventing a savvy developer from configuring an entire site to use eventfinder, rsvp and / or volunteer registration as is.

As far as things being incompatible, I really have to ask what people are expecting from these three modules in terms of interactivity. There are a wide variety of needs in terms of how registration should work, and I receive a lot of feedback from organizations looking to align eventfinder with their specific business needs. The question, in my mind, is not how to integrate these modules more fully, but how to capture the ways people do registration on the web. It looks to me like what is needed are several flavors of event registration that can meet broader goals and maybe serve the needs of most of the groups out there.

The trouble with that is that with each new registration system makes eventfinder more complex, which actually limits its usefulness for some developers. So there is a balance to be struck between features and usability, and I guess I am just having to think about it. What would be helpful is details on the actual 'compatibilities' people are looking for.

M

Zack Rosen’s picture

Zack Rosen commented

This patch

http://drupal.org/node/39619

...attempts to address this Issue. Please test and give feedback.