ostinatofreak

I got rid of the visibility conditions for both Total and Stripe, and now we’re right back to what I wrote in my original post: “This value must be greater than or equal to 1.” Forminator unfortunately doesn’t tell me which field it’s talking about. When I fill out the form, I fill it out for myself and 4 other people (additional family members), and I try to pay for a family membership ($170).

It seems like there are maybe two problems with the form right now. The first one is with visibility, which I think is unfortunate, because there was nothing wrong with the logic. It doesn’t make sense to display a Total field when the user specifies that they plan to pay another way (i.e. with Zelle or by mailing a personal check). It also doesn’t make sense to display the Stripe field if the Total field is at 0. It would be nice to be able to use features as they are designed to be used. Or if there is some rule against hiding a Stripe or calculation field, then Forminator documentation should clarify to the user on-screen what conditions cause malfunctions to take place… or just disable the feature altogether if there is no way for Forminator to work when those kinds of fields have visibility conditions set.

The second problem is now coming out with the “This value must be greater than or equal to 1” error. I have no idea what is going on there, but clearly this is no longer related to visibility conditions, because at the moment my form has no visibility conditions anywhere.

P.S. I just put Stripe into test mode and tried it again, same error. Then tried it again without inputting any family members (I have 3 kids and a spouse I usually put in), same error. Then tried a VISA instead of Discover, same error.

I was finally able to get back to this (had to reinstall Windows 11 last week).

I disabled all plugins except Forminator – the form still gives me the same “Stripe field doesn’t exist” error. I also tried deleting the Stripe field altogether, saving the form, then going into Stripe settings and deleting the Stripe setup. I then went into Stripe and generated a new private key and set Stripe up from scratch in Forminator. Recreated the Stripe field in the form.

Same problem still exists.

I always have the entire website backed up (I do it regularly using FTP). At this point if you contact me at [email protected] with an email address such as @forminator.com or something, I will give you a temporary admin login on this website. There is no sensitive information on the site – even the Stripe section does not show the private key.

If you’d like to try it out on the website, I’ve put Stripe into Test Mode. See https://washoetennis.org/membership/ . I don’t think Test Mode is really relevant here though, because Forminator itself is stopping the testing process before it has a chance to begin, giving the user this “Stripe field doesn’t exist” error.

I’m really hoping to fix this in the next week, because 300 members are going to start using it next week to renew their annual membership, and I’m really not excited about the prospect of having to rebuild this form from scratch using WPForms.

PS maybe you could edit my original post so it doesn’t have the pasted info. I set the pastebin link to expire in 2 weeks. If you can’t edit the post, let me know if there is anything I can do in the interest of privacy – thanks.

https://pastebin.com/zsTB6AGn

Ok thanks. That seems to have worked. However, I seemed to have found another bug in the process. I have both of the panel groups set to only show one panel at a time. But if I go and edit the page again, that setting is turned off. Every time I edit the page, I have to turn that setting on for both panel groups again, or it goes back to being disabled.

Thank you!

Ok, thanks. I guess you must have been talking about a Datepicker field since I don’t see any Forminator field that is just called “Date.” But I see there is an option in the Datepicker field that allows me to have today’s date be the default.

Follow-up question: if I use conditions to hide the datepicker field (like as soon as “first name” is not null or something like that, making the Datepicker field disappear right away), can I still use the Datepicker field to base other fields’ visibility on? I’ve been playing around with it, and I’m starting to get the impression that “hidden” doesn’t just mean hidden from view, but also hidden from Forminator’s own internal awareness and therefore unusable in decision making. It would be nice to not have to have the date actually showing on the form to the user, but still have Forminator internally be aware of the date.

https://pastebin.com/sH7Cb5TK

The pertinent question in the form is the one that asks, “Were you ever previously a paid WTC (or formerly RTC) member?” This question should not appear during the months February through August. (This is slightly different than the info I gave above… above I was just trying to simplify the example.)

Right now (since it’s September), the form works. But if the current date were April or whatever, the form unfortunately still includes this question when it’s supposed to hide it.

Ok, where do I sign up? (Google searches and looking around here on www.ads-software.com did not help… and the Tablesome homepage doesn’t seem to have anything about a beta program)

### WordPress Environment ###

