The first half of August was mostly about things that were half-finished: tours that knew which apartment they belonged to but never said so, a delete that did not delete, and error messages written for us rather than for you.
Unit details from inside a tour
A 360 scene that belongs to an apartment can now show a details button, so a visitor walking through a flat can open its specification without leaving the tour and finding it in the list.
It works in the viewer's own tour overlay and in standalone tour embeds on your website, where the click is passed out to the page the same way the viewer's details button already was.
Deleting a unit for good
Deleting a unit has always hidden it and kept the row, along with everything referencing it: its activity, its clickable areas on the navigator, its analytics, and the inquiries that mentioned it. Several of you asked how to actually remove a unit and could not find it, because it was not there.
There is now a second, explicit option that removes a unit and its traces. Before you confirm, it tells you what will be destroyed, including how many leads referenced only that unit, and it asks you to type the unit's name. Inquiries that mentioned other units as well are kept, with the deleted unit scrubbed from them.
The ordinary delete is unchanged. Both are now reachable from the units list and the unit page, rather than only from inside the project editor.
The dashboard is fully translated
Every language now has the whole dashboard. The gaps were mostly in the strings you hit most often: the confirmation toasts after saving something, and the validation messages on forms, which were English no matter which language you had selected because they were written into the code rather than the translations.
Login errors that say what to do
A customer reported that login was broken. It was not: their account had been created with Google and had no password, so the email and password form could never work for them. What they saw was a raw error code from our authentication provider, which told them nothing.
Failed logins now explain themselves. The most common case, an account that signs in with Google, says so and points at the Google button. A browser blocking site data, which also broke sign-in silently, is detected and explained. And anything we cannot classify is reported to us rather than only to the person trying to log in.
Feedback boards render at the right size
Uploading an image to a feedback board could leave it blank for up to ten minutes, or render it at half size in a box the wrong shape. The board read its dimensions from a record filled in by a job that ran every ten minutes, and never corrected a wrong value once written. It now measures the image itself, so a board is correct the moment it is uploaded and stays correct.
Smaller things
- Links to a specific frame and rotation in the viewer work again, and a project can hide the left and right arrows if the labelled view buttons are the only way you want people to move between images.
- Embed parameters are applied correctly when a viewer is loaded inside another page, rather than being dropped on the first render.
