Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Hello @stumur,

    Thank you for reaching out and for the detailed explanation — that makes the workflow very clear, and it is absolutely something we can help you streamline.

    You can get very close to your ideal workflow by adding a custom “Click here to Approve this band” link inside the email using the mailto: method.

    In your “Email Notification” (the one you receive as an admin), you can add something like this:

    <a href="mailto:{email}?subject=Your Band Submission Has Been Approved&body=Thanks for your band submission.%0A%0AWe are pleased to invite you to create a profile page on our Live Music Agency website by filling out the details in our new bands sign-up form:%0A%0Ahttps://thelivemusicagency.com.au/new-bands-sign-up-form/%0A%0AKindest Regards,%0AThe Live Music Agency">
    Click here to Approve this band
    </a>

    Note: Please make sure you replace {email} (in the above code) with the actual member’s email field tag from your form (see attached screenshot at https://ibb.co/xKZsZn7Q). Additionally, feel free to change the link text “Click here to Approve this band” to your own preference.

    For further information on how to create and edit “email notifications” inside Forminator Forms, please refer to the official documentation at https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#email-notifications-forms.

    The result would be a link that, by clicking it, a new email draft can open with:

    • the band member’s email address already filled in,
    • the subject line pre-populated, and
    • your message already written out.

    This gives you a very quick workflow: click the approve link, check the draft, and press send. See also the attached screenshot at https://ibb.co/6R64m6gs.

    Please note that while this link method works well in most cases, it does have some limitations. The exact behavior may vary slightly depending on your device or email client/app (such as Yahoo, Gmail, Outlook, etc), and formatting like line breaks may not always appear perfectly. Furthermore, if no default email app is configured on your device, it may not open properly.

    I hope this helps streamline your workflow. Please let us know if this answers your question or if you need any further assistance — we’ll be happy to help.

    Best regards,
    Mina Emad

    Hello @jquinn33,

    Thank you so much for your kind words and review! We’re really glad that Forminator is meeting your needs and that you’re enjoying both the functionality and the support experience.

    If there’s ever anything you need as you continue using Forminator across your client sites, please don’t hesitate to reach out — we’re always here to help.

    Thanks again for your trust and support, and have a great day!

    Best regards,
    Mina Emad

    Hello @jquinn33,

    Thank you for your response and kind words!

    I’m glad we were able to help you move forward with this. If you need any further assistance or run into anything else, please don’t hesitate to reach out — we’re always happy to help.

    Since everything is now working as expected and the topic is resolved, we’d truly appreciate it if you could take a moment to share your experience with Forminator and the support you received by leaving a quick review here: https://wordpress.org/support/plugin/forminator/reviews/#new-post

    Your feedback means a lot to us and helps others as well. Thanks again, and have a great day!

    Best regards,
    Mina Emad

    Hello @jquinn33,

    Just checking in on this — I wanted to see if you had a chance to try the suggested solution.

    Please let us know if it worked for you or if you’re still experiencing any issues. We’d be more than happy to assist further if needed.

    Looking forward to your update.

    Best regards,
    Mina Emad

    Hello @sewmagic,

    Thank you for your response and collaboration!

    We’ll be here and looking forward to hearing how it goes once you’ve had a chance to test everything.

    Please don’t hesitate to reach out if you run into any questions along the way.

    Best regards,
    Mina Emad

    Hello @alanintertec,

    Thank you for the update; it’s great to hear that the checkbox approach is working well for you!

    I’m glad we were able to help you move forward with this. If you need any further assistance or run into anything else, please don’t hesitate to reach out — we’re always happy to help.

    Since everything is now working as expected and the topic is resolved, we’d truly appreciate it if you could take a moment to share your experience with Forminator and the support you received by leaving a quick review here: https://wordpress.org/support/plugin/forminator/reviews/#new-post

    Your feedback means a lot to us and helps others as well.Thanks again, and have a great day!

    Best regards,
    Mina Emad

    Hello @sewmagic,

    Just checking in on this — I wanted to see if you had a chance to try the suggested solutions.

    Please let us know if it worked for you (and which solution) or if you’re still experiencing any issues. We’d be more than happy to assist further if needed.

    Looking forward to your update.

    Best regards,
    Mina Emad

    Hello @vanderk ,

    Thank you for your detailed report and for sharing all the context — this really helps a lot in narrowing things down.

    I’ve reviewed your case along with similar reports, and I’d like to clarify what’s happening and address your questions directly.

    What this error actually means

    The log message: “Cart simulation failed: Could not validate nonce” is not the root cause of an issue, but rather a warning generated during a background process.

    The PayPal plugin performs a cart simulation in the background to calculate totals before creating an order. If that request runs without a valid session/nonce, the validation fails and the log entry is created. This commonly happens due to:

    • Cached or stateless requests
    • Expired sessions
    • Background calls (not real user actions)

    1. Is this expected behavior or a real problem?

    Based on:

    • Your successful live transactions
    • No checkout failures reported
    • The errors occurring regularly even without users

    This is generally considered non-blocking behavior and can often be safely ignored from a functional standpoint. These logs are not necessarily tied to failed payments and are often just noise from background validation.

    2. Are there known issues with your plugin version?

    There are no confirmed widespread regressions tied specifically to your version (4.0.2) regarding this error. However, similar reports across versions indicate:

    • The message appears frequently in logs
    • It is usually not the root issue, but a side effect of caching or session handling

    3. Can this be disabled or adjusted?

    There is no official setting to fully disable cart simulation, as it’s part of how PayPal keeps totals accurate. However, you can try this PHP snippet on a staging/test website:

    add_filter( 'woocommerce_paypal_payments_simulate_cart_enabled', '__return_false' );

    However, it’s not guaranteed to resolve the logs and is generally not recommended unless needed for testing.

    Recommended next steps

    To confirm the source, we suggest:

    1. Temporarily enable Cloudflare Development Mode (or pause it briefly)
    2. Disable WP Rocket for a few minutes
    3. Monitor logs for 5–10 minutes

    If logs stop, it confirms a caching layer is triggering these requests. If everything is working fine on the checkout side, then this is very likely just log noise from background processes.

    Please note that within this forum, we focus on supporting WooCommerce core functionality. Since this behavior originates from the WooCommerce PayPal Payments plugin, the best place for deeper investigation or plugin-specific fixes would be their dedicated support channel:
    https://wordpress.org/support/plugin/woocommerce-paypal-payments/

    That said, if you notice any issues directly related to WooCommerce core features, please don’t hesitate to let us know — we’ll be more than happy to assist.

    Best regards,
    Mina Emad

    Hello @jquinn33,

    Thank you for sharing the form exports — that helped us take a closer look.

    I was able to reproduce the issue on my end, and it comes down to a small mismatch in the currency settings between two fields in the form.

    What’s happening

    Each form includes:

    • A currency/number field (used to define the amount)
    • A PayPal field (which uses that amount dynamically)

    On the French version of your form, the PayPal field is correctly set to CAD, but the amount field (“Montant par carte-cadeau”) is still set to USD.

    How to fix it

    Please update the currency in the amount field to match CAD:

    1. Go to Forminator → Forms → Edit your French form (“Gift Card Order Form – Fr”)
    2. Click on the field named “Montant par carte-cadeau”
    3. Navigate to the field “settings” tab
    4. Change the currency from USD to CAD (see the attached screenshot at https://ibb.co/YBKdyKCW)
    5. Save the form and test again

    For further information on the currency field settings, please refer to the documentation at https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#currency-settings.

    Once you update the setting to CAD in that field, the correct currency should display on the front end.

    Please let us know how it goes or if you’d like us to double-check anything further.

    Best regards,
    Mina Emad

    Hello @jquinn33 ,

    Thank you for sharing the export code — we appreciate it.

    It looks like the code may have been affected by the forum editor formatting (this can sometimes modify characters or spacing when pasted directly), which makes it difficult for us to properly import and test the form.

    Could you please share the export again using an external tool like https://pastebin.com? This will preserve the formatting exactly as needed. Here’s how to do that:

    1. Copy the full export code of both forms
    2. Go to https://pastebin.com
    3. Paste the code there and create a new paste
    4. Share the link(s) with us here

    This will allow us to accurately import the forms and continue the investigation.

    Thanks again for your cooperation — looking forward to your update.

    Best regards,
    Mina Emad

    Hello again @alanintertec ,

    Thank you for sharing the form export — that was very helpful.

    I’ve been able to reproduce the issue on my end, and it appears to be related specifically to visibility conditions involving file upload fields.

    What’s happening

    When a required field of any type (e.g., the “Date images where taken” fields) has a visibility condition based on a file upload field (e.g., the “Upload Images” fields) being empty (null) or not empty (i.e., Show/Hide the “Datepicker field” When the “file upload field” Is/Is not empty [null]), the following occurs:

    • On the front end, the visibility logic works as expected
    • However, on submission, the server-side validation fails, resulting in the error:
      “Your form is not valid, please fix the errors!”

    How to solve

    While rolling back to v1.52.1 (or older versions) appears to resolve the issue, please note that older versions may lack important security updates and improvements included in the latest release.

    As a temporary workaround, we recommend:

    • Avoid using file upload fields (“Upload Images”) in visibility conditions, especially when:
      • The condition checks for empty/null values
      • The affected fields (“Date images where taken”) are marked as required

    If possible, you can:

    • Replace the condition with another field type (e.g., checkbox, select, etc.), or
    • Remove the required constraint from fields controlled by such conditions

    Next Steps

    We will escalate this to the development team for further investigation, as this behavior is not expected and should be addressed in a future update.

    If you have any additional examples or edge cases, feel free to share them — they can help speed up the fix.

    We really appreciate your thorough testing and patience while we look into this. Please don’t hesitate to reach out if you need help adjusting the form in the meantime.

    Best regards,
    Mina Emad

    Hello @alanintertec ,

    Thank you for the update on your issue.

    Please note that we’re not allowed to have the login credentials shared here or log in to the website.

    You can simply commence by sharing a link to your test form page and the export of the form with us here, and we will help debug the issue.

    To export your form:

    • Go to Forminator → Forms in your dashboard
    • Click the gear icon next to the form
    • Select Export
    • Copy the export code
    • Paste it at https://pastebin.com
    • Share the link with us here

    Note: This export does not include any submitted data — your entries remain safe on your site.

    Once we have that, we’ll investigate further and help you get this resolved.

    Best regards,
    Mina Emad

    Hello @pressonforlife ,

    Thank you for reaching out!

    At the moment, Forminator doesn’t provide a built-in option to create an “Inline Form” directly in the form settings. However, it can be customized using a small CSS snippet.

    First, make sure you’ve created a form with only an “email” field and the “submit” button. You can do so via Forminator → Forms → Add New Form. You can create a new “blank” form or start with a “Newsletter Signup” form template.

    Second, go to Forminator → Forms → Edit Form → Appearance Custom CSS → Enable Custom CSS, then past the foloowing code there:

    .forminator-row:nth-child(2) {

    margin-right: 0;

    }


    button#forminator-submit {

    width: 100%;

    display: block;

    }

    #submit {

    display: block;

    }


    @media only screen and (min-width: 783px) {

    .forminator-row:nth-child(2) {

    float: left;

    width: calc(100% - 120px);

    margin-right: 10px;

    display: inline-block;

    }


    #submit {

    display: inline-block;

    }

    }

    Third, feel free to style the “email” field and the “submit” button to your preference. You can simply achieve this using the options in the Appearance tab of the form settings.

    Please let us know if this answers your question or if you need any further assistance — we’ll be happy to help.

    Best regards,
    Mina Emad

    Hello @weju ,
    Thank you for reaching out!

    At the moment, Forminator doesn’t provide a built-in option to style the “No file chosen” text directly in the form settings. However, it can be customized using a small CSS snippet:

    .forminator-file-upload > span[data-empty-text="No file chosen"] {

    color: #d31717 !important;

    }

    Note: Make sure you update the CSS snippet with the color you prefer.

    You can add the CSS code via Forminator → Forms → Edit Form → Custom CSS → Enable Custom CSS, then past the code there.

    Please let us know if this answers your question or if you need any further assistance — we’ll be happy to help.

    Best regards,
    Mina Emad

    Hello @marcosquare ,

    Thank you for reaching out — I understand how frustrating this behavior can be, especially during checkout.

    From your description, this does not sound like the default WooCommerce checkout behavior. It indicates that the checkout flow is being modified by a third-party theme or plugin. To help isolate the issue, we’ll need to narrow down what’s customizing your checkout.

    To help us investigate further, could you please share with us the following:

    • A link to your checkout page
    • A screen recording of the issue (if possible)
    • Your WooCommerce System Status Report:
      • Go to WooCommerce → Status
      • Click “Get system report”
      • Paste it to https://pastebin.com and share the link here

    Once we have this information, we’ll be able to take a closer look and guide you toward a solution.

    Best regards,
    Mina Emad

Viewing 15 replies - 1 through 15 (of 20 total)