This is a first blog post about how we build the team portal for Roparun.
But first what is Roparun? The Roparun is a relay race of over 500 kilometres from Paris and Hamburg to Rotterdam, where people in teams, take part in an athletic event to raise money for people with cancer. It’s also called an adventure for life. This is also clear from the motto, which for years has been: ‘Adding life to days, when days often can’t be added to life’.
So each year Roparun organizes this race and around 400 teams participate in the event. The first part of the project was to setup donation functionality and that is working right now.
The next part of the project is to create a new portal for team captains where they can manage their team data, (e.g. name of the team, start location and the individual team members). We...Read more
I have finished a working prototype of the form-processor and action-provider extension. See my previous blog post for where the idea came from.
Below I will explain what you can do with this extension. Lets assume we have an external website where students can signup to volunteer in a summer program. When a student has signed up we want this data to be present in CiviCRM and the student added to the group student volunteers.
We then have a screen where we can enter the name, define the input fields (in our case email address)...Read more
Last week we had a Sprint in the wonderful city of Brussels. This blog post is a recap of what I have been up to.
I started the sprint to work on a new extension the form processor. This idea came to my mind as I had a few clients at which I had to develop a custom api for data coming from their website (in those cases CiviCRM was separated from the website). And my idea was that I wanted to give system administrator and implementers a tool in which they could create those kind of API by themselves. So the form processor was born.
Below is a sketch of the screen of the form processor (click the image for a larger preview):
The form processor is designed so that the user first defines the...Read more
civicrm-setup library aims to replace the CiviCRM installer. Following the December/January iteration, it's available for use as a CLI installer and as a web-based WordPress installer.
- Entropy: The main installer's code has grown messy. For example, it mixes...
The power of Workplace by Facebook is now available for CiviCRM users!
New button in the User Profile opens up a communication channel within CiviCRM for work chat, team groups, project updates, instant messages or alerts (see pic. 1 below). The functionality will noticeably improve communication across organization inside or outside the office as it falls back on all the strengths Facebook has to offer, the most prominent being the user-friendly familiar interface and secure collaboration.
pict. 1 - runing Workplace by Facebook from CiviCRM
Workplace by Facebook is your own version of Facebook which is a really convenient tool for internal communication. There are enough...Read more
I just published a small extension (funded by Amnesty International Vlaanderen) to prevent the REST API requests still coming through when the site is in maintenance mode.
The extension is CiviCRM native and the structure is based on the CiviCRM User Framework. However, as I have little to no experience with a CMS other than Drupal, I have only implemented the Drupal module. Would be really great if others could add the same trick for the other CMS's!
- check if API request originated from REST (api_key and key in the request)
- if yes, check if CMS is in maintenance mode
- if yes, throw API_Exception with error code maintenance_mode
The extension can be found here.Read more
One of the main reasons our partners choose to set up a CiviCRM application is its extended functionality developed specifically for managing all contacts, communications, records and activities of an organization in one place.
Yet one of our clients put a broader meaning into the concept single CiviCRM-based solution and requested new functionality that would allow users to manage their emails (check and read incoming emails, compose new messages, etc.) from the CRM instead of shifting between different applications.
In other words, the client requested an inbuilt email client for CiviCRM that would prevent the staff from wasting time by tediously switching between CRM and Emails.
CiviCooP and Systopia and Palasthotel have been working together on CiviProxy and CiviProxy. This blog is a round up of what we have achieved in the last couple of days. The first thing we have achieved is that we had fun and a very good work atmosphere. We made long days and made lots of progress.
What are CiviProxy and CiviMcRestFace?
CiviProxy is a script to act as an application firewall for CiviCRM. It could be used to put your civicrm in secure network. CiviProxy is the gatekeeper to which external systems, such as your website, connect (this is for example when a user signs a petition on your website and the website submits this data to your CiviCRM). CiviProxy will make sure the call is from the right place (ip-adress) and is only doing what allowed to do.
CiviMcRestFace (CiviMRF) is a framework to be used in other systems (such as your external website) to connect to CiviCRM. The framework itself is...Read more
We’ve talked about and have made some progress on APIv4. Along with a native form builder and an improved UI, a new version of CiviCRM’s API was identified as a key objective our roadmap. While it may be the least glamorous of the three, it is an increasingly important and powerful feature within CiviCRM. And it’s time for an update.
Api version 4 represents an important leap forward for the CiviCRM platform. An api is an "Application Program Interface" used to create, read, update or delete information in the database. It is used by extensions, 3rd-party integrations, customizations, and increasingly by the core CiviCRM software itself. CiviCRM currently ships with api version 3, which has many excellent features but also some limitations which hinder development of api-based applications.
Broadly speaking, APIv4 will allow organizations using CiviCRM to:
Busy sites have often encountered problems with deadlocks on the group contact cache. There were no less that 3 different code contributions to mitigate this problem put up for 4.7.8 and a number of other discussions have been going on in JIRA.
Merged into 4.7.8 are some improvements which we hope will mitigate this problem for those sites that experience it. JIRA is the primary source of information on this, however I wanted to share a brief overview.
The focus of the fix so far has been very much on deadlocks when clearing the contact cache. The reason being that these have been causing the most havoc. In analysing the problem it turned out that when someone edits pretty much anything the code looks for stale groups & tries to flush the cache. Depending on the size of the cache that can take a few seconds and it doesn't update the cache last flushed date until afterwards. So if the...Read more