Edit a configuration and how versions work

You can change a configuration at any time: add a column, map a new field, fix a wrong category column. Content Uploader is built so that changing the mapping never rewrites what already happened.

Open the editor#

• On the Dashboard, select the settings icon on the configuration's card (its label is Edit …).
• On the page of a file, select Edit configuration. This opens the editor for that file: the button at the end then reads Save and check file name (with a tick box, Check … with this configuration after saving), and saving checks that file again with the new mapping.

The header says which version you are looking at: Version 3, saved 12 Oct 2026, 21:07. Saving a changed mapping creates a new version; files that were already checked keep the version they were checked with.

What a version is#

Each time you save a changed mapping (destination, record ID, fields, taxonomies, images, custom fields, or whether files have a header row), a new, unchangeable version is stored. Versions are numbered from 1.

• A run (one uploaded file) is checked with one version and keeps it. The page footer says which: Checked with configuration version 2 (saved 12 Oct 2026, 20:51). The review you read is always the review of that version.
• Saving only the name, the publishing option or the emails does not create a version.
• Saving without changing anything does nothing.
• There is no button to restore an earlier version. To go back, open the editor and set the mapping back; that saves a new version with the old values.

Apply a new version to a file that is waiting#

You uploaded a file, saw that a field was mapped wrongly, fixed it and saved. The waiting file still carries the old version. On its page:

• Check again with version N (in the footer) checks the same file again with the newest version. Before it is published, a file may be checked again as often as you like.
• If you came through Edit configuration from that file and saved, the file is checked again for you.

A file that has been published cannot be checked again against a different version: upload it again if you want its rows compared with the new mapping. What was last published stays the baseline for the comparison.

What a changed mapping does to items already published#

Nothing happens on your site when you save. The next file is compared with what was last published, using the new mapping:

• If the change affects a field (you now map an excerpt, or a different category column), the items it touches show up as updated in the review, with the old and the new value, before anything is sent.
• If the change affects how rows are recognised (you choose another record ID column, or switch between an ID column and no ID), the rows may look new. The old items stay on your site. Check the review; if the counts are not what you expected, do not publish (choose the record ID).
• Moving a configuration to another site does not move its history: items are new on the new site, and the first file asks you to confirm (This is the first file published with this configuration.).

The first file published with any new version asks you to tick I reviewed the changes above, because the new mapping has not been used to publish yet.

Two people editing#

If someone else saves the configuration while you have the editor open, a notice appears: … saved version 4 of this configuration at 14:02 while you were editing. Your changes are still here and have not been saved. Your edits are kept in the page (and survive an accidental reload of the tab). You can Open it in a new tab to compare, Discard my changes and load it, or, when you save, answer Someone else saved this configuration while you were editing… with Save mine anyway.

If the site's fields change while the editor is open (for example you installed a plugin and refreshed the site's fields), a notice says so; reload to map the new fields. Every notice at the top of the editor, with its buttons, is listed in a notice appears at the top of the page.

Sample file read again#

If you upload a different sample while editing, the editor keeps your mapping and offers Use the new columns once the file is read.

My file has no header row (or Row 1 holds column names), under Sample file, reads the sample again the other way and opens the editor with the columns it then has. Your mapping is kept, but it names the old columns, so point the fields at the new ones. Saving makes a new version even if nothing else changed, because every later file is read the new way (files without a header row).