chloemccarty

Update: turns out if you manually edit the block it strips out the html_id attribute so the CF7 block cannot be used at all if you want to use the custom attributes that were previously available with CF7 in the classic editor.
You would have to use the shortcode block instead.

It would be great if these attributes were available in block settings.

@jordyvanovereem @alessiovanzini There’s some issue with the fact that the signature plugin JS doesn’t copy the signature data over to the required hidden field until after form submit.
I resolved this for myself by adding the code I noted in this solution: https://www.ads-software.com/support/topic/validation-required-issues/#post-14155577

This code causes the data to be copied over as soon as you mouse over the submit button. If it doesn’t work for you, you may have to tinker with it or try a different solution, like running sigObj.beforeSubmit() inside a timed interval. That’s not pretty, but it would probably work.

Hey alessiovanzini, did you try making the edit to the code I noted above? That fixed it for me, plus the code I added here for the issue where you need to double-click submit
https://www.ads-software.com/support/topic/validation-required-issues/#post-14155577

I was able to resolve the validation issues by using my code above plus https://www.ads-software.com/support/topic/cf7-5-4-update-missing-validation-message/#post-14152788 to fix the empty validation message.

Are you using the normal [submit] shortcode for your submit button in cf7?

What error do you get? What browser are you using?
If you add
console.log('hover'); before the sigObj.beforeSubmit(); in the code I posted above, do you see that log to the console when you go to click the submit button?

I’m having the same issue after updating to CF7 5.4.

Here’s what I did to fix it:
In this file contact-form-7-signature-addon\public\js\scripts.js
Before line 57, add this code:

// Custom Event Listener to populate signature data before submit.
$(form).find('input.wpcf7-submit').on('mouseover', function() {
    sigObj.beforeSubmit();
});

This forces the signature data to be copied over to the hidden field when the user mouses over the submit button, which completes just in time before the form actually submits.
This works on edge, chrome, firefox, android and iphone (safari).
Noting this could get messed up if the user submits the form a different way (e.g. by hitting “enter”) but if your signature field is the last field on the page this probably won’t happen

• This reply was modified 3 years, 8 months ago by chloemccarty.

Noting that I was able to fix this issue with the following code in the meantime, but I don’t love this solution because it could break in the future if CF7 ever makes use of other important localized script data:

add_action('wpcf7_enqueue_scripts', 'prefix_fix_form_reset');

function prefix_fix_form_reset() {
    $wpcf7 = array();
    wp_localize_script( 'contact-form-7', 'wpcf7', $wpcf7 );
}

You can add this to functions.php

• This reply was modified 3 years, 8 months ago by chloemccarty.

Hi there!

I realized this was a permissions issue. In my multisite, the wp-content/uploads/sites/2/wpcf7_signatures/ directory where the signature images are stored was missing write permissions from the web group so the signature field couldn’t be created.
Giving that directory proper permissions fixed this issue and now my emails are populated with in-line images.
Thanks!

Thanks for the advice, that did the trick! (I just hooked it into the ‘woocommerce_before_cart’ action)

