# Online Sandcastle for previous versions?

**URL:** <https://community.cesium.com/t/online-sandcastle-for-previous-versions/11374>\
**Category:** CesiumJS\
**Created:** [October 29, 2020, 1:50pm UTC](https://community.cesium.com/t/online-sandcastle-for-previous-versions/11374 "2020-10-29T13:50:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_B](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/james_b/32/2424_2.png) [@James\_B](https://community.cesium.com/u/James_B)\
**Post date:** [October 29, 2020, 1:50pm UTC](https://community.cesium.com/t/online-sandcastle-for-previous-versions/11374/1 "2020-10-29T13:50:54Z")

</div>

I need to track down what I think might be a regression, and in the past it’s been really helpful to be able to just paste a code block into various versions of Sandcastle to find the version where things broke. I’m pretty sure that I used to be able to do this but I’m having trouble finding the right URL scheme in my notes.

I found [this very old post](https://community.cesium.com/t/using-older-versions-of-cesium/2803) saying that there should be a Sandcastle link from the Downloads page, which I think is [here](https://cesium.com/downloads/cesiumjs/) now, but that’s no longer the case. It also used to be possible to get to a “front page” for each release, e.g. [here](https://cesium.com/downloads/cesiumjs/releases/1.60/index.html) but the Sandcastle links on those pages are broken now too.

Is there a current way to use old Cesium versions live online? I want to file a bug report but I don’t have time to download a dozen old versions and build them myself…

---

<div class="post-metadata">

**Author:** ![omar](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/omar/32/1999_2.png) [@omar](https://community.cesium.com/u/omar)\
**Post date:** [November 1, 2020, 7:15pm UTC](https://community.cesium.com/t/online-sandcastle-for-previous-versions/11374/2 "2020-11-01T19:15:53Z")

</div>

@James_B this is indeed no longer supported. I have found the Glitch template referenced in this tutorial to be a useful workflow for this: [https://cesium.com/docs/tutorials/build-a-flight-tracker/#step-1-set-up-your-cesium-app](https://cesium.com/docs/tutorials/build-a-flight-tracker/#step-1-set-up-your-cesium-app)

Since all you have to do is change the version number linked from the CDN to quickly try older versions (of course you can do this in any environment). Here’s a direct link to the cesium template that can be forked (or “remixed”): [https://glitch.com/edit/#!/cesium-template](https://glitch.com/edit/#!/cesium-template)

---

<div class="post-metadata">

**Author:** ![James\_B](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/james_b/32/2424_2.png) [@James\_B](https://community.cesium.com/u/James_B)\
**Post date:** [November 2, 2020, 11:47am UTC](https://community.cesium.com/t/online-sandcastle-for-previous-versions/11374/3 "2020-11-02T11:47:05Z")

</div>

Thanks Omar. It took a while to spin up, but I was able to test my code and determine that this isn’t a regression, just a misunderstanding on my part. It would be cool if this template were added to the bug-report template on GH, as a Sandcastle alternative – i.e., “Include a link to a reproduction of the issue using {Sandcastle}, or remix {this Glitch template}.”, etc.

(In case you’re curious, I was using an imagery provider from the BaselayerPicker widget to manually request an image with `requestImage`, thinking that would cause the `errorEvent` to raise, but it does not. I thought it had done so in the past because I was also selecting that provider as the active baselayer, which caused the Viewer to request imagery from it, which does trigger `errorEvent` when it fails. It’s clear to me now, although a few words in the docs about exactly when `errorEvent` is supposed to fire sure wouldn’t hurt 😃 )