I recently had a requirement to allow for export of Accounting Batches to a format that AccountEdge can use. The good news was AccountEdge has many CSV import wizards for many different types of data. The bad news was the layout of the accounting batch export CSV file from CiviCRM did not match what AccountEdge expected. So I set about creating a new export format for CiviCRM which is compatible with the "File ... Import Data ... General Journal Entries" wizard in AccountEdge.
What I had to do:
Step 1: Update list of export options to include the new choice "CSV for AccountEdge"
In 2014 MAF Norge funded CiviCooP developing the TriggerAction extension (https://github.com/CiviCooP/org.civicoop.triggers) to assist them with automated Donor Journeys in CiviCRM. Our team of Jaap & Erik from CiviCooP and Steinar & Helen from MAF Norge worked hard for a week and we came up with something that does work but is fairly complicated and decidedly unsexy. During the CiviCRM sprint in Edale Jaap & Erik from CiviCooP worked on a first analysis of CiviRules, a CiviCRM extension that is based on the Drupal Rules module. We described our thoughts (and some great contributions from community members) on a wiki page: http://wiki.civicrm.org/confluence/display/CRM/CiviRules+extension
In 2015 our aim is to actually develop and deliver the...Read more
When preparing an email newsletter, one part of it that is time consuming is gathering together all the content that is needed. In my experience, virtually all the content already exists elsewhere, such as in the local CMS, in CiviCRM, or on a blog, or some other online source. So I was thinking how can I make this process easier. What I did: I created mail merge tokens for CiviCRM that autofill a list of recent blog posts, stories, or any other type of CMS content. So the end-user sees a list of tokens, one for each content type, each term/category, each aggregator feed, and for each date range. Such as "Content of type 'blog' created in the last 7 days" . What is particulary powerful about this approach, is that if you are also using a CMS aggregator (such as the aggregator module in Drupal core) then virually any external RSS feed is turned into CMS content, which is now available as a CiviCRM token.
Some examples of how this new extension may help your...Read more
Whether your nonprofit or social good organization is small, like the local animal shelter, or large, like the Creative South conference, chances are volunteers mean a lot to your mission. Ginkgo Street Labs has been leading the effort to develop the CiviVolunteer extension of CiviCRM to make it easier and faster for nonprofits to manage their volunteers.
Because of the CiviCRM project’s open-source structure, many nonprofit users are active on the online forum, troubleshooting issues and sharing ideas for things they wish CiviCRM could do. We regularly organize and categorize this input into the CiviVolunteer Road Map, which shows where we’re going next with development.
Right now, we are...Read more
How we've achieved this?
Those of you who have been following our blog, or our linked in discussion group, or are on our partner list will know that quite a few people have been working on a new question and answer site for CiviCRM, based at Stack Exchange. CiviCRM is already a super helpful community. Stack Exchange provides a really powerful tool that 'curates' the question and answer process much more effectively that traditional forums. We think the combination of the two, will take our community based help and support to the next level, but we need your help to do so.
Before the powers that be at Stack Exchange will grant us a CiviCRM Q&A platform, they want us to prove that we have the community to make it work. They are asking us to get people to commit to our proposal. We need at least 200 people to commit. We've already got over half way there in just under 2 weeks, which is pretty good but we have a way to go yet. Commiting should take less than a minute so...Read more
This extension has been unpublished from the CiviCRM extensions directory, as it is obsolete. The source code is still at GitHub (https://github.com/sgladstone/com.pogstone.paymentprocessorhelper), but is not maintained, nor recommended.
Pogstone has published a new native extension called "Payment Processor Helper" Its designed to standardize and streamline, and ease support challenges related to automated recurring contributions that are connected to payment processors. This extension is NOT a payment processor. Its designed to work along side existing payment processors, which at this point includes PayPalPro, Authorize.net and eWay recurring. Hopefully this is of use to organizations using one of those 3 payment processors, and/or other developers creating payment processors that want to offer automated recurring...Read more
Every software project is faced with the challenge of balancing the need to innovate and introduce new features, with the interest of many users in minimizing their maintenance costs and avoiding the risks that inevitably come with software upgrades. One way to meet this challenge is to provide a Long-term Support (LTS) release with an extended release cycle.
For the past several years, a small and dedicated group of community members led by Eileen McNaughton (Fuzion NZ) and Nicolas Ganivet (Cividesk) has done most of the hard work and heavy lifting to maintain version 4.2 as a "community-supported" LTS release. This has worked well, but there have been some inefficiencies due to not having a centralized repository for the LTS version of the codebase.
Given the increasing importance of a reliable LTS for many members of the community, the LTS team approached the Core Team...Read more
As you may know from a recent blog post by artfulrobot, CiviCRM is applying for a dedicated platform on Stack Exchange. I don't know about you, but I would love to see this happen. (If you wonder what this is all about, please refer to the beforementioned blog post which explains it very well.)
This initiative needs backing from Stack Exchange veterans now! Here is why:
In the current phase of the proposal, Stack Exchange wants to see how many and what kind of people would actually be contributing to the platform. People are asked to commit to using it. Three values are being measured, out of which the minimum counts. In our case, this is "committers with 200+ reputation on any other [SE] site" with only 8 out of the required 100 committers so far. So while we...Read more