SIGN UP

User Email Notification Bug and Billing Frequency Non Match

By: Brent Sherman | Asked: 10/15/2022
Forums › Category: Code Help › User Email Notification Bug and Billing Frequency Non Match
0 Vote Up Vote Down
Brent ShermanBrent Sherman asked 2 years ago
Hello Formidable Community, I'm encountering TWO interesting issues with my registration/payment screen:

ITEM ONE
The info in this field [492 show="user_login"] populates the username in the New User email if I resend the email, but not when the user submits their original registration.  Strange Right? ITEM TWO
The BILLING FREQUENCY from the REGISTRATION RECORD doesn't match the BILLING FREQUENCY from the STRIPE>COLLECT A PAYMENT action. 

Item one feels like a bug of some sort, but I'm pretty sure I'll need someone who's good at hooks, php or js to fix item two for me, since the ... function isn't available in the REPEAT EVERY field(s) in the STRIPE>COLLECT A PAYMENT screen.

I've sent a request for item two in the paid help area before, but I'm not getting relevant feedback.

Thanks for your help to anyone who knows how to fix these!

I'm happy to pay someone to create the code to make item two work properly.

Best Regards,

Brent

Attachments
2022-10-15-Formidable-Community-Request-002.png
2 Answers
1 Vote Up Vote Down
Victor Font answered 2 years ago
My best guess is that Item 1 could possibly be a timing issue between when the registration is created in WordPress and when the form entry fields are stored in the frm_items and frm_item_metas tables. For Item 2, visit the Formidable Masterminds Developers Directory to find paid help at https://formidable-masterminds.com/developers-directory/
Brent ShermanBrent Sherman replied 2 years ago

Victor, thanks for the feedback. One of our community members jumped in and fixed both items. Take Care, Brent

0 Vote Up Vote Down
Brent ShermanBrent Sherman answered 2 years ago

We were able to correct ITEM ONE by requiring the user_login to = the users email address at registration.

We were able to correct ITEM TWO by adding multiple “collect a payment” actions, and setting conditional logic for each one.

When I say "we", I actually mean someone much more advanced than me. :)  I consider this item closed/resolved.

Making the Best WordPress Plugin even better - Together

Take on bigger projects with confidence knowing you have access to an entire community of Formidable Experts and Professionals who have your back when the going gets tough. You got this!
Join the community
crossarrow-right