Fillin Forge Changelog

Release notes of Fillin Forge (the free plugin) and Fillin Forge Pro (the add-on), newest first. They are the Changelog sections of the readme files of the two packages. Free and Pro have their own version numbers. A line that applies to only one of the two builds of the free plugin is left out, and so is a release made of such lines only.

Fillin Forge (free plugin)

1.2.6

• If WP-Cron does not start a Fillin Forge task on time (a retry that adds a booking to your calendar, a row for Google Sheets, a payment check) and the task is more than 15 minutes late, the Fillin Forge screens now tell administrators, and the notice can be hidden for a day. The button “Run them now” starts up to 10 such tasks per press.
• Tasks that Fillin Forge Pro handles are neither run nor removed while Pro is off or too old, and the notice says so.
• On a site with DISABLE_WP_CRON the notice advises a system cron job and links to how to set one up.
• The payment number in e-mails, Slack messages and webhooks is now labelled “Payment ID”, as on the submission screen. Before, it said “Payment intent”.
• Deactivating Fillin Forge now removes its scheduled retries for calendar events and Google Sheets rows. Before, retries that carried data stayed in the queue.
• The new texts are translated into the 15 languages the plugin ships in.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.5

• If you take bookings into Google Calendar, update Fillin Forge Pro to 1.3.6 as well. With an older add-on the link below already works, but a booking whose event could not be created is neither marked nor reported.
• Submissions: a booking whose calendar event could not be created (Fillin Forge Pro 1.3.6 marks it) shows its own sentence next to “Time not confirmed”, in the list and in the submission window: check your calendar, add the event if it is not there, and confirm the time with the visitor.
• The e-mail “Time not confirmed in the calendar” has its own wording for an event that could not be created: its subject ends with “the event could not be created”, and the text says to check the calendar and add the event if it is missing.
• The link in that e-mail now opens the Submissions list on the page that holds the submission and scrolls to its row. Before, it opened the first page of the list, and an older submission could be pages away.
• The new texts are translated into the 15 languages the plugin ships in.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.4

• If you take bookings into Google Calendar, update Fillin Forge Pro to 1.3.5 as well. With an older add-on the time picker below already works, but a booking whose time could not be confirmed is neither marked nor reported.
• Time picker: on a form that books into Google Calendar (Fillin Forge Pro), when the free times cannot be loaded, the picker now says “Could not load free times. Please try again later.” and offers no time, where it used to show every time of the day as free. Without Pro, or after the Pro trial has ended, nothing changes here.
• Time picker: the same message shows when the request for the free times fails altogether or its answer cannot be read. The browser used to offer every time of the day unchecked.
• Time picker: when the date is changed quickly, a late answer for an earlier date no longer replaces the times of the date shown now, and no longer clears the time already picked.
• Submissions: a booking whose time was not put in the calendar shows “Time not confirmed” in the list and in the submission window, with a sentence on what to do. Fillin Forge Pro 1.3.5 sets the mark.
• A short e-mail “Time not confirmed in the calendar” goes to the form’s notification address for such a booking. Fillin Forge Pro 1.3.5 asks for it; a form with its admin notification switched off gets none.
• The new texts are translated into the 15 languages the plugin ships in.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.3

• If you take card payments, update Fillin Forge Pro to 1.3.4 as well, and Pro first. The add-on now confirms every payment with Stripe. With an older Pro a notice asks you to update it, and every paid submission is saved as “Payment not confirmed” until you do (they are checked again by themselves afterwards).
• Payments: a card payment is no longer saved as paid just because a payment id came with the form. Fillin Forge asks Fillin Forge Pro to confirm the payment with Stripe, and the amount saved with the submission is the one Stripe holds, not the one the browser reported.
• Payments: a payment that does not exist, belongs to another form, was not paid or already belongs to another submission is refused, and the visitor is told that the payment could not be verified.
• Payment statuses in words: a submission paid for another amount than its values come to is kept as “Paid amount differs”, a payment nobody could confirm yet as “Payment not confirmed”, and one Stripe holds no completed payment for as “Not paid”. The notification, the list, the submission, the PDF and the export say so, with a sentence on what to check.
• The submission shows a “Check payment in Stripe” button (from Fillin Forge Pro 1.3.4) for a payment that is not confirmed yet.
• Saving a form tells you when a payment amount comes from a calculation the server cannot repeat.
• Payment field: the editor opened an old fixed payment amount in a currency without hundredths (JPY, for example) divided by 100, so 1000 yen showed as 10.00 and was saved as 10. It now shows the amount as it was typed.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.2

