Whether you're just getting started with customizing CiviCRM or you already think you know everything about it, I invite you to spend a few minutes playing with the new API Explorer in 4.6. You'll be glad you did.
End-user tips and tricks go in this category.
CRM Data plans refer to documenting agreements on representation, format, definition and structuring of data. Current and future CiviCRM users can utilise it to increase efficiency, knowledge creation and interoperability with other systems.
In order to optimise and future-proof the CRM system, the data structures, in addition to the data itself, need a good re-work. There are two main steps to the process:
My first exposure to CiviCRM was around 2009. I was working at Freeform Solutions, Canadian IT nonprofit organization that supports other nonprofits by providing technology support. We were looking for a CRM system that would support an HR organization that had a few thousands contact records. They needed a software that would allow all staff to access the same contacts database so that all staff members can update the records, send newsletters and other mass mailings and to run reports on the collected data to know what type of clients they work with.
This goes out to CiviCRM users (yes YOU too!), admins and developers.
A key productivity tool in my day to day life is a set of Q&A websites called Stack Exchange. They have different sites for all sorts, from programming through to parenting(!). Typically, I'm on the programming ones usually, but stay with me, this isn't about to get technical.
Chicago agency SocialRaise explains how to combine a $120,000 Google Grant with the power of CiviCRM. Imagine having an online marketing budget of $120,000 handed to your organization. That, in combination with landing pages created with CiviCRM and the tools to segment and organize your communications, will enable your nonprofit to reach more people, increase volunteers and drive fundraising efforts.
Don't ask for your privacy. Take it back.
Reset the Net is a campaign to improve individual and organizational privacy against mass government surveillance. I think we as CiviCRM community members should step up and act. In particular, hosting providers, implementors, and organizations using CiviCRM should up their game to implement SSL, HSTS, and PFS.
After having worked with CiviCRM for going on a year, I was excited to see the community around the project and learn more about others who are using CiviCRM. Initially, I questioned the risk vs. reward of traveling 3000 miles across the country and leaving my new business for so many days. As the time drew closer and I started digging deeper into the session descriptions I began to get excited.
We've just added a page detailing CiviCRM's security policy and release process.
This page is intended to help people identify how they can stay abreast of security updates, know when to expect them, and how to tell which release of CiviCRM to expect security fixes for.
If you maintain or operate a CiviCRM site (or sites!) then you this is a page you should be familiar with, and there are a few actions you should take -
Because of the way the synchronization process works with the UF_Match table, deleting records can be tricky business. If done in the incorrect order, your CiviCRM database can end up with a bunch of Junk contact records. Below is a best practice process for removing records, first the Drupal user record should be deleted then the CiviCRM record.
Process to Follow
Step 1 - Identify the Identify the Contact record(s) to be merged/removed in CiviCRM and note the Drupal User ID for the record to be removed.