Release Kaleta 3.31.1 · phprs-cms/kaletacms

Kaleta 3.31.1 is a fixes release after 3.31. No database change.

Pipeline

A stage keeps its kind while deals are in it. Changing a stage from open to won or lost (or back) is refused while deals in it do not fit the new kind; the editor says how many. A stage whose deals all fit already – for example after a change made in 3.31 – can still be switched. Labels and order still change.
People without Pipeline access see a deal on a customer's timeline only as "A deal" – with its time and number, but no title, stage, person or link. The same holds for Claude's get_contact.
Claude's save_deal with an enquiry now uses the stage you give (an open stage). Without it, the deal starts in the first open stage as before.

Certificate reminders come 14 and 7 days before the date. Domain registrations keep 30 and 7. Both lists are in Fleet → Calendar; a reminder already sent within a threshold is not sent again.
Today shows an update rollout held back by the pilot sites for more than 3 days – one item per release, linking to the Rollout tab, which now says how to release it.

An encrypted copy uploaded back for a restore no longer counts as a backup made on this server. It used to make the last backup look fresh and could delay the automatic backup. The Backups tab marks it as an uploaded copy.
A restore never loses the file it restores. Local backups and uploaded copies rotate separately (the newest 10 of each), and the rotation waits until the restore has finished.
A failed off-site copy is now recorded as a backup failure, so alerts, System status and the Fleet console see it. The text never includes the password, user name, e-mail addresses or paths. A failing media copy is recorded once when it starts failing, not every hour.

System status points the automatic suspension to Settings → Security (where it moved in 3.23).
Customers and Pipeline link to their own articles in the guide.
Czech labels for the customer CSV import and export.

Update from the admin as usual. Nothing to do afterwards.
A Fleet console that saved its own reminder days keeps them for domain registrations; certificates use 14 and 7 until you change them.