Forum Replies Created
- AuthorPosts
clearscope
ParticipantOk great, thank you!
For some reason when I add that to our theme it then adds an additional button to the bottom of the page. So I had to comment out this part:
if (!class_exists(‘Quform’)) {
return;
}echo do_shortcode(‘[quform_popup id="1"]‘);
And leave in only the <script> part:
<script>
jQuery(function ($) {
$(‘#menu-item-75’).on(‘click’, function () { $(‘.quform-popup-link-1’).trigger(‘click’); return false;
});
});
</script>Anyway by making that amendment now it is working for us.
Thank you
clearscope
ParticipantWow, that’s awesome!!!
Thank you!
Quform rocks 🙂
clearscope
ParticipantHello,
We would like to create a similar layout of text fields in a grid/columns layout as shown in the screenshot of the original poster above (also attaching screenshot here). Basically, we’re just wanting to create the grid/columns layout with the text fields, without any need to do the more advanced javascript that this thread was about.
Is it possible to create such a layout, and if so do you already have a guide for how to do this?
Thank you
Attachments:
You must be logged in to view attached files.clearscope
ParticipantAwesome, we got it now after updating jQuery. Thank you!
clearscope
ParticipantThank you for your reply –
Sending along an email now with the link and a screenshot of the console error.
clearscope
ParticipantThank you for the reply –
This does seem to be quite a functionality removal that has occurred here, because it means that SMTP can now only be used globally. That means that there is no longer the ability to send using SMTP and using a different address / credentials as the sender for a particular form (all forms must now use the global address if using SMTP).
clearscope
ParticipantThank you!
That is absolutely perfect and much appreciated.
Thank you for all of the top notch support!!!
clearscope
ParticipantHi – thank you
We do need to be able to display a message to the user that the address is already subscribed.
Is it possible to provide the example referenced but modified for the v2 API?
Or would it be better to change the version of the API that we are using to match the example?
I’m just not sure how to do either. Here is the current code that we are using:
function my_save_to_mailchimp($form) { if (!class_exists('Mailchimp')) { require_once dirname(__FILE__) . '/Mailchimp.php'; } $mailchimp = new Mailchimp('mailchimpid'); $listId = 'listid'; $email = $form->getValue('iphorm_23_3'); // OPTIONAL: if you are saving additional fields to MC, set the merge tags, otherwise set $mergeVars to an empty array $mergeVars = array( 'MERGE1' => $form->getValue('iphorm_23_1'), 'MERGE2' => $form->getValue('iphorm_23_2'), 'MERGE3' => $form->getValue('iphorm_23_4'), 'MERGE4' => $form->getValue('iphorm_23_5'), 'MERGE6' => $form->getValue('iphorm_23_6'), 'MERGE17' => $form->getValue('iphorm_23_7') ); // Other settings $emailType = 'html'; $doubleOptin = false; $updateExisting = false; $replaceInterests = false; $sendWelcome = false; $mailchimp->lists->subscribe($listId, array('email' => $email), $mergeVars, $emailType, $doubleOptin, $updateExisting, $replaceInterests, $sendWelcome); } add_action('iphorm_post_process_23', 'my_save_to_mailchimp', 10, 1);
clearscope
ParticipantHello,
With our Mailchimp integrated Quform form, we are receiving this popup error when a submission is made and when that email address is already subscribed to the mailing list:
“An error occurred submitting the form”
When you do the same from the default Mailchimp hosted signup form, it displays the message: “email@domain.com is already subscribed to list…”
Is there a way that we can have the Quform error message state the same as the Quform error message, to tell the user that the email address is already subscribed?
The problem is that in such instances, with the current unspecific error message, it does not tell the user that the email address is already subscribed, so they end up contacting the company to report a problem or to ask why they can’t subscribe, when if fact it’s simply because they are already subscribed.
clearscope
ParticipantThank you for all of your help in getting this working!
It is greatly appreciated!!!
clearscope
ParticipantHi,
Thank you, but unfortunately we cannot confirm that it is working as we are now getting a popup error when submitting the form, stating “An error occurred submitting the form”. The submissions still seem to go through into the Quform entries, despite the error, but nothing goes into Mailchimp.
Thank you
Attachments:
You must be logged in to view attached files.clearscope
ParticipantWe have now sent along the requested info, thank you!
clearscope
ParticipantHello,
Thank you, however when we try the above code for $mergeVars it just seems to break the form again and nothing gets sent through to Mailchimp (though no error gets logged if we enable DEBUG).
When we use the original code it works properly and the contact is created in Mailchimp, but this of course does not contain the Groups:
function my_save_to_mailchimp($form) { if (!class_exists('MCAPI')) { require_once dirname(__FILE__) . '/MCAPI.class.php'; } $api = new MCAPI('key'); $listId = 'listid'; $email = $form->getValue('iphorm_21_3'); // OPTIONAL: if you are saving additional fields to MC, set the merge tags, otherwise set $mergeVars to an empty array $mergeVars = array( 'MERGE1' => $form->getValue('iphorm_21_1'), 'MERGE2' => $form->getValue('iphorm_21_2'), 'MERGE3' => $form->getValue('iphorm_21_4'), 'MERGE4' => $form->getValue('iphorm_21_5'), 'MERGE6' => $form->getValue('iphorm_21_6'), 'MERGE17' => $form->getValue('iphorm_21_7') ); // Other settings $emailType = 'html'; $doubleOptin = false; $updateExisting = false; $replaceInterests = false; $sendWelcome = false; $api->listSubscribe($listId, $email, $mergeVars, $emailType, $doubleOptin, $updateExisting, $replaceInterests, $sendWelcome); } add_action('iphorm_post_process_21', 'my_save_to_mailchimp', 10, 1);
clearscope
ParticipantOk thank you!
clearscope
ParticipantHi,
Sorry to clarify – it is not the main recipients that are having the issue, but rather conditional ones.
The thing is that with this form and several others, we often have to update the labels / values for the dropdown field that determines the conditional recipients. That dropdown field is a list of courses, and the applicant’s selection of that field determines which conditional recipient receives the email. So when old courses finish or new ones open up, we are removing or adding to the list of labels / values of that field.
So the only thing that we can figure is, perhaps because of the frequent updating to the list of labels of the field that determines the recipient, that this somehow causes some wires to cross in Quform and that is why it is having the email issues?
- AuthorPosts