• If you take payments in a currency without hundredths (JPY, KRW, VND, CLP, or another one Stripe counts in whole units: BIF, DJF, GNF, KMF, MGA, PYG, RWF, VUV, XAF, XOF, XPF) and got around the old mistake below by typing a price 100 times smaller, put the real price back as soon as Fillin Forge Pro 1.3.3 is installed, because the fix for the charge is in the add-on. After that a price is charged exactly as typed, so the small price would be charged as the small price.
• Payment amounts: every currency was counted in hundredths, so a price of 1000 JPY in the payment field was charged as 100,000 JPY. Amounts are now counted in the currency’s own unit (whole yen for JPY, cents for USD), and the amount saved with a submission is shown the same way, for example JPY 1,000 or USD 10.00. The payment field itself is in Fillin Forge Pro, so if you run the add-on, update it to 1.3.3 as well.
• Rating field: clicking a star now tells conditional logic and calculations, so a field that shows, hides or adds up depending on the rating changes straight away.
• Templates: Market Research and General Survey no longer bring a page break field, which only works with Fillin Forge Pro. Without it, saving turned that field into a text input labelled “(Requires Pro)”; now the form is a single page. In Internship Application the graduation year list starts at the current year, and in Service Appointment the vehicle year goes up to next year, instead of years fixed in advance.
• The rule for which fields of a form hold a value is now kept in one place, so the Google Sheets rows of Fillin Forge Pro keep their columns in the form’s order.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.1

• Deleting the last Forge plugin or add-on on a site now removes everything Forge stored on the site, on every site of a network: the statistics settings and the install ID, the shared job queue with its scheduled events, and the other settings and caches the Forge plugins share. While another Forge product stays, only this plugin’s own share goes.
• A Forge plugin deleted a moment earlier in the same bulk delete is no longer counted as still installed, and a Forge plugin for WooCommerce no longer keeps the shared data on the site for good.
• Needs Fillin Forge Pro 1.3.0 or newer if you run the add-on, as before.

1.2.0

• This release needs Fillin Forge Pro 1.3.0 or newer if you run the add-on. The licence layer is the add-on’s alone now: the free plugin no longer loads any licence code (the wordpress.org package has none at all), and its Settings screen asks the add-on, not a licence key, whether Mailchimp, HubSpot and Google can be connected. An older add-on is kept from starting. A notice, shown only to a user who can update plugins, names the version it needs and links to the downloads page of your Avakode account.
• Fixed: the form editor’s preview ended in an error, because the preview request called a check that had been renamed. It now runs the same checks as saving a form.
• Fixed: with an out-of-date Fillin Forge Pro add-on installed, saving a form no longer turns its Pro fields into text or switches its Pro settings off, so the add-on’s update finds them as they were. The cards of the form editor that ask for the add-on say to update it, with a link to the download, instead of offering it for sale.
• With the add-on active, an AI generation error that needs your Avakode account opens the Fillin Forge Pro settings instead of a dashboard screen that this plugin does not have.
• The changed lines are translated in all 15 shipped languages.

1.1.0

• New: a “Send a test submission” button in the form editor. It sends one sample submission through the saved form by the same code a visitor’s submission goes through (validation, the saved record, the notification email), so you can check a form without filling it in. The record is marked Test; the notification email starts with “[Test]” and says it is a test; any email field gets your own address, so the auto-reply comes to you. reCAPTCHA is not asked for, and nothing goes on to webhooks, integrations, post or user actions or analytics.
• When a form cannot be tested, the button says why in plain words: a required file upload, a payment field, a required field whose pattern or length limit no sample value can meet, or an admin page opened at a different address from the site’s.
• Test submissions are left out of the counts, the exports and the analytics, and out of the REST submissions list unless it is asked for status=test.
• A star rating must be a whole number from 1 up to the field’s number of stars. A rating of 0 counts as “not rated”: an optional field accepts it and a required field asks for a rating.
• Fixed: every Fillin Forge admin screen raised a PHP warning, and the builder preview linked a stylesheet the free plugin no longer ships. The conversational layout’s stylesheet now comes from the Pro add-on.
• The new lines are translated in all 15 shipped languages.

1.0.41

• Deleting the plugin leaves the job queue the Forge plugins share in place while another Forge plugin or add-on is still on the site. The check used to miss add-ons, and Rank Forge installed from wordpress.org, so the queue could be dropped while a neighbour still had jobs in it.

1.0.40

• Internal clean-up in the documentation of a shared helper; no change in behaviour.

1.0.39

