Okay, I'm double-posting today in case you don't find this buried in the forum. My forum posting contains all of the details regarding a custom hack written for a client to automate 7 renewal email reminders based on expire date.
I do hope you find this useful. http://forum.civicrm.org/index.php/topic,6176.msg98034.html#msg98034
- Annalee
Hey gang sorry it's taken me so long to get back to you but we've been busy slogging through a few outstanding issues. For those of you who are currently in the throes of your data conversion here are a few quick words of advice.
1. Set up a local site for your data conversion so you don't run into any restrictions on how many records you can import at one time on your server, otherwise, you will spend a lot of time creating many, many small text files.
Hi All
Here at The Leukaemia & Lymphoma Research charity, a lot of events have participants who may be children or where a team leader is booking for all team members. The current implementation of CiviCRM insists on the inclusion of an email address for all participants, which is a problem in the two scenario's. Some of the teams are quite large and each team member has specific settings which need to be captured, such as t-shirt size, route etc.
We have continued the research to see how often someone tweeted about organisations that happen to use CiviCRM. We analysed 5988 tweets by 3478 users about 574 sites.
The team is excited to announce the third beta release for 4.1 with support for Drupal 7, Drupal 6, Joomla 1.7/1.6, and the integration with Wordpress 3.3 (wohoooo!!!).
Thanks to a successful Make-it-Happen campaign the 4.1 release comes with a much improved and super flexible approach for running Civi's critical back-ground processing tasks. These tasks include keeping membership statuses up to date and sending renewal reminders, sending scheduled CiviMail mailings, sending pledge payment reminders, and more. I've spent the past 10 days testing and documenting the new "consolidated cron" functionality, and the good news is that I think it fulfills the promise of providing a convenient and friendly way to administer and run all the required tasks for a site.
The "bad" news is that these improvements are NOT backward compatible. The set of PHP scripts which were previously used to run these tasks have all been deprecated (and moved to a 'deprecated' directory). This means that all CiviCRM-related cron jobs will stop working as soon as any site is upgraded to 4.1. (Yes, a loud warning will appear on the screen at the end of the upgrade process.)
Notice to non-developers: This post is about how some functionality in 4.2 will be implemented in code and in the database, with very minor changes to anything visible through a browser. If you're not a developer, it probably won't interest you.
The first North of England meetup took place on the 12th of January 2012. It was really well attended with fifteen attendees. The attendess consisted of people interested in CiviCRM, users, implementers and developers. Some of these people had travelled quite a long way to get there and we were really pleased to see them.
For anyone who is using pricesets and/or automated recurring contributions with a payment processor, you will probably enjoy the 3 custom searches that you can download here
One of my favorite features in CiviCRM 4.1 is the improved support for custom tokens via hooks. It's really opened up the possibilities for building some great functionality and new workflows in CiviCRM. If you already know what tokens and hooks are, skip down to see some cool examples.
