Yes, first item of business - the official announcement of news that has been showing up here and there already. The upcoming release, that was previously referred to as 2.3 has been renamed to 3.0. :-) After long discussions we decided that the return of CiviReport, together with many other changes and improvements that have been introduced in this release deserve a major version number. Robust reporting abilities, introduction of major changes in thhe user interface, and an abundance of other new features - we think it's a big step forward and want to underline it.
The whole team has been busy finishing up the functionality for the 3.0 release, but we're getting to the end of the path. The first alpha release for 3.0 is scheduled for Wednesday, August 5th (which is one week from now). We estimate that the first beta is going to be released 4 weeks after that, on August 26h.
There is...Read more
- Reduce the number of "clicks" needed to move around in CiviCRM
- Allow sites to optimize CiviCRM navigation for the way they use it
- Find Contributions: Instead of clicking the CiviContribute link, waiting for the dashboard to load, then clicking Find Contributions .... just click the Contributions menu and select Find Contributions
- Groups represent a relationship between "you" (i.e. one of the owner organizations of that Civi instance) and a contact (i.e. a member, newsletter subscriber, media contact, alumni, etc.).
- Relationships represent a relationship between 2 external contacts.
As mentioned previously, we’re introducing quite a few new CiviEvent features in CiviCRM 2.3. Most of them are still undergoing our internal CiviCRM QA cycle, but do check them out at our CiviCRM 2.3 sandbox if you’re interested (there is still time for some minor fixes to accommodate your use-cases!).
CiviCRM 2.3 introduces the concept of wait lists, where participants who registered after a given event was full are placed. These participants are informed before their initial registration that the event is full, and if they continue their registration process, they are put on a waitlist. Once the event gets some free spaces (because some other participations expire, or participants cancel their participation, or are removed by an admin, or the event gets more spaces…), a cronjob-based script makes sure that the participants from the top of the waitlist (first-registered-first) are moved to pending...Read more
Greetings and Salutations :-)As some of you may already know, the existing "Greeting Type" feature in CiviCRM is pretty broken. You can't use it to specify a greeting for either email or printed / postal communications (no token or export support). In addition, as described in Tony Guzman's recent blog on Better Household Management - it's not designed to support a number of key use cases. So... Tony and the folks at Dharmatech have been working with us to figure out a flexible WORKING solution which can handle the simple cases ("Dear Dave") as well as the more complex cases ("Dear Dave and Bob", "The Honorable Scout Conberg", etc.). If you haven't read Tony's blog yet - start with the Greetings and Salutations section there. Then, if this is... Read more
CiviCRM Multi-Org refers to the ability to support multiple owner organizations (usually a hierarchical structure of umbrella orgs and sub-orgs or local chapters) and keep some data siloed in each org while allowing other users to aggregate data across orgs too. It has been been a tough nut to crack. But I and the organization I work for (The Public Interest Network) are committed to getting it working in CiviCRM 2.3.
At the recent developer camp in San Francisco, we had 2 great brainstorming sessions on multi-org, which resulted in this wiki page: http://wiki.civicrm.org/confluence/display/CRM/Multi-Organization+Support+in+CiviCRM.
For many multi-org use cases, one of the currently-possible options listed on that page could very well work. However, I need a little more flexibility, and I also want better multi-org support "out-of-the-box" (the current options involve...Read more