• This release needs Fillin Forge Pro 1.2.0 or newer if you run the add-on. The free plugin no longer checks licences at all: the Pro features – the Stripe payment field, Google Sheets, WhatsApp, HubSpot, conversational forms, analytics and AI generation – now carry their own code and their own licence check inside the add-on. An older add-on is switched off whole rather than left half-working.
• The free plugin no longer loads anything from Google or Stripe on its own screens; those scripts come with the add-on.
• Request input is sanitised where it is read, and admin output is escaped.

1.0.38

• This release needs Fillin Forge Pro 1.1.0 or newer if you run the add-on. An older add-on is switched off whole rather than left running, because beside this core it would be present and wrong rather than absent. Until you update it Post Submission, User Registration, multi-step and conversational forms, payment, repeater and calculation fields, AI form generation and the analytics screens are unavailable. Forms already saved and the submissions already collected are untouched, an admin notice names both versions and what stopped, and installing the current add-on brings all of it back.
• Deleting the last Forge product on a site now clears the job queue the Forge plugins share – its table, its two scheduled events and its version marker. While any other Forge product is still installed, deleting this one leaves the queue exactly as it is, because the pending jobs in those rows are that product’s too.
• The Conditional Logic section no longer shows a PRO badge – conditional logic is part of the free plugin.
• Admin screens load their scripts and styles through WordPress instead of inline tags, and file writes go through the WordPress filesystem API.

1.0.35

• Smaller package and one less admin surface: the SDK’s own menu, opt-in screen and promotional notices are gone.

1.0.31

• The appointment picker now generates its time slots on any install. Overlaying real busy times from a connected Google Calendar still needs the separate Pro add-on, which holds the OAuth application.
• Removed licence checks that could never fail, on conditional logic, file uploads and webhooks. Those have been free for some time, but the code still asked and the admin screens still showed a PRO badge.
• Availability of add-on features is now decided by whether the add-on is installed, not by a licence call.

1.0.30

• Security hardening: all dynamic output is now escaped late at the output site with the context-appropriate function (esc_html/esc_attr/esc_url, esc_html__ for translated strings used as format strings, and wp_kses for trusted pre-built admin/field markup). No behavioural changes.

1.0.29

• Pro-only features (Post Submission, User Registration, multi-step forms, conversational mode, repeater and calculation fields) are now provided entirely by the Fillin Forge Pro add-on and are no longer bundled in the free plugin – the free download contains only fully-functional free features.
• Removed the leftover form-count limit scaffolding; the free plugin has always supported unlimited forms.

1.0.28

• Uninstall cleanup now removes transients only under the plugin’s own unambiguous prefix, so unrelated transients belonging to other plugins are never deleted.

1.0.24

• New: Support menu item that opens the Avakode support dashboard.

1.0.21

• Hardened inline admin script output (field-mapping editors).
• WordPress.org compliance and code-quality improvements.

1.0.18

• Pro entitlement is now resolved by the Fillin Forge Pro add-on; the free plugin bundles no licensing SDK.
• The Google integration SDK now loads only when the Pro Google Sheets feature is active.
• readme metadata cleanup.

1.0.0

• Initial release.

Fillin Forge Pro (add-on)

1.3.6

• If you take bookings into Google Calendar, update Fillin Forge to 1.2.5 together with this version. With Fillin Forge 1.2.4 the mark and the e-mail still appear, but they describe the cause as a taken or unchecked time, and the e-mail’s link opens the first page of the list. Older versions show neither.
• Google Calendar: when the event cannot be created (the server or the network answered with an error, or the answer was not an event), or when every try is answered “please wait”, the submission is marked “Time not confirmed” and one e-mail goes to the form’s notification address (a form with its admin notification switched off gets the mark only). Before, the owner was not told.
• The “Time not confirmed” e-mail links to the submission’s own page of the list (with Fillin Forge 1.2.5).

1.3.5

• If you take bookings into Google Calendar, update Fillin Forge to 1.2.4 together with this version. With an older Fillin Forge the booking is still kept without an event, but the “Time not confirmed” mark is not shown on the Submissions screen and the e-mail is not sent.
• Google Calendar: a time that is already taken gets the same mark and e-mail. Before, the event was just skipped.

1.3.4

