Having the version history of views can be quite handy, we often leverage it to show different options of the same space:
However, it seems like this feature isn’t available when embedding the tour in an iframe? It looks like the entire top bar has been disabled, which is fine (I’d even prefer for the hyperlink back to the tour page to be removed from all share links completely), but not having the ability to view versions is a huge bummer. Can this be forced back somehow?
Also the floorplan mini map icon appears to not be available when the tour is embedded in a iframe?
Hi and sorry for the delayed reply!
The idea behind the embedding of Virtual Tours is to have a easy and simple experience, hence why this feature has not been included. However, I do realise the versioning is used also for showcasing design options, which we plan as a separate feature. Currently the versioning is indented as more of a iterative/collaborative feature.
I will have a discussion with the team to see what we can do until we develop the Design Options feature.
as for the floor plan and minimap - this feature should definitely work - you can check out the demo embedded tour here Chaos Cloud – Present, review, and render — easily perform every step on the cloud | Chaos
Hi Vasil, just wondering if there’s been any more news on either allowing versioning in the embedded tours or the Design Options feature?
Additionally, and somewhat related, I run into issues when new versions of panoramas are uploaded but the embedded iframe tours then won’t display them. When the virtual tour is first created and the embed link is generated, I can throw it into a simple html page and everything functions as expected. However, if I then log into my Chaos project and add new versions I can no longer see any of the 360 images in the embedded tour. The embed loads the initial/updated floorplan and the tour UI correctly, but the hotspot 360° panorama images show a blank screen.
Right-click > “Reload frame” in Firefox fixes it for that session (but this tool/option doesn’t always seem to be available in Chromium), and opening the link URL directly in a new tab works correctly after a manual refresh. I’ve tested on multiple browsers and devices and the behaviour seems consistent - the direct link tour functions as expected, the embedded tour won’t load the images.
I’m in over my head at this point, but on the off chance our AI overlords have correctly identified an issue and that it means something to someone, this is their commentary:
- In DevTools the embed attempts to create a streaming session fail with `POST https://cloud.chaos.com/collaboration/api/vista-scene/stream-session 401 (Unauthorized)`. There is a redirect chain (308 → 307 → 200) that sets cookies during those navigations.
- `GET /collaboration/n/<linkremoved>` → 308 → redirects to `/collaboration/folder/…` → 307 → `/collaboration/virtual-tour/…` → 200
- `set-cookie` headers are present in the redirect responses.
- `POST /collaboration/api/vista-scene/stream-session` returns `401` in the iframe context.
This looks like the embed requires a streaming session that depends on cookies/session state but those cookies or storage are not available/sent in the cross-site iframe context.
I won’t pretend to understand that, and apologies if it’s completely off the mark, just curious if the behaviour I described is known and/or if there’s an obvious fix?
Grey Block Hey! This sounds like a bug to me. I will refer the dev team and QA to look at it!
CC konstantin_lukashev martin_dimitrov
Any update on this? Even just confirmation that it’s a known issue and I don’t need to troubleshoot any more on my end.
@Grey_Block I just reminded the team about it. Will come back here as soon as they give me an answer.
@Grey_Block Good news! It has been fixed. Can you verify on your end.
Here is a screenshot of the issue that was resolved on our end
Nice. I haven’t tested extensively on multiple/new projects yet, but I revisited the link to the original project that prompted me to raise the issue and it appears like it’s working as expected. I will return if I encounter it on any other projects, otherwise thanks for the update/fix!
