Your docs say it works. Line 41 says it doesn't.

Plugin tickets are bug reports in disguise. Repile clones the customer's site, runs the exact release they have installed, and points at the line that broke. If the bug is yours, the GitHub issue is already written.

Start with Pro See pricing

WordPress.org topic

formwise · 3.4.2

“Emails stopped sending after 3.4”

Triaged: real bug
Sandbox built
Checked out [email protected]
Cause found

includes/class-mailer.php

40$from = get_option( 'formwise_sender' );

41if ( ! is_email( $from ) ) return false;

42$headers = [ "From: $name <$from>" ];

GitHub issue openedReply drafted. Waiting for you.

Customers describe symptoms. You need a verdict.

Repile doesn't stop at a likely answer. It reproduces the failure and comes back with one of two things: your line, or proof it isn't yours.

~~“Emails stopped sending after 3.4”~~
Your bug
Updating to 3.4 left the sender setting empty, so line 41 skips every email. Issue opened with the steps, evidence and failing line.
~~“Fatal error on PHP 8.3 after activating”~~
Your bug
An unguarded count(null) in class-settings.php. A workaround for the customer today, a fix for the next release.
~~“Your checkout button does nothing”~~
Not yours
Your handler is fine. The theme's sticky header covers the button on phones. CSS fix tested in the sandbox, ready to send.

It reads the code they run. Not the code you wish they ran.

Your help center was written before the bug existed. Repile checks out the release on the customer's site and reads that. Free and Pro live in separate projects, each with its own instructions and memory, so answers never cross over.

Formwisegithub.com/formwise/formwise

3.3.23.4.13.4.2 · customermain

Memory · Customers on PHP 8.3 need 3.4.1 or later.

Formwise ProIts own repo, instructions and memory

separate project

The issue is filed before you've read the topic.

Your WordPress.org forum lands in Repile like any other ticket. When the bug is yours, your developers get an issue they can act on.

01Topic lands
Forum, FreeScout or Help Scout. Same queue.
02Site cloned
Same WordPress, PHP and plugin versions.
03Failure reproduced
Triggered in a real browser, with evidence.
04Line found
File and line for every claim.
05Issue and draft
One click posts the reply from your account.

formwise/formwise · issue

Emails silently skipped when the sender is empty

Open · linked to the forum topic

Reproduced on WP 6.6.2, PHP 8.2
includes/class-mailer.php:41 returns before wp_mail
Fix: fall back to the admin email and log it

WordPress.org support forum

Drafted by Repile

Thanks for the report. Updating to 3.4 left the sender address empty, so emails were skipped. Set one under Formwise › Email and they'll go out again. The next release falls back to the admin email.

Post to forum

Straight answers.

Anything else? Write to [email protected] and a human answers.

Does it handle free and Pro?

Yes. One project per product, unlimited on every plan. Repile reads the release the customer runs.

What if the bug is ours?

You get a GitHub issue or PR with the steps, evidence and failing line, linked to the ticket.

Does it post on our forum?

Only when you click. It posts from your own account, and your WordPress.org password never leaves your Mac.