Yes, the nonce is cached even when the user has something in the cart. (The ‘apply_coupon_nonce’ is reset when you add something to the cart, but for some reason when you then go to do an action like add a coupon to your cart, you get a cached nonce which causes a 403 error on the /?wc-ajax=apply_coupon request meaning logged out users can’t use coupons.

I determined that the ‘apply_coupon_nonce’ nonce for woo was getting cached for logged out users when I temporarily added some logging to woocommerce\includes\class-wc-frontend-scripts.php and wp-includes/pluggable.php

That fixed it, thanks for all your help!

<fieldset class=”c-enrollment-prospect-form__form__fieldset__subfieldset financial-information”>
<legend class=”c-enrollment-prospect-form__form__fieldset__legend”>Financial Information</legend>
[group no-income-provided-group]
<div class=”clearfix”>
<div class=”form-group -text”>
[checkbox income-not-provided id:income-not-provided use_label_element “I choose not to provide my income information.” ]
</div>
</div>
[/group]
[group income-does-not-qualify-group]
<div class=”clearfix”>
<div class=”form-group -text”>
[checkbox income-does-not-qualify id:income-does-not-qualify use_label_element “I certify that our household does not qualify because our total annual income is above $100,000.” ]
</div>
</div>
[/group]
[group household-income-group]
<div class=”clearfix”>
<div class=”form-group -text”>
<label for=”household-income” class=”-sentence”>What is the gross annual income (before taxes) generated by the houshold? <span>*</span></label>
[number* household-income id:household-income placeholder “$”]
</div>
</div>
[/group]
</fieldset>

show [income-not-provided-group] if [income-does-not-qualify] not equals "checked"
show [household-income-group] if [income-not-provided] not equals "checked"
                          and if [income-does-not-qualify] not equals "checked"
show [income-does-not-qualify-group] if [income-not-provided] not equals "checked"
show [tech-subs-po] if [tech-shipping] equals "Please ship to my P.O. Box."
show [temp-housing] if [temporary-housing] equals "Yes"

There are a LOT more fields on the form but I left out the ones that aren’t relevant. Hopefully that’s okay.

I added the custom fields and the rules but I don’t think the tool is working for me since I can’t see any of the fields. https://webpagefx.mangoapps.com/sf/MzI5NzI1XzczNDMyNjc
https://conditional-fields-cf7.bdwm.be/form-tester/?formcode=%3Cfieldset%3E%3Clegend%3EFinancial+Information%3C%2Flegend%3E%5Bgroup+no-income-provided-group%5D%3Cdiv%3E%3Cdiv%3E%5Bcheckbox+income-not-provided+id%3Aincome-not-provided+use_label_element+%E2%80%9CI+choose+not+to+provide+my+income+information.%E2%80%9D+%5D%3C%2Fdiv%3E%3C%2Fdiv%3E%5B%2Fgroup%5D%5Bgroup+income-does-not-qualify-group%5D%3Cdiv+%3E%3Cdiv+%3E%5Bcheckbox+income-does-not-qualify+id%3Aincome-does-not-qualify+use_label_element+%E2%80%9CI+certify+that+our+household+does+not+qualify+because+our+total+annual+income+is+above+%24100%2C000.%E2%80%9D+%5D%3C%2Fdiv%3E%3C%2Fdiv%3E%5B%2Fgroup%5D%5Bgroup+household-income-group%5D%3Cdiv%3E%3Cdiv%3E%3Clabel+for%3D%E2%80%9Dhousehold-income%E2%80%9D+c%3EWhat+is+the+gross+annual+income+%28before+taxes%29+generated+by+the+houshold%3F+%3Cspan%3E*%3C%2Fspan%3E%3C%2Flabel%3E%5Bnumber*+household-income+id%3Ahousehold-income+placeholder+%E2%80%9C%24%E2%80%9D%5D%3C%2Fdiv%3E%3C%2Fdiv%3E%5B%2Fgroup%5D%3C%2Ffieldset%3E&mailbody=&conditions=show+%5Bincome-not-provided-group%5D+if+%5Bincome-does-not-qualify%5D+not+equals+%22checked%22show+%5Bhousehold-income-group%5D+if+%5Bincome-not-provided%5D+not+equals+%22checked%22++++++++++++++++++++++++++and+if+%5Bincome-does-not-qualify%5D+not+equals+%22checked%22show+%5Bincome-does-not-qualify-group%5D+if+%5Bincome-not-provided%5D+not+equals+%22checked%22

I think you might get that error if you’re using a VPN.
For the beta form tester, what am I supposed to put in the “Conditions (export)” field? I didn’t see an option to export my conditional fields on my form anywhere.

P.S. I just reverted the plugin to 1.8.3 and the conditional fields work again. I made no other changes so I am sure the update is what caused the problem.

I ended up being able to figure it out by adding some selectors and making sure this settings was unchecked https://webpagefx.mangoapps.com/sf/MTQ0MDUyXzYxNzgzNTE

Thanks!