Event Finder should ship with better default settings. When you first turn it on you have to futz too much with it too make it obvious for end users how it is supposed to work. Here are my suggestions:

* Enable Event Type Searches - defaulted on
* Enable Location Proximity Searches - defaulted on
* Search Description - defaulted with boilerplate text
* MyEvents Description - defaulted with boilerplate text
* Host an Event Description - defaulted with boilerplate text
* Send Message to Registered Users Description - defaulted with boilerplate text
* Registration List Description: - defaulted with boilerplate text
* Enable EventFinder to send a confirmation mail to people who enter events - defaulted on
* Enable registration confirmation email - defaulted on
* Email Name: - defaulted to the site ownders name name
* Email Address: - defaulted to the site owners address
* Host Email Subject Line: - defaulted with boilerplate text
* Host Email Body: - defaulted with boilerplate text
* Register Email Subject Line: - defaulted with boilerplate text
* Register Email Body: - defaulted with boilerplate text
* Enable Saved Searches - defaulted on
* Maximum Saved Searches per User: - defaulted with boilerplate text
* Saved Search Description: - defaulted with boilerplate text
* Create Saved Search Instructions: - defaulted with boilerplate text
* Saved Search Email Body: - defaulted with boilerplate text
* Saved Search Event Description: - defaulted with boilerplate text

If I get some time to do this I will make a SQL dump of the settings and some text I think up later. If you want to tackle this go check out the defaults for volunteer module.

http://drupal.org/node/20086

Comments

Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »

We can certainly look at these items.

- I would prefer not to set the default value for 'enabling saved searches' to on. The email sent by saved searches does require a good bit of configuration in order to properly interoperate with the events module. Since an event can be of any node type, and thus possess any variety of fields and values, someone has to reconcile the differences in order to make these mailings meaningful.

The same logic applies to the other types of mailings as well, although probably to a lesser extent. If anyone has ideas on how to best tackle these problems I am certainly open to ideas.

- The event type searches should probably only default to 'on' if there are event types configured in the system. Because of the fact EventFinder interoperates with the event and location modules, these search fields are unpopulated unless at least one node type is configured for events.

- We can certainly provide default boilerplate text for the various descriptions.

M