6

After some tinkering, I think I understand better how this works. I included fields for both a volunteer and a new detained person. Before, there were only fields for collecting information on the new detained person. Now that there are fields for both individuals: 1) the logged in person filling out the form and 2) the new detained individual. Next I ...


5

The freelancer wasn't familiar enough with CiviCRM to realize that the municipality field we were looking for was already an integrated part of the CiviCRM through the county field.


4

Michael McAndrew shared a WIP at https://github.com/mecachisenros/caldera-forms-civicrm/pull/85 it does not yet include any ACL people have to remember to add a hidden contact id to the form a dedupe rule where contact id triggers a match (contact_id weight = 1, threshold = 1) is required


4

This type of problem commonly occurs when any of these is true: No default country is set No default state is set Available countries is not set - list on right-hand side is empty Available states is not set - list on right-hand side is empty Check your CiviCRM Localisation Settings. Below is a screenshot of a working configuration for a site in Australia ...


3

Caldera and Civi Caldera is a wprdpress plugin, you can locate them under wp-content/plugins/


3

Yes, I think you can setup caldera form to create an activity of type X in Civi and than have Civirule to send email (using email api extension) when activity of type X is created. You can use Civi token to include memberships details in email message. Thanks Pradeep


3

You can use the Integration of CiviCRM's Form Processor with Caldera Forms. See https://wordpress.org/plugins/cf-civicrm-formprocessor/


3

Jsgoti, Welcome to CiviCRM SE. You definitely achieve this using Caldera module. All you have to do is 1 - Create a form with First Name, Last Name and Email field and also drop down in Caldera form. 2 - Click on Processor tab. 3 - Add a new processor of type 'CiviCRM Group'. Then configure the settings to link contact to group Add condition by ...


3

The Contact Link at the top of the page serves as a form of labeling and as a way to connect/link other entities (processors) like an Activity to a Contact on the form. It's purpose may become redundant in the future, but just to be replaced with Caldera Forms' magic tags (kinda like CiviMail tokens). The link, and magic tags are a way to share and pass ...


2

Just an update on this question, Agileware have developed the following for Caldera Forms: EWAY payment gateway integration for Caldera Forms using EWAY Rapid 3.0 API CiviCRM recurring payments for memberships and donations using Caldera Forms Ability to view and update stored credit cards using Caldera Forms This work will / is and be publicised in a ...


2

In response to a question about WP, Caldera and iATS play nicely and do recurring danaskallman said: no, it's either of these two add-ons as of now stripe and authorize. iATS isn't an option for payment processors so it would need to be developed likely. Andrei said: the official CF payment add-ons support PayPal Express and Pro, Authorize.net, Dwolla, ...


2

Dedupe rules are set in the contact processor. If you want it to create a duplicate, create a dedupe rule in Civi that it can never satisfy. A dummy one basically :)


2

The contact reference field in caldera forms limiting the entries to a group created containing the employers should work.


2

This might not be the same, but the information at this link comparing drupal civicrm webform to profiles might be a similar starting point: https://docs.civicrm.org/sysadmin/en/latest/integration/drupal/webform/#compared-to-civicrm-profiles


2

In theory you can set up a Contribution page with Price Set with all your 'merchandise' available as Price Fields so they could order eg 5 postcards or 3 x pack of 3 cards etc. Then i you set the form for Pay Later that becomes a 'promise' which is recorded in civicrm as a pending transaction. when they submit then the purchaser will get an email, and the '...


2

This was my own confusion and I had help from the CF-CiviCRM author. Great support there. The problem was related to conditional statements in the form. I had created conditions for the appearance of all the contacts in a multi-contact form, but I hadn't applied conditions to processors. I had assumed that the conditions related to the show/hide fields ...


2

You can use Jaap Jansmas integration of CiviCRM with the Form Processor for that: Just create a form processor using the action "Mailing Event: Subscribe to mailing list". You can even create simple deduplicating rules using conditions on the actions "Contact: Get Individual by name and email" and "Contact: Create or update ...


2

I have it working and, at least in my case, the issue is with the handling of available countries and available states as rbaugh describes in this github issue. Essentially, if you leave the right-hand box empty to include all countries (as the CiviCRM note directs), none of the states are loaded. Loading all of the countries into both right-hand boxes works....


1

If you install it from github you need to run the following command in the directory of the plugin composer install This is explained in the readme on Github. The easiest way to install this plugin is on the Manage plugin page in your wordpress installation and then press add plugin and search for this plugin in the plugin directory.


1

The problem is solved by using cf-civicrm developer version from github rather than the version proposed by Wordpress. To understand more you can see this Post : https://github.com/mecachisenros/cf-civicrm/issues/185


1

Are you using Caldera add on plugin to create wp user if yes than i guess its a question to ask Caldera support team. Also can you check the email address you used already has wp user account or there is an entry in civicrm_uf_match table under uf_name column


1

Actually, the process is easy: In the Caldera form > tab Builder, add an hidden field with the value {get:field_name} (replace field_name by the desired value) In the Caldera form > tab Process, add a CiviCRM process and match the needed field with the one from Caldera with the magic field syntax, so here %field_name%. (In my case, 'employee of' ...


1

Making sure that Localisation is set is the first step. On the form itself, you need to define a country field: and then the State/Province Field. In the State Field be sure you are linking to the Country Field:


1

There's an example of how to do the second part of this in the integration module's README. Checksum support to auto-populate form with URLs like example.com/some-page?cid={contact.contact_id}&{contact.checksum} The part I'm not aware of is how to properly redirect from one form to a second form with the right contact ID and checksum. I don't have ...


1

Check out https://wordpress.org/plugins/verify-email-for-caldera-forms/ to do that double opt in step.


1

Ok, I worked this one out. You have to create the fields in the Caldera form first and then match CiviFields in the processor you've added to the Caldera fields you've created, it's a bit like mapping fields for import


1

Take a look at CiviCRM ACF Integration which will sync Civi data into WP. Then you can handle displaying the data using various WP methods. It's in early stages but there's lots of room to grow... Let WP display content and Civi manage contacts.


1

Building on Pete's answer - in 2020 the solution is the Agileware fork of Content Views CiviCRM plus Data Processor. This blog post has relevant download links.


1

See this question first: What is the recommended Wordpress equivalent for drupal-views for some ideas and then consider the Views plugin for WordPress, what they call "the Query Builder for WordPress." Then of course there is the Query Wrangler plugin.


1

Interesting, we (as in CiviCooP) are on the same quest. We will do a work-together on 9 November and I expect one of the projects coming out of that to develop a View-type of Wordpress plugin. Want to join us if we are going to do this in a sprint?


Only top voted, non community-wiki answers of a minimum length are eligible