• Hi,

    I’m getting a weird error. All my auto exports are sending emails (via SMPT) with a .tmp file (that then gets blocked by email client but that is normal), not a csv. If I do it manually, it works perfectly.

    I’ve rolled back the versions, checked permissions but can’t find anything. I think the first day it happened was the 14th of October and since then it’s been the same.

    Any ideas?

    Thanks

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter scmo1910

    (@scmo1910)

    So, a little more info.

    Rolled back to version 1.58 and it works. Also did a little PHP diving and checked email logs and forminator logs. Apparently it’s either the renaming of the tmp file to csv or the mail routines not being able to find the file due to the paths. But I will keep digging.

    Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    Hi @scmo1910,

    I hope this message finds you well and sorry to know that you are experiencing an issue.

    I was unable to replicate the issue on my end, and there aren’t any similar issues reported on our end. It appears to be an issue specific to your website’s environment.

    Can you please confirm if you tried performing a conflict test to ensure no other plugins is conflciring and causing an issue? If not yet, can you please give that a try which helps to ensure no other plugin is conflcting and causing an issue?

    The following documentation should help you further: https://wpmudev.com/docs/getting-started/getting-support/#conflict-test

    As this is a live website with traffic, please create a staging website and perform the test without disrupting the live traffic. A staging website is a copy of your live website in a new directory on the same server using a separate database.

    Please feel free to get back to us if you need any further clarification, we are here to help.

    Best Regards,
    Nebu John

    Hello,

    Scheduled submission exports no longer arrive with their CSV attachment
    when sent through the Brevo mailer in WP Mail SMTP.

    The issue still occurs with Forminator 1.58.4.

    Comparing older and newer WP Mail Logging records, the attachments field
    has changed from a named CSV file to a randomly named temporary file.

    Working export — 12 October 2026:
    “attachments”: “/forminator/research-261015230769.csv”

    Affected export — 2 November 2026:
    “attachments”: “forminator-export-OyRtsskEAGspYyGT-dsDVtX.tmp“

    Both records show:
    “error”: null

    Test results:

    • Through WP Mail SMTP’s Brevo mailer, using an API key, the email
      arrives but the export attachment is missing.
    • In a test using a non-Brevo sending route, the email arrived with
      a CSV attachment, even though WP Mail Logging still recorded
      a .tmp attachment.

    This suggests an interaction between the way the scheduled export
    attachment is provided and the Brevo mailer, but I have not established
    which component causes it.

    Could you please investigate:

    1. Whether the change from a named .csv file to a .tmp file is intentional.
    2. Where and how the final .csv attachment filename is assigned.
    3. Whether that filename is passed in a way that API-based mailers,
      including WP Mail SMTP’s Brevo mailer, can preserve.

    Environment:

    • Forminator: 1.58.4
    • WP Mail SMTP: 4.10.3
    • WordPress: 7.1.4
    • PHP: 8.5.12
    • Mailer: Brevo in WP Mail SMTP, using the Brevo API, not SMTP relay

    I can provide additional sanitized logs if needed.

    Thank you.

    Plugin Support Fida – WPMU DEV Support

    (@fidawpmudev)

    Hello @obylu ,

    I hope you are doing well, and thank you for the update.

    I am glad that the issue is resolved for you. To identify which plugin or services were conflicting, you can run a conflict test as mentioned above https://wordpress.org/support/topic/wrong-export-file/#post-19059516

    Kind Regards,
    Fida Al Hasan

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.