Extensions are a growing part of the CiviCRM way of doing things. We need to develop a process and toolset to facilitate getting them translated and making those translations easily installable. This post is intended to lay out some issues and a potential approach in order to generate discussion.
Here are some assumptions and suggestions I have:
- Extension developers should be responsible for coding their extensions with ts(), and can be expected to do things like extract strings from their extension and upload somewhere for translation.
- Transifex is the tool used for translating CiviCRM strings. It has a team for each language translation, who do the translations. This approach is working fairly well. Having extension strings presented for translation in the same space, and displaying percent translated for them, etc. would be ideal.
- Translations are done in spurts and at somewhat unpredictable times, depending on the interest and...
If you want to see how a group has grown over time or view your Civi groups in their hierarchy, check out the new Groups Extension.
Like many organisations, Woodlands Church uses Civi groups extensively. We have groups which are mailing lists but many of our Civi groups are real groups of people who meet together week by week and group attendance is a significant indicator of engagement with the church. With well over one hundred groups in the city we cluster our groups by location and use the Civi groups hierarchy to reflect this.
Until now there hasn’t been an easy way to view Civi groups in their hierarchy but a new extension makes this possible, showing the groups hierarchied by their ‘parent’ group. Totals are shown for both child and parent groups and it’s also possible to quickly see members by clicking on a...Read more
Better volunteer management tools have been on the want list of many a CiviCRM user, dating back as far as 2006. Many of the organizations we work with require tools for managing volunteers apropos to specific events. For example, they may host periodic festivals requiring heavy volunteer participation to cover needs from ticket-taking, to crowd control, to staffing info tables, to A/V. In many of these cases, the organizations are already using CiviEvent to manage registration for regular attendees. While they could create duplicate events -- one for attendees (i.e., Participant role = Attendee) and one for volunteers (i.e., Participant role = Volunteer) --, this is clunky, counter-intuitive, and inflexible. Enter CiviVolunteer.
1. Specify Volunteer Needs
Event administrators specify their volunteer needs through a new “...Read more
The team is excited to announce the release of 4.2 stable with support for Drupal 7, Joomla 2.5 and WordPress 3.3.
You can download the release from SourceForge, and you can also test drive the release on each platform using the public demos:
Extensions take flight
The combination of extendability and a facility for folks to share their innovations is a key to the success and growth of the three content management platforms that CiviCRM integrates with. After several "experimental implementations" - we think the extensions functionality for CiviCRM is now ready for prime time with the 4.2 release. This...Read more
GiftAid has been ported to a Civi Extension for 4.2, so that it can be used in CiviCRM irrespective of the CMS. The extension has been tested in Drupal 7, Joomla and Wordpress. Hope it will make especially Joomla folks happy, as there were requests in the forum about porting the module as a Joomla Plugin.
Latest improvements include
- Simplying/re-structuring the custom data group used in Giftaid to make it more meaningful
- Enforcing the contact to have a home address for creating a GiftAid declaration
- Giftaid profile to use address fields of Location type: Home
- Copying the home address to the GiftAid declaration at the point of creating the declaration
- Only contributions of status 'Completed' can be added to a GiftAid batch, to be submitted to HMRC.
Download link: https://github.com/rajeshrhino/uk.co.nfpservices....Read more
I blogged a while ago about "Putting the R back in CRM" about the limits on relationships in the self-service areas. Well I am happy to have an update. I (Pogstone Inc) have sponsored the creation of a new extension ( along with JMA Consulting). This extension is taking advantage of the CiviCRM extension framework for modules, so it should work under Drupal, Joomla or Word Press.
The extension is designed to enhance event registration for the scenario where a parent is registering their child or children for an event, such as a school program, camp program, or any other youth program. It will allow the collection of data about one or both parents, the children, and several emergancy contacts. To register multiple children, the standard checkbox "register multiple participants" would be used. Upon submission, the module...Read more
So maybe filling out forms isn't anybody's idea of a good time, but at least building them can be fun, thanks to the shiny new version 3 of Webform CiviCRM Integration!
If yours isn't among the 700+ sites using Webform Integration, this Drupal module is a smart form-builder and processor that answers the following question: "CiviCRM has built-in forms for stuff like event registration and contributions, but what about collecting CRM data on my ________ form?" Fill in the blank with just about anything - survey, petition, enrollment, application, support, opt-in, you name it. You can use it to collect and update information about contacts, relationships, cases, activities, event participants, group subscriptions, tags, and custom data.
So What's New?
Version 3 has major improvements for working with existing contacts and option lists, a new look, UI improvements, and other enhancements....Read more
Hey All, Thanks for your patience and putting up with the delays in the release of CiviSync Outlook. CiviSync Outlook is the much awaited Outlook integration plugin for CiviCRM. It allows information sync between CiviCRM and Microsoft Outlook. CiviSync Outlook uses CiviCRM API. Due to some restrictions with API; at one stage we decided to use our own version of the API but it's not something we would like to run with in long term and hence dropped it fairly quickly.
CiviSync now uses the native API. A detailed user manual in creation but in the meantime Target Integration's wiki page will give you some information on how to install and use it on your installation of Outlook.
Don't forget you need four things to login to a CiviCRM instance using REST API:
- API Key for the user who is trying to login. You don't need the...
I am starting a project that will allow CiviCRM to support the needs of an Australian non-profit. This non-profit is subject to the Australian Goods & Services Tax rules (GST) for some but not all transactions.
The GST requirements apply whenever the non-profit provides a tangible good or service in exchange for a payment. This is most common with their dinners, selling DVDs, and items from their gift shop.
I have written up the requirements and possible approaches on the CiviCRM wiki at:
I would love to get feedback from anyone who would like to participate or later use the new module.
Many CiviCRM customizations have been packaged and distributed as Drupal modules. This can be desirable when a customization delves into both the CMS and CRM functionality, but -- when a customization focuses only on CiviCRM -- Drupal modules are a drag: they need to be patched for CMS upgrades (D6/D7) as well as CRM upgrades (Civi 2.x/Civi 3.x), and they don't work with CiviCRM's other CMS's (Joomla and WordPress).
Fortunately, dlobo has been making progress on support for native modules (built around the "CiviCRM Extension" system) in 4.1 and 4.2. An example module is here:
Of course, this still poses a challenge: a native module needs to use native tools for packaging code, adding new web pages, developing templates, etc. -- and all those tools come with a learning curve. To improve the learning curve, I've taken a...Read more