Bit Form Global Settings – Customize Your Forms Across All Pages

Manage key site-wide settings effortlessly with Bit Form Global Settings. From customizing validation and error messages to enabling secure token generation after page load (to prevent conflicts with cache plugins), everything is centralized. You can also opt in to usage reporting and choose to delete all form data tables when uninstalling the plugin—giving you full control over your form behavior and data management.

In this documentation, we’ll walk you through the key features available under Bit Form’s Global Settings. You’ll learn how to customize Validation Error and Invalid Messages, how to generate a token after page load to prevent conflicts with cache plugins, how to automatically delete all data tables when uninstalling the plugin, and how to opt in to anonymous usage reporting. These global settings help you manage form behavior and data handling across your entire WordPress site from one central location.

Bit Form Global Settings

To configure your Global Settings in Bit Form, start by going to the Bit Form dashboard. Then click on App Settings, and from there, select General. Inside the General section, you’ll find the Global Settings option where you can manage site-wide form configurations.

Validation Error/Invalid Message

This setting allows you to define default validation error and invalid messages for all form fields across your site. For example, if you have multiple forms with required fields like email, users will see a standard error message if they leave it blank. While you can set these messages individually in each form’s field settings, doing so for many forms can be time-consuming. With Bit Form’s Global Settings, you can configure these messages once and apply them universally.
If you need a unique message for a specific form or field, you can still override the global setting within that form’s local configuration. Form-level settings always take priority over global settings when both are defined.

Let’s look at how to use the Bit Form Global Settings – Validation Error/Invalid Message by taking the Required Field as an example. This will help you understand how global validation error or invalid messages are applied across all forms.

Required Field: A Required Field is a form field that must be filled in before the form can be submitted. If it’s left empty, an error message will appear asking the user to complete it.

To edit a global error message in Bit Form, simply click the edit icon next to the message. A popup will appear, allowing you to customize the message text as needed.

In the editor, you can customize the error message to fit your needs. You’ll also see shortcodes available within the editor—these are especially useful for dynamically inserting field names or other relevant details into your messages.

Shortcodes

Shortcodes are placeholders you can use in your error or validation messages to automatically insert specific values—like the field label or size limits. When the form is displayed to users, Bit Form replaces these shortcodes with actual values. This makes your messages more dynamic, informative, and user-friendly.

Available Shortcodes in Global Settings – Validation Error/Invalid Message

Use the following shortcodes in your global validation and error messages to make them dynamic and user-specific. Here’s what each shortcode does and where it applies:

• “${field.label}” – Displays the label of the field (e.g., “Email”, “Name”).
  Usage: Applicable to all field types.
• “${field.minimum}” – Inserts the minimum allowed value or character count.
  Usage: Used in Number, Text, and Textarea fields.
• “${field.maximum}” – Inserts the maximum allowed value or character count.
  Usage: Used in Number, Text, and Textarea fields.
• “${field.minimum_file}” – Shows the minimum number of files required.
  Usage: Applicable to File Upload fields.
• “${field.maximum_file}” – Shows the maximum number of files allowed.
  Usage: Applicable to File Upload fields.
• “${field.maximum_size}” – Displays the maximum file size limit (usually in MB).
  Usage: Applicable to File Upload fields.

After customizing your error message, simply click the Save button to apply and store your changes.

Generate Token after page load to prevent conflict with cache plugins

This option is designed to help prevent issues caused by cache plugins on your WordPress site. When enabled, Bit Form generates a unique security token (nonce) after the page has fully loaded, instead of including it in the initial cached HTML.

What Does It Do?

• Prevents Token Mismatch Errors: Cache plugins often save and serve static versions of pages, including outdated tokens. This can cause errors when users try to submit a form.
• Improves Form Security & Compatibility: By generating the token after the page loads, Bit Form ensures the token is always fresh and valid—improving compatibility with caching systems.

Delete all data table when delete plugin

This setting controls whether all Bit Form-related database tables and form data should be permanently deleted when you uninstall the plugin from your WordPress site.

What Does It Do?

• Cleans Up Your Database: When enabled, all data created by Bit Form—including form entries, settings, and configurations—will be removed along with the plugin.
• Useful for Complete Uninstalls: Ideal if you no longer plan to use Bit Form and want to fully clean up your WordPress database.
• Use With Caution: If you think you might reinstall Bit Form later or need to keep your form data, it’s best to leave this option disabled.

Usage Reporting Opt In

This setting allows you to voluntarily share anonymous usage data with the Bit Form development team to help improve the plugin.

What Does It Do?

• Helps Improve Bit Form: By opting in, you allow Bit Form to collect non-sensitive, anonymous data such as plugin usage patterns, WordPress version, PHP version, and active features.
• No Personal Data Collected: The data shared does not include any personal information or form entries.
• Totally Optional: You can choose to opt in or out at any time—your experience with the plugin will not be affected either way.