If you are using Drupal 6, you have a vested interest in extended Drupal 6 support for CiviCRM 3.4 until spring 2012. If you are staying with Drupal 6 because of budgetary reasons or because Drupal 7 doesn't yet support all the modules you need for your site, this is vital for you. You will make sure your 3.4 CiviCRM/Drupal 6 setup remains healthy and safe.
Please donate here, if you haven't already.
Last Friday we had the first CiviCRM marketing meeting on irc. Nine people contributed and a couple more were unable to attend due to being on trains or planes. It felt like a good starting point and some encouraging thoughts came out of it. This is a quick synopsis.
CiviEngage is a Drupal module that (in the next release of CiviCRM) automatically configures CiviCampaign to make it easier to get up and running by setting many of the configuration tasks with sensible defaults.
Ah yes, next April 2012 is NTEN again and voting is open to vote for sessions you'd like to see at NTEN. There are 2 fantastic sessions, so please support the CiviCRM community and vote:
Hi,
We have continued the research to see how often someone tweeted about organisations that happen to use CiviCRM. We analysed 2023 tweets by 724 users about 175 sites. Not a lot of new sites since last month, but a lot more tweets.
A couple of issues have begun to sting us repeatedly and I see others raising same issue.
#1
Getting a Default Header/Footer used in the SysTplMsgs
SysTplMsgs (System Template Messages) are found here /civicrm/admin/messageTemplates?reset=1)
Hi,
Two weeks already since civicon, the dust has settled and Amy Dobbs and the team at skillmatters have filmed and uploaded the sessions.
Over the past few years the administration menu has grown quite a bit. Although I use it quite often, I find that I'm sometimes unsure where to look for a particular configuration option. We've heard the same comments from both experienced and new users - so Xavier Dutoit and I thought it would be a good idea to take a stab at re-working the menu structure. The goals of the re-organization are:
Like many others who have no doubt gone before me, I found myself spending a large chunk of time this week finding and merging duplicate contacts. Civi's deduping UI has gotten a lot better lately, and I love having the ability to go through it more quickly than before. But deduping is only as good as the queries it runs, and of course prevention is better than cleanup.
Here are some observations of how all those dupes in my DB got created:
