Forminator Pro plugin review and common issues

Forminator stores submissions in custom database tables. Check: (1) in Forminator → [form] → Submissions, verify the correct form is selected and no date filters are hiding entries; (2) the “Store submissions” setting must be enabled in the form’s Settings → Submissions — if disabled, submissions are processed (emails sent) but not stored; (3) check if submissions are being incorrectly marked as spam (Forminator → [form] → Submissions → Spam tab); (4) if using a multi-page form, ensure all pages complete before the submission is recorded.

Forminator Stripe integration requires: (1) Stripe keys configured in Forminator → Settings → Payments → Stripe (separate test and live keys); (2) verify “Live Mode” is enabled in Forminator → Settings → Payments; (3) browser Console may show Stripe.js loading errors or invalid key errors; (4) the form must have a Payment field and the Payment field must be connected to Stripe in the field settings; (5) test in Stripe’s test mode with test card numbers (4242 4242 4242 4242) to verify the integration works before going live.

Forminator polls use AJAX for real-time result updates. If results are not updating: (1) clear all page caches — cached poll HTML shows static old results; (2) verify the poll’s display settings include “Show Results After Vote”; (3) a JavaScript error may prevent the AJAX update from completing — check browser Console after voting; (4) heavy object caching (Redis) may cache the poll results response — exclude the Forminator poll AJAX endpoint from object caching; (5) test without cache plugins active to isolate whether caching is causing the issue.

Add a Calculation field to your Forminator form. In the field settings, write the calculation formula using other field values: {field-name} references another field’s value. Example for a service estimator: (Quantity × Price_Per_Unit) + Setup_Fee = {quantity} * {price} + {setup_fee}. The Calculation field displays the result in real-time as the user fills in the form. Connect this Calculation field to a Payment field (Stripe or PayPal) to charge the calculated amount. This creates a dynamic quote form where customers select services and see the price update automatically.

In the form settings under Email Notifications, create multiple notification rules. For each rule: (1) configure the recipient email (e.g., sales@company.com); (2) add a condition: only send this notification when “Department” dropdown equals “Sales”; (3) create another notification for Support (recipient: support@company.com, condition: Department = Support). When a visitor selects their department and submits, only the matching department’s notification fires. This eliminates manual routing for inquiry forms.

Yes — Forminator free includes Stripe and PayPal payment collection. Unlike WPForms (which requires the $199.50/year Pro plan for payments), Forminator processes payments in the free version. Stripe charges its standard processing fees (typically 2.9% + 30¢ per transaction) but the plugin itself does not add a surcharge or require a premium tier for payment functionality. This makes Forminator exceptionally cost-effective for simple payment forms.

Yes — Forminator supports two quiz types. Knowledge Quizzes assign points to correct answers and display a score result at the end. Personality Quizzes assign answers to personality types and show the matching type when complete (like Facebook-style “Which character are you” quizzes). Both quiz types can display custom results based on score ranges or personality type matches. Embed quiz results on a results page, share via social media integration, or collect email addresses before showing results as a lead generation tool.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.