Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CESIUM_BASE_URL ignored in 1.42 #6225

Closed
mreilaender opened this issue Feb 15, 2018 · 6 comments
Closed

CESIUM_BASE_URL ignored in 1.42 #6225

mreilaender opened this issue Feb 15, 2018 · 6 comments

Comments

@mreilaender
Copy link

mreilaender commented Feb 15, 2018

Setting the CESIUM_BASE_URL like below breaks Cesium (v1.42). It seems to be completely ignored as the console errors show (see picture).

In v1.41 everything works correctly.

window['CESIUM_BASE_URL'] = './path/to/somewhere';

image

@hpinkos
Copy link
Contributor

hpinkos commented Feb 15, 2018

Thanks for reporting this @mreilaender!

@tfili another one related to your Resource changes?

@tfili
Copy link
Contributor

tfili commented Feb 18, 2018

If you change it to window['CESIUM_BASE_URL'] = './path/to/somewhere/'; (with the trailing slash) it should work in 1.42. I fix this in #6231, so it should make it in the next release.

@mreilaender
Copy link
Author

mreilaender commented Feb 20, 2018

Thank you @tfili for the quick fix. Unfortunately, adding the trailing slash doesn't work ... Still the same errors. I'm simply gonna wait for the next release.

@tfili
Copy link
Contributor

tfili commented Feb 23, 2018

I was able to reproduce the problem without the slash and adding the slash fixes it. All my fix does is guarantee the slash is there.

If that doesn't fix the problem, you may want to try master to make sure it actually addresses your issue.

@mark-lassche
Copy link

For what it's worth we're running into the same issue. Adding trailing slash did not fix the problem, downgrading to 1.43 did resolve the issue for us.

@hpinkos
Copy link
Contributor

hpinkos commented Apr 5, 2018

@mark-lassche there's a new issue for this open here: #6411
We should have it fixed again for the 1.45 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants