Drupal

The CiviCRM Drush integration recently got a fairly major refactoring (issue CRM-9986), and should be available with the CiviCRM 4.2 release.
The main user facing change is that "drush civicrm-cache-clear" has been replaced by integration with the standard drush cache-clear command. You can see it in the options by running "drush cache-clear", or call it directly (this time using the alias "cc") using the command "drush cc civicrm".

At CiviCon, Gunner from Aspiration Tech facilitated a session with the entire community soliciting feedback, discussion and comments on the project. It was a good opportunity for everyone to give feedback on the state of the project, things that we are doing a good job with, and things that we can improve. We ended up doing a collaborative grouping of the feedback in various categories and sorting the comments.

Some of the positives that are worth highlighting include:

We had our 4th CiviCon in San Francisco a few days back. It was a very well attended event with very high quality sessions. We hope to have most of the videos online in the next few weeks. I'm quite keen on watching all the sessions that I had to miss. There were lots of highlights for me personally during this event, i'll make an attempt to recreate some of them here:

• The quality of the talks I attended were very high. Most groups are using CiviCRM very creatively and pushing the limits in multiple ways. We need to continue on increasing the extensibility thus giving developers / integrators more choice.
• The quality of the Birds of a Feather session was very high. Unfortunately these were not recorded. Jim's talk on how they use Civi for theatre registration and season passes at BACT, Peters talk on CiviMobile and Rachna and Jason's talk on PopVox, CiviCRM and Advocacy were super impressive. A blog post on Popvox and CiviCRM is coming soon, definitely opens up the wide world of advocacy and contacting your congress-person/senator for CiviCRM users.

Greater Manchester Centre for Voluntary Organisation (GMCVO) require an ICT Officer who can customise and develop open source software (PHP), work with hosting environments (Linux), and install and configure open source databases/websites for external organisations (Drupal/CiviCRM).
For more information about the post and how to apply visit: http://www.gmcvo.org.uk/vacancy-part-time-ict-officer-gmcvo

<Cross posted from Advomatic.com The code blocks will be easier to read there.>

Sometimes after launching a new site our clients find that there are fields and features in CiviCRM that they don't use.  We are working with a client that wants to remove all fields and features that aren't useful in order to simplify their user interface and make it easier to use.  This includes things like SMS features, email signatures, and demographics.  There are also several fields that they wanted renamed to be more consistent with the legacy system that they migrated from.  To fulfill this requirement I used a combination of template overrides, and CiviCRM's translation system.  

First up I should point out that if you do want to go down this path you need to make clear to the client that this will take a fair amount of effort up front (hopefully less for you now that you are reading this recipe).  Additionally, if/when you upgrade CiviCRM these customizations will need to be reviewed at the very least, and possibly even re-done to some extent.  So while this customization will make things more usable for CiviCRM administrators, it will add cost to both the initial site build, and to ongoing maintenance.  

If you've recently upgraded to CiviCRM 4.1, you'll need to upgrade your webform_civicrm as well. Versions 2.3 and below are not fully compatible with Civi 4.1. Version 2.4 is, and will be released in the next couple of days, especially if I get a few comments on this post from people who have sucessfully tested it! The latest -dev is stable and working, so please feel free to download it and try it out on your 4.1 site!

Note: webform_civicrm 2.4 is not backwards-compatible with older versions of CiviCRM, and should only be used with 4.1.x

There have been several hook() or Drupal module based solutions for "members only" pricing for events or for other 'discounts' related to memberships.

I take a different approach by using only jQuery and blocks in Drupal 6.  For those who use Drupal 7 you can adapt this code with Drupal 7's new javascript namespace and Joomla folks could even make use of this in custom TPL files.

Hi,

So as every consultant, there is a bit of new projects, maintenance, stuff you do for free for the community, new ideas, meetings, pre-sales, funky developments & the dreaded admin part (invoicing/timesheet).

CiviCRM had a very successful year in 2011. The project grew significantly in different areas and we made progress on a few long standing issues. The biggest change in our opinion is the increase in community involvement across all aspects of the project.

• We had 1 major release  which supported Drupal 6, Joomla 1.5 (v3.4) and Drupal 7, Joomla 1.6 (v4.0). We also had 13 minor releases in 2011. A chart of the types of organizations using CiviCRM can be found here along with the usage of various components.

• We held the 2nd North America CiviCon in Chicago which was organized by Young-Jin Kim from  Emphanos. The 1st CiviCon Europe was held in London and organized by Michael McAndrew, Third Sector Design and David Moreton, Circle Interactive. Each of the conferences had 100+ attendees. We also held user and developer training, and code sprints around these conferences