Changelog
What's changed in each version of the forms, newest first. All four forms (contact, quote request, appointment request and callback request) share the same engine, so these notes apply to all of them.
FreeContactForm has been available since 2005. This changelog starts with the 2026 rewrite.
Download the latest version.
To upgrade, replace the fcf-assets folder and keep your fcf-config folder. Each download includes docs/UPGRADING.md with the details.
Versions:
Version 2026.1.1
Upgrade by replacing the fcf-assets folder. Your fcf-config folder keeps working as it is; the one new setting is optional.
Added
TRUSTED_IP_HEADER(optional, in the spam protection section). Behind Cloudflare or another proxy, set it to the header that carries the visitor's real address (CF-Connecting-IPfor Cloudflare), so visitors no longer share one per-visitor limit and{IP}shows the visitor rather than the proxy. Empty by default.- The self-test page warns when the site is behind Cloudflare and this isn't set, and shows the visitor address the form sees.
Changed
- IPv6 visitors are counted per /64 network for the per-visitor limit, so one connection can't get round it by switching addresses.
- Rate-limit counters are kept in a private sub-folder of the server's temporary folder (permissions 0700). If the folder can't be made private, the limits switch off instead of using a folder other accounts can change.
- Old counters are removed automatically once they are older than the longest limit window.
- The credit line under the form now names the type of form and links to its page on freecontactform.com.
- Clearer licence (see the licence): the form can be used on websites you build for clients, as long as the credit link stays visible.
Version 2026.1.0
A major rework. If you are coming from the 2024 release, read docs/UPGRADING.md.
New layout. Your settings, email templates, field rules and colour tweaks now live in fcf-config/. Everything else is in fcf-assets/ and can be replaced wholesale when a new version is released.
Requires PHP 8.2 or newer.
Removed
- The auto-responder (
SEND_AUTO_RESPONSE,EMAIL_OUT_*, thefcf.email-out.*templates). It could be abused to send your branded email to anyone. - Leftover code from the Pro version (reCAPTCHA messages, file-upload checks).
Changed
- Sending through an SMTP mailbox is now the default (
USE_SMTPisYES, port 465 / SMTPS filled in). You create a mailbox on your hosting and enter its server, login and password. PHP'smail()is still available by settingUSE_SMTPtoNO. EMAIL_FROMcan be left empty when sending through SMTP: the mailbox you log in with is used.EMAIL_FROMmust be a fixed address on your own domain. It can no longer be taken from the form (mail "from" a visitor's address is rejected or sent to spam by most providers). The visitor is still the Reply-To.fcf.default-custom.cssis nowfcf-config/css/fcf.custom.css.- The browser-side field rules moved out of
fcf.form.jsintofcf-config/fcf.rules.js. - The attribution link now stays visible after a message is sent.
- Debug output is collected and shown once, instead of streaming to the visitor.
- SMTP timeout is 20 seconds (was 5 minutes).
Added
- Spam protection with no account needed: honeypot, minimum-time check, a per-IP rate limit, and a cap for the whole website (
SITE_LIMIT_MAX, default 30 per hour) so a spam flood cannot use up your host's hourly sending allowance. - Optional log file for problems (never contains messages, names, emails or IPs).
- DKIM signing settings.
- A self-test page (
fcf-assets/fcf.selftest.php), off until you set a token. docs/DELIVERABILITY.mdanddocs/UPGRADING.md.- Error messages are linked to their fields for screen readers, and the keyboard focus moves to errors and to the thank-you message.
- Missing translations fall back to English.
Fixed
- Crash (PHP 8) when a request sent a list instead of text for a field.
- An optional Reply-To, or a CC/BCC name without an address, caused an error.
- Email addresses on newer domain endings (such as
.photography) were rejected. - Length limits counted bytes instead of characters.
{IP}could be faked by the visitor and was not escaped.- A submitted value containing
{Message}could be expanded a second time. SMTP_SECUREwas ignored unlessSMTP_AUTHwas YES.- A language file containing a semicolon in its text was corrupted.
- Opening the PHP files directly in a browser showed errors.