What changed in QR-Verse: bulk import, saved codes, restored pages

This is the first of these. QR-Verse changes most weeks and until now the only way to find out was to notice. So here is what changed, in the order of how much you will feel it. Some of it is new, and a lot of it is us finding things that were quietly broken and fixing them.

New

Bulk import from a CSV file. Upload a spreadsheet and QR-Verse creates a dynamic code for every row, up to 2,000 at a time. You get a preview with row counts and a per-row error list before anything is saved, so a bad link on line 340 does not cost you the other 339. Find it in the toolbar on your QR codes page. Business plan.

It reads the spreadsheet you actually have. Comma or semicolon separated, quoted fields, Windows line endings, and the column headers people really use: url, target_url, link, destination, ziel. Semicolon exports out of German Excel work without touching them. There is a sample CSV in the import window if you would rather start from a known-good file.

Better

Save errors now speak your language. If content cannot be saved as a dynamic code, you get the reason in the language you are using, and the reason is specific: content too long, wrong type for this code, link type not allowed. Previously those arrived as raw English, in every language.

The link shown while you create now matches the real one. The create page showed qr-verse.com/r/ while every code we actually issue lives on go.qr-verse.com/r/. Same code, right address, in all seven languages.

Fixed

WiFi, vCard and plain text codes save properly again. This is the big one. A dynamic WiFi, vCard or text code was rejected before it was ever stored while the preview stayed downloadable, so the code appeared to work once and was then not in your account. It saves now, it survives editing, and the content page opens the way it should. If you made one of these between early and mid August and could not find it afterwards, that was this.

Feature pages in six languages load again. 35 of our 63 translated feature pages were returning a not-found error, across German, French, Italian, Spanish, Dutch and Portuguese. The pages existed and were fully written; the site sent you to the wrong address for them. Links between related features walked into the same wall. All of them open now, and we added a check that stops us shipping if we ever list a page that does not answer.

Canceled your plan? Your invoices are back. Canceling hid the billing history section, which was the only way into the invoice portal. Nothing was ever revoked on our side, the door was just no longer drawn. Former subscribers can reach past invoices again from account settings.

In the iPhone app, hitting the free plan limit says so. Creating a second dynamic code on the free plan showed "something went wrong, check your connection", which is a lie about a network. It now tells you that you have reached the free plan limit of one dynamic code and offers the upgrade, which is what was happening all along.

The create page cannot get stuck on a blank screen. It used to wait indefinitely on a sign-in check before drawing anything. That check now has a time limit, and a slow check no longer decides you are a first-time visitor and drops the welcome walkthrough on top of an account you have had for a year.

Behind the scenes

Four times a day, we use our own product. An automated run signs in with a real paid account, creates a QR code, scans it, checks that the scan was recorded, and checks that custom domains still resolve. It runs from outside our own servers, because a test that runs from inside them can pass while proving nothing. Roughly six hours is now the longest a core break can hide.

We can see browser errors again. Error reporting from the browser had been silently off since mid June, which meant a whole class of breakage was only visible if somebody wrote in about it. It is on. We would still rather hear from you, but we no longer depend on it.

Framework and dependency updates, with security patches. Routine, unglamorous, and the reason this section exists.

Anything in here that still does not behave, tell us. The fastest fixes on this list started as one person writing in.