Block Form Submission in WordPress: 5 Simple Steps

Some forms should not be sent yet. A support form for an order that is not paid. A booking for a date that is full. An application from someone who has not accepted the terms. In each case you want to block form submission in WordPress until the answers are right, and you want to tell people why instead of leaving them to guess.

This guide explains when to block form submission, why simply hiding the button is a weak answer, and how to set it up with Submit rules in FillKite Pro in five simple steps. For a longer guide with live examples, see form submission rules.

When should you block form submission?

Block a form when sending it would waste your time or break a process. These are the common cases:

• Unpaid orders. Support requests that only paid customers should send.
• Missing agreement. A contract or a waiver that must be accepted first.
• Not eligible. A form for people over a certain age, or from certain regions.
• Not ready. A request that needs an order number or a document before anyone can help.
• Contradicting answers. Two answers that cannot both be true, such as a delivery date before the order date.

Why hiding the button is not enough

The quick fix is to hide or disable the Send button with conditional logic. It works for a demo, but when you only hide the button instead of choosing to block form submission properly, you get four problems:

1. It says nothing. People see a button vanish and do not know what to change.
2. It lives in the browser. If JavaScript fails, or someone sends the form another way, nothing stops it.
3. It is hard to read for assistive technology. A button that disappears can confuse screen reader users.
4. It cannot offer a way out. A visitor with an unpaid order needs a link to pay, not a missing button.

How Submit rules work in FillKite Pro

Submit rules are rules on the whole form, written with the same editor as field logic. When a rule holds, three things happen. The Send button looks faded and is marked as unavailable to screen readers, a message appears under it, and an optional link lets the person fix the problem.

The same rule is checked again on your server when the form arrives. So it also works without JavaScript and when someone skips the browser, and nothing is saved while a rule holds. Because the button is marked unavailable instead of being removed, keyboard and screen reader users still find it and hear why it will not send.

How to block form submission in 5 simple steps

1. Open the form. In the FillKite builder, go to the Settings tab and choose Submit rules.
2. Build the rule. Pick a field, a condition and a value, the same way as for field logic. For example: Is the order paid? is No.
3. Write the message. Say what is wrong and what to do, such as “The order must be paid first”.
4. Add a link. Optional, but useful: “Pay now”, “Sign in” or “Read the terms”.
5. Choose a look and save. A warning look for something fixable, an error look for something final. Then update the form.

Example: support for paid orders only

A shop wants support requests only from customers whose order is paid. The form asks for the order number, the question “Is the order paid?” and a message. The Submit rule says: when Is the order paid? is No, show “The order must be paid first” with a “Pay now” link.

A visitor who picks No sees the Send button fade and the message appear straight under it. A visitor who picks Yes can send the form at once. You can try exactly this form on the paid order support demo. Nothing you type is saved or sent.

Write a message people can act on

When you block form submission, the message is the whole experience. A rule is only as good as its message, and these habits help:

• Say what is wrong, then what to do. “Please confirm your age first” is better than “Not allowed”.
• Be calm. The visitor did nothing wrong. Use the warning look, not the error look, when they can fix it.
• Link to the fix. One link, with plain words on it.
• Keep it short. One sentence, under the Send button, where people are looking.

Submit rules or field logic?

Both use the same rule editor, so they feel alike. The difference is what they control. Field logic changes what a visitor sees inside the form (read the conditional logic guide). Submit rules decide whether the form may be sent at all. If you want to block form submission, use Submit rules; if you want to change the questions, use field logic. You can see many forms that use logic on the demo forms page.

Frequently asked questions

Can I block form submission in WordPress without code?

Yes. In FillKite Pro you block form submission by writing a rule as a sentence in the form settings, add a message and save. No code is needed.

Does it work if JavaScript is off?

Yes. The rule is checked again on your server, so a form that should not be sent is refused even without JavaScript. Nothing is saved.

Is it accessible?

The Send button is marked as unavailable instead of being removed, and the message sits right under it, so keyboard and screen reader users can find it and hear why the form will not send.

Can I have more than one rule?

Yes. Each rule has its own condition, message and look, so you can block for different reasons with a different message each.

Is this part of the free plugin?

Submit rules are part of FillKite Pro, on every plan. The free plugin shows them as a locked card so you can see what they do.

Last updated: October 9, 2026