When the saved value isn’t what you expected
Updated November 9, 2026
| What you see | Why, and what to do |
|---|---|
| What the visitor typed was replaced. | The field is set to Always fill it, so the rules decide the saved value. Tick Visitors can’t change this field, use a Hidden field, or switch to Fill it only if it’s empty. |
| A {today} date is a day off. | The page uses the visitor’s date; the saved entry uses your site’s time zone. Check Settings → General → Timezone. |
| Old entries didn’t change after I changed the rules. | Rules apply when forms are submitted and when entries are edited. Saved entries keep their values until one of a field’s sources is edited. |
| An edited entry didn’t update. | A field is worked out again only when a field it depends on changed in that edit. If another plugin made the change, it may change fields one at a time, which KodaFill doesn’t see (developers can call kfill_entry_rerun()). |
| A field was cleared when an entry was edited. | With Always fill it, a field is cleared when no rule matches and If no rule matches is empty. Add an If no rule matches value, or a rule for that case. |
| A Drop Down or Radio Buttons field wasn’t set. | The rule’s value isn’t one of the field’s current choices; the editor shows (not a choice). Pick a current choice. |
| Values keep changing or don’t settle. | Fields may fill each other in a loop. The KodaFill tab warns about this: see Rule order, default and loops. |
| A Number field and KodaFill disagree. | Don’t use KodaFill on a field with Enable Calculation turned on. |
Was this page helpful?
Thanks for letting us know.