• Update Fillin Forge to 1.2.3 together with this version, if you take card payments. With an older Fillin Forge the payment is still checked and the saved submission is put right, but the notification e-mail has already gone with the old amount, and the submission shows no status words and no button.
• Stripe payments: a submission is now saved as paid only when Stripe says so. The payment is looked up with your own Stripe key, in the mode set on the payment field, and has to belong to this form and this field, be in the field’s currency, be for the amount the form comes to (a difference of one smallest unit of the currency is allowed) and not already belong to another submission. A payment made in Stripe’s test mode is never accepted on a site in live mode.
• Stripe payments: before the visitor is charged, the amount is checked on the server for what the server can repeat: a fixed price, or a formula made of numbers, + – * / and brackets over fields that hold a number or a choice. A formula it cannot repeat (one that uses another calculation field, for example) is held only to the total the browser reports, and the form editor tells you so when you save the form.
• Stripe payments: a payment that Stripe cannot confirm at that moment is saved as “Payment not confirmed” and asked about again by itself: after 2 minutes, 10 minutes, 1 hour, 6 hours and 24 hours, then at most every 6 hours for 30 days, up to 12 checks in all. The “Check payment in Stripe” button in the submission asks at once.
• Stripe payments: the Stripe webhook goes through the same checks, and a note about a charge whose form was never submitted no longer turns the real, paid submission into “Not paid”.
• Stripe payments: a form with two payment fields, one of them hidden by a condition, now pays with the field the visitor sees.
• Conversational forms: the page no longer scrolls down to the form when it loads, and the first question takes the cursor only when the form is on the screen.
• Conversational forms: an optional e-mail address or web address that is filled in is now checked on its own step, like a required one, instead of only after the last question.

1.3.3

• If you take payments in a currency without hundredths (JPY, KRW, VND, CLP, or another one Stripe counts in whole units: BIF, DJF, GNF, KMF, MGA, PYG, RWF, VUV, XAF, XOF, XPF) and got around the old mistake below by typing a price 100 times smaller, put the real price back as soon as this update is installed. From then on a price is charged exactly as typed, so the small price would be charged as the small price.
• Stripe payment field: in a currency without hundredths, a price of 1000 JPY was charged as 100,000 JPY, because every currency was counted in hundredths. The price shown, the check on the server, the payment itself and a total taken from a calculation field are now all counted in the currency’s own unit. USD and the other currencies with cents work as before. The smallest payment is 50 of the currency’s smallest unit (USD 0.50, JPY 50). Update Fillin Forge to 1.2.2 as well, so the submission screens show the amount in the same unit.
• Google Sheets: when conditional logic hid a field, every value after it moved one column to the left in the row sent to the spreadsheet. The row now follows the form’s fields in order and leaves an empty cell for a hidden one. Rows already in the spreadsheet are not changed.

1.3.2

• Deleting the last Forge plugin or add-on on a site now removes everything Forge stored on the site, on every site of a network (the statistics settings and the install ID, the shared job queue with its scheduled events, the settings and caches the Forge plugins share). While another Forge product stays, only this add-on’s own share goes.

1.3.0

• This release needs Fillin Forge 1.2.0 or newer. Fillin Forge 1.2.0 no longer loads any licence code (the wordpress.org package has none at all), so the add-on now brings the shared licence resolver along and answers the core’s question whether the connection behind Mailchimp, HubSpot and Google is made. Whichever of the two you update first waits for the other: the add-on stays off on an older Fillin Forge and says which version it needs.
• The notice about a Fillin Forge that is too old goes only to a user who can update plugins, and links to the downloads page of your Avakode account.
• Settings → Google (Sheets + Calendar): when the add-on does not run the Google features yet, it says so with the same “connect Fillin Forge to your Avakode license” notice as the Mailchimp and HubSpot cards, translated in all 15 shipped languages.

1.2.5

• Analytics: submissions sent with the form editor’s “Send a test submission” button are left out of the numbers in the forms list, the Analytics cards and table, and the conversion rate.
• The add-on now supplies the conversational layout’s stylesheet to the form builder’s preview, where the free plugin used to point at a copy it no longer ships (Fillin Forge 1.1.0 asks for it).
• Fixed: WordPress 6.7 and later reported “translation loading … triggered too early” because the add-on’s feature labels were translated while plugins were still loading; they are translated on init now.

1.2.4

• Deleting the add-on now runs a clean-up of its own – the add-on used to ship no uninstall script, so WordPress ran none. The licence key and site token it stored are removed, and so are the site’s Avakode account binding and the hourly statistics event when it is the last Forge plugin on the site.

1.2.3

• With a free core older than 1.0.39 the add-on stays off and says which core it needs, instead of stopping wp-admin with a fatal error: that core still declared the License screen the add-on has carried since 1.2.0.
• Updates: the update client starts before the add-on checks its free core, so an add-on that cannot run with the installed core can still be updated.
• Updates: “View details” falls back to the add-on’s own homepage and requirements when there is no newer release.

1.2.1

• The add-on carries the API client that the wordpress.org build of the free plugin leaves out.

1.2.0

• Licensing moved into the add-on: its licence class, the License screen and the upgrade prompt; the free core asks nothing about licences. The Stripe payment field and the integration connections moved with it.