Example Use Case
This example is a one event page which has tabs of many types of content and views attached which allows a anonymous user to view the info, see registered participants, register for the CiviCRM event via one webform which also automatically creates a contact, membership, active drupal user, and participant event registration to the event, logs in the user, and sets his user entered password via text field on the webform. Skvare has developed similar solutions for clients using these methods.
Using this method you can create easily customizable membership join, and event registration pages which leverage the full gauntlet of advanced Drupal 7 modules, and the ease of customizing the layout and style with css in the Drupal theme.
Original blog posted at Skvare.com.
CiviCRM 4.4.alpha3 was released today, and there's a shiny new beta release of Webform-CiviCRM-Integration 4 to go with it. Here's what's new in Webform-Integration land:
It's awesome that unlike profile forms, Webforms allow you to put more than one contact on the form. But after you've got a dozen or so, you start lose track of "what they heck are they all for?" This handy feature lets you give them more descriptive labels than "Contact 1" and "Contact 12."
Finally you can add and renew memberships via Webforms. This allows your users to sign up, renew, or upgrade their membership(s) as well as those of their spouse,...Read more
The second alpha release of CiviCRM 4.4 is now available for downloading AND you can try it out on the 4.4 sandbox site!
We Need You to Try it Out!
Excited to try the new features in this release? Please do! Great software requires great testers, and you can help. You don't need to be super technical to participate in this way, but your participation will make a huge difference.
- Download it and either do a fresh install or (better yet) upgrade a test copy of your existing database. Note that this is alpha software and should not be used on production servers.
- Try to break it! Do all the things you normally do with CiviCRM, try out as much as you can think of.
- If anything doesn't seem right, please let us know on the ...
WORKING TOWARDS DEVELOPING A CIVICRM COMMUNITY IN MEXICO
Mónica Tapia-Alvarez and Isobel Platts-Dunn
In 2009, with Common Cause International technical assistance and while developing a new citizen advocacy model for educational reform, we assessed the importance of IT solutions for managing members, petitions and donations from a large number of citizens. The IT solutions that US-based organizations used were discarded because their license was extremely expensive for Latin American organizations (Convio annual license cost is around US$50,000) and had in-built US representatives and media that was useless for Latin American contexts.
Through searching for different tools (a search suggested by...Read more
If you use the Drupal Webform-CiviCRM Integration module, pay attention for a sec, you're going to want to know this:
In order to keep up with the evolution of CiviCRM and the Webform module, I've forked the Webform-CiviCRM Integration project and started work on version 4. It will be compatible with the upcoming Webform 4 and CiviCRM 4.4 (a nice convergence of the number 4). Version 3 of this module will not work with those, so when you upgrade one of those modules, you'll need to upgrade the other 2 as well. If that's not making sense, here it is in a table:
|Version 2 works with:||6...|
With the 4.3 upgrade, the Progressive Technology Project has made a number of important steps toward breaking out our work into pieces that others can use on their sites. This blog will begin a series of (hopefully) weekly blogs outlining new functionality that others can use.
Our first blog features the civicrm_petition_email Drupal module. Thanks to the hard work of agh1, a Drupal 6 version of the module is available (https://github.com/agh1/civicrm_petition_email). We just finished porting it to Drupal 7.
For the impatient:
git clone git://git.progressivetech.org/powerbase/civicrm_petition_email
git checkout 7.x-1.x
With this module enabled, there are a few new checkboxes on the petition form that allow you to specify the name and email address of a target that should get notified every time the petition is filled out. In addition, you can optionally specify a field in the petition...Read more
Tonight found Giant Rabbit hosting the local CiviMeetup in Berkeley, CA, where we talked Drupal Webform Tips and Tricks (and if you want to support CiviCRM payment integration in Drupal webforms, you might consider giving a few dollars to our Make It Happen Campaign) and a few basic data how to's.
We had a good mix of WordPress, Joomla, and Drupal users, and Civi users old a new - and a good mix of cocktails to ease us out of the workday.
Oh, and then there was the CiviCRM Trailer. That happened.
We have seen two recent breakthroughs for people who want to spend more time on implementing awesome websites and less time fiddling with hosting.
Pantheon has launched a hosting service for Drupal that’s even simpler than cPanel and has seriously good performance and scalability built-in. We don’t need to setup caching anymore or worry about a reverse-proxy server; all we need to do is enjoy designing and configuring our sites. Developers like it just as much as implementers because it clearly separates the dev, testing and live environments and plugs nicely into GitHub. It schedules backups and it’s easy to move your site elsewhere if you want to.
CiviCRM Starter Kit is a Drupal-and-CiviCRM-in-one bundle that I have been interested in. It includes a sensible choice of modules and extensions to get you...Read more
The attached chart came out of a discussion between Kasia Wakarecy, Lola Slade and myself (Lynna Landstreet), at Freeform Solutions, about some issues we'd encountered when trying to to do major version upgrades of CiviCRM and Drupal on a client's site at the same time. Since we're likely to have a number of other combined upgrades like that to do in the future, we wanted to iron out the best process for doing them as smoothly as possible.
And we thought it might be useful to share what we’ve got thus far with others in the CiviCRM community, partly because it might help other people, and partly to find out others’ experiences: do you agree with what we’ve outlined here? Disagree? Have anything you’d want to add/change? We’re thinking of contributing this to the wiki documentation, but wanted to post it here for discussion first.
The pink boxes on the chart represent the actual steps involved, with the green ones being the state of the site(s) you’re working on...Read more