If you are using a checksum from civimail, then I believe we have managed to 'daisy-chain' forms by enabling the checksum field and contact ID on form 1, and then use those as tokens in the path used after the submission so that info is passed through to form2 etc
EDIT I see my memory was slightly incorrect. Rather than putting the tokens in the Redirection ...
On the CiviCRM part of the webform, in the 'Contribution' section there is a field 'Payment Processor Mode' where you can set either 'Test Mode' or 'Live Transactions' (and save this, of course, not forgetting to reset both this and Stripe dashboard when going live).
The limit of 12 is hard-coded in the webform_civicrm module. You can find the line here
The most crude way to change it is to edit the source code. You will lose this change the next time the webform_civicrm module on the site is ...
Another potential approach for webforms which I've used (in both Drupal 7 and Backdrop), is to adjust settings on the "Existing Contact" webform component for that contact.
In the "Contact Field Handling" section, you can configure it to lock the Contact Fields, Email, etc. if they contain data, leaving them open for editing if they are ...
That's one of the problems with checksum links - it's just a link connected to a specific user and although you sent the link to the specified contact, there is no guarantee that it is actually that person using it. The options come down to hoping people read your instructions and answer correctly.
You can ask people not to forward the mail ("Please ...
Here's what I ended up doing. It feels a bit weird, but so far it seems to do the trick.
Having created the fields I need for the two contacts, and ensuring that buyer is contact 1 (because the contribution appears to only work for contact 1), I can then specify a membership that will be applied to contact 2.
Even though I've set a minimum price for the ...
The problem is having null in civicrm_line_item:price_field_id & price_field_value_id
If a donor has one historical contribution that is missing the price field id & price field value id, then you cannot access their contribution tab.
The fix is to fill in the missing fields, a couple of options:
LineItem Edit extension and do them one by one
Posted in Webform CiviCRM Drupal Issue queue:
Webform CiviCRM indeed has not been specific about price_field_id or
price_field_value_id in the past - b/c CiviCRM core has been 'fetching' these
automatically. When there is a ton of price_fields though (both visible and
hidden), the fetching may not produce the correct result or no result at ...