Friendlier sign-in errors, a keyboard-friendly reset window, and one Portail address
A handful of small fixes around logging in. First, if you type www.portail.cc, you now land on portail.cc, with the page and any link details kept. The www address used to load the full site on its own, but our sign-in provider only trusts portail.cc, so Google sign-in failed there and password reset links lost their way back. Now there is one address and everything on it works. Second, the login form, the sign-up page and the email code check no longer show raw technical errors. Messages that started with the word Firebase and ended in a code in brackets are gone. If you try too many times in a row, you see a plain note asking you to wait a few minutes. If your connection drops, you are told to check it and try again. If an account has been disabled, you are told so and pointed to support. Anything we haven't written a specific message for falls back to a simple "Something went wrong, please try again" instead of a code. All of this is in English and Russian. Third, the "Forgot password?" window now behaves properly with a keyboard and a screen reader. It opens with the cursor already in the email field, Tab and Shift+Tab stay inside the window instead of wandering off to the page behind it, Escape closes it, and when it closes your focus goes back to the "Forgot password?" link. Screen readers announce it as a dialog with its title. Nothing about your account or plan changes.
638 words
www.portail.cc now forwards to portail.cc, so Google sign-in and reset links work from either address.
Login, sign-up and reset errors are plain sentences in English and Russian, never raw codes.
The password reset window keeps keyboard focus inside it and returns it when closed.
Portail v2.6.18 shipped on 2026-10-10 as a patch release focused on friendlier sign-in errors, a keyboard-friendly reset window, and one portail address. A handful of small fixes around logging in. First, if you type www.portail.cc, you now land on portail.cc, with the page and any link details kept. The www address used to load the full site on its own, but our sign-in provider only trusts portail.cc, so Google sign-in failed there and password reset links lost their way back. Now there is one address and everything on it works. Second, the login form, the sign-up page and the email code check no longer show raw technical errors. Messages that started with the word Firebase and ended in a code in brackets are gone. If you try too many times in a row, you see a plain note asking you to wait a few minutes. If your connection drops, you are told to check it and try again. If an account has been disabled, you are told so and pointed to support. Anything we haven't written a specific message for falls back to a simple "Something went wrong, please try again" instead of a code. All of this is in English and Russian. Third, the "Forgot password?" window now behaves properly with a keyboard and a screen reader. It opens with the cursor already in the email field, Tab and Shift+Tab stay inside the window instead of wandering off to the page behind it, Escape closes it, and when it closes your focus goes back to the "Forgot password?" link. Screen readers announce it as a dialog with its title. Nothing about your account or plan changes. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: www.portail.cc now forwards to portail.cc, so google sign-in and reset links work from either address, login, sign-up and reset errors are plain sentences in english and russian, never raw codes, and the password reset window keeps keyboard focus inside it and returns it when closed. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.6.18 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.