Skip to content
CardCloser
Fix a problem

My changes did not save

The usual cause is an unsaved section. Here is how to check, and what else it could be.

Short answer

Most often the section was never saved. CardCloser saves per section, and leaving a tab with unsaved work shows a dialog offering Save and Continue, Discard Changes or Stay Here. If you chose Discard, the edits are gone.

Start with the most likely cause, which is right about eight times out of ten.

First: was the section saved?

CardCloser saves per section. Editing the About panel and then opening Brand does not save About — the Portal stops you and asks.

  1. Go back to the panel you edited.
  2. Look at whether your text is there. If it is, save now.
  3. If it is not, the edits were discarded and will need re-entering.

The dialog that appears when you leave a tab is the one to read. It offers Save and Continue, Discard Changes and Stay Here. Discard Changes does exactly that.

Then: check the other causes

You edited in one browser tab while another tab had the Portal open.
Close the other tab and work in one. Two tabs holding two drafts of the same account will fight, and the last save wins.
Your session expired while the page stayed open.
Reload the Portal. If you are asked to sign in, sign in and re-enter the change — an expired session cannot save.
Your connection dropped mid-save.
CardCloser tells you when a save does not complete. Reload, check what is actually stored, and save again.
You saved, but you are looking at a cached public page.
The Portal is the truth. Reload the public page — it refreshes within the hour, or immediately if you republish.
A required field is invalid.
A field with an error blocks its section from saving. Scroll the panel for a red message.

If it happened more than once

A save that silently fails is a serious defect, and CardCloser is built so that a failed save says so rather than looking successful. If you are losing work repeatedly, that is worth telling us about immediately.

  1. Note which panel it was, and roughly what you did.
  2. Note whether you saw any message.
  3. Use Report a problem and include both.

Attach a screenshot if you have one. Bug reports with a screenshot are the ones that get diagnosed fastest.

How saving actually works

Each section holds its own draft while you edit. Saving sends that section, and the server's answer is what the Portal then shows — the browser does not assume it worked.

If two saves overlap, the older answer is ignored rather than allowed to overwrite the newer one. This is why a slow connection produces a delay rather than a mystery.

Was this helpful?

Still need help?

In Fix a problem · Last reviewed July 31, 2026