Cause for older API version to suddenly stop working, generating errors?

[TracySchloss]

I have an older site that was based on the 3.2 version of the API library.  It's been working fine for the past year or so.  Today I got an email that the site is not working.  I've made no changes on this end.  I am getting errors that one of the buttons that's within a border container doesn't have a region set.  When I commented that out, just to see what would happen, the next component generated the same type of error.

Are the older locations still available and is it not OK to assume these will still be in place for longer than a year?  This site isn't that old.

This is an example of the path I had in my code.  It was valid at the time I wrote it.
http://serverapi.arcgisonline.com/jsapi/arcgis/3.2/js/esri/css/esri.css"

The URL to the site is http://http://gis.dhss.mo.gov/Website/VFC/provider.html

[JeffPace]

That link is still valid.

If the code didn't change, the browser must have.

[TracySchloss]

I can believe that, they are constantly pushing patches and updates with no notice.  That isn't going to be satisfactory answer for the user, though.  It just so happens that I've been working on updating it, since it's not styled to be mobile-friendly, but I'm not ready to push it out today!

[JeffPace]

Yes, rapid development cycle is not always so friendly on the developer.

Can you test it in an older browser to confirm?

I tried the link and it isnt working for me at all (chrome)

[JeffPace]

looking at this a little more, this is definitely a dojo/css issue

I have the 3.2 api hosted locally. If you want you can try pointing your app to it to make sure something didnt change on ESRI's end

www.mymanatee.org/arcgis_js_api/library/3.2/arcgis/?v=3.2

[TracySchloss]

The user says it was working yesterday, which makes me think it is internal to us.  But my other JS sites are all working.  Of course this is just about the oldest one, so there could still be an issue with the JS library.

[JeffPace]

If you are using a webcache you might try clearing it.

Getting the error in multiple browsers, when its a css issue, makes me think either something is getting block/corrupt, or something changed on the source side.