The EventFinder module requires CiviCRM and some default configurations to work. With the new CiviCRM 1.3, defaults that were included in the CivicSpace installer are no longer functioning.

You can see the defaults in the picture below. In 0.8.2 CiviCRM 1.2 had the CiviCRM profile selected, now it is not selected.

Kieran

CommentFileSizeAuthor
screenshot13_0.jpeg75.27 KBAmazon

Comments

Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »

Will look into this.

M

onionweb’s picture

onionweb commented

you can't select a civicrm profile for events. it always defaults to the default civicrm profile and ignores the profile chosen in admin/settings/eventfinder.

Anonymous’s picture

Anonymous (not verified) commented

I think this has to do with using the latest CiviCRM release, there was a time when you really could only work with the 'default' profile the platform shipped with. I am looking into it and should have some sort of a patch worked out soon.

M

Michael Brunelle@civicspacelabs.com’s picture

Michael Brunelle@civicspacelabs.com commented
Category: task » support

Any update on this? The default profile bug renders event registration somewhat worthless to users that haven't registered with your site: even if the default profile includes the CiviCRM e-mail adderess data field, new addresses cannot be collected by eventfinder registration b/c they're assumed to have been collected by the user creation routines...

Amazon’s picture

Amazon commented
Status: Active » Closed (won't fix)