WordPress address (URL): https://www.orangenote.io
Site address (URL): https://www.orangenote.io
WC Version: 6.0.0
REST API Version: ? 6.0.0
WC Blocks Version: ? 6.3.3
Action Scheduler Version: ? 3.3.0
WC Admin Version: ? 2.9.4
Log Directory Writable: ?
WP Version: 5.8.2
WP Multisite: –
WP Memory Limit: 768 MB
WP Debug Mode: –
WP Cron: ?
Language: en_US
External object cache: –

### Server Environment ###

Server Info: nginx/1.14.0
PHP Version: 7.4.10
PHP Post Max Size: 64 MB
PHP Time Limit: 300
PHP Max Input Vars: 1000
cURL Version: 7.58.0
OpenSSL/1.1.1

SUHOSIN Installed: –
MySQL Version: 5.7.35-0ubuntu0.18.04.2
Max Upload Size: 64 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 6.0.0
WC Database Prefix: wp_
Total Database Size: 46.26MB
Database Data Size: 43.16MB
Database Index Size: 3.10MB
wp_woocommerce_sessions: Data: 2.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_order_itemmeta: Data: 0.09MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_actions: Data: 0.33MB + Index: 0.22MB + Engine InnoDB
wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_logs: Data: 0.19MB + Index: 0.16MB + Engine InnoDB
wp_ce4wp_abandoned_checkout: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_ce4wp_contacts: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_comments: Data: 0.05MB + Index: 0.09MB + Engine InnoDB
wp_edd_customermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_edd_customers: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_mailchimp_carts: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_mailchimp_jobs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_options: Data: 4.05MB + Index: 0.13MB + Engine InnoDB
wp_postmeta: Data: 20.45MB + Index: 0.45MB + Engine InnoDB
wp_posts: Data: 2.23MB + Index: 0.06MB + Engine InnoDB
wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_usermeta: Data: 0.09MB + Index: 0.03MB + Engine InnoDB
wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
wp_wc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfBlockedIPLog: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfBlocks7: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wfConfig: Data: 1.28MB + Index: 0.00MB + Engine InnoDB
wp_wfCrawlers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfFileChanges: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfFileMods: Data: 6.52MB + Index: 0.00MB + Engine InnoDB
wp_wfHits: Data: 1.02MB + Index: 0.05MB + Engine InnoDB
wp_wfHoover: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfIssues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wfKnownFileList: Data: 2.52MB + Index: 0.00MB + Engine InnoDB
wp_wfLiveTrafficHuman: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfLocs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfLogins: Data: 0.38MB + Index: 0.17MB + Engine InnoDB
wp_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfNotifications: Data: 0.09MB + Index: 0.00MB + Engine InnoDB
wp_wfPendingIssues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wfReverseCache: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wfSNIPCache: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wfStatus: Data: 0.13MB + Index: 0.09MB + Engine InnoDB
wp_wfTrafficRates: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wpmailsmtp_debug_events: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wpmailsmtp_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wpml_mails: Data: 0.09MB + Index: 0.00MB + Engine InnoDB
wp_yoast_indexable: Data: 0.14MB + Index: 0.09MB + Engine InnoDB
wp_yoast_indexable_hierarchy: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_yoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_yoast_seo_links: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_yoast_seo_meta: Data: 0.23MB + Index: 0.00MB + Engine InnoDB

### Post Type Counts ###

attachment: 74
custom_css: 1
download: 1
edd_payment: 1
feedback: 91
jetpack_migration: 2
jp_img_sitemap: 3
jp_sitemap: 3
jp_sitemap_master: 3
nav_menu_item: 20
page: 14
post: 1
product: 24
revision: 148
shop_coupon: 1
shop_order: 52

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (24) ###

WP fail2ban: by Charles Lecklider – 4.3.0.9
Add From Server: by Dion Hulse – 3.4.5
Akismet Anti-Spam: by Automattic – 4.2.1
Beaver Builder Plugin (Lite Version): by The Beaver Builder Team – 2.5.1
Creative Mail by Constant Contact: by Constant Contact – 1.4.8
Homepage Control: by WooThemes – 2.0.3
Jetpack: by Automattic – 10.4
Mailchimp for WooCommerce: by Mailchimp – 2.5.4
PowerPack Lite for Beaver Builder: by Beaver Addons – 1.2.9.2
Storefront Footer Text: by Wooassist – 1.0.1
Ultimate Addons for Beaver Builder - Lite: by Brainstorm Force – 1.5.2
Premmerce SEO for WooCommerce: by premmerce – 2.1.4
WooCommerce Admin: by WooCommerce – 2.9.4
Print Invoice & Delivery Notes for WooCommerce: by Tyche Softwares – 4.6.4
WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.3
WooCommerce Stripe Gateway: by WooCommerce – 5.9.0
WooCommerce Payments: by Automattic – 3.4.0
WooCommerce PayPal Payments: by WooCommerce – 1.6.3
WooCommerce Shipping & Tax: by WooCommerce – 1.25.20
WooCommerce: by Automattic – 6.0.0
Wordfence Security: by Wordfence – 7.5.7
Yoast SEO: by Team Yoast – 17.8
WP Mail Logging: by Wysija – 1.10.2
WP Mail SMTP: by WPForms – 3.2.1

### Inactive Plugins (0) ###

### Settings ###

API Enabled: ?
Force SSL: ?
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
subscription (subscription)
variable (variable)
variable subscription (variable-subscription)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: ?

### WC Pages ###

Shop base: #118 - /shop/
Cart: #120 - /cart/
Checkout: #122 - /checkout-2/
My account: #124 - /my-account/
Terms and conditions: ? Page not set

### Theme ###

Name: Storefront
Version: 3.9.1
Author URL: https://woocommerce.com/
Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ?

### Templates ###

Overrides: –

### Subscriptions ###

WCS_DEBUG: ? No
Subscriptions Mode: ? Live
Subscriptions Live URL: https://www.orangenote.io
Subscription Statuses: –
WooCommerce Account Connected: ? Yes
Active Product Key: ? No

### Store Setup ###

Country / State: United States (US) — Nevada

### Payment Gateway Support ###

WooCommerce Payments: products
refunds
subscriptions
subscription_cancellation
subscription_suspension
subscription_reactivation
subscription_amount_changes
subscription_date_changes
subscription_payment_method_change
subscription_payment_method_change_customer
subscription_payment_method_change_admin
multiple_subscriptions
tokenization
add_payment_method

PayPal Checkout: products
refunds
subscriptions
subscription_cancellation
subscription_reactivation
subscription_suspension
multiple_subscriptions
subscription_payment_method_change_customer
subscription_payment_method_change_admin
subscription_amount_changes
subscription_date_changes

Stripe: products
refunds
tokenization
add_payment_method

### WooCommerce PayPal Payments ###

Onboarded: –
Shop country code: US
WooCommerce currency supported: ?
PayPal card processing available in country: ?
Pay Later messaging available in country: ?
Webhook status: –
Vault enabled: –
Logging enabled: –
Reference Transactions: –
Used PayPal Checkout plugin: ?

### WooCommerce Payments ###

Version: 3.4.0
Connected to WPCOM: Yes
Blog ID: 139864478
Account ID: acct_1ImYdc2EzoTDAUtJ

### Action Scheduler ###

Complete: 706
Oldest: 2021-12-02 07:58:35 +0000
Newest: 2021-12-22 04:25:04 +0000

Pending: 4
Oldest: -0001-11-30 00:00:00 +0000
Newest: 2021-12-26 11:18:38 +0000

### Status report information ###

Generated at: 2021-12-22 04:25:07 +00:00

Here is a link to a video showing the issue (Opera version 82.0.4227.33).

Wow, your response really surprised me. A conflict problem is on the server, not on my computer. I knew that this problem would have to show similar results in all browsers if it were a conflict problem, so I checked out the website using both Edge and Firefox. Sure enough, the problem was not there with Edge and Firefox.

It appears this is some kind of problem with the Opera web browser. I’ve been using it for years and years – by far my favorite browser (seems to do everything other browsers do), and this is the one time I’ve finally encountered a problem with any website. I just reported it to the Opera team.

Having said that, I found the relevant code. It appears that embedded within a <form> element, there are <div> and <p> elements. I thought the <form> tag was pretty specific to the point where it’s improper to put anything else like that inside of it, if I remember correctly. If this ends up being improper HTML, I’m hoping WooCommerce can add that to their next update – clean the code of affected product pages. If it’s happening to my basic site which I’ve only accessed through the standard interface that WooCommerce / Storefront provides me (it’s not like I ever added the code myself), it seems to me that this is most likely affecting others as well. Even if it’s affecting a lot of pages out there, it would likely go undetected and unreported for the vast majority of users it affects, since not many people use Opera compared to Chrome/Edge/Firefox. (And even if it only affects 1% of all WooCommerce sites, that’s still a lot of sites.)

Same with students.twedt.com – Jetpack sync issue, and clicking on the link to start a fix was not successful.