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

Issue with LoadQueue basePath #254

Open
dill0wn opened this issue Feb 26, 2018 · 0 comments
Open

Issue with LoadQueue basePath #254

dill0wn opened this issue Feb 26, 2018 · 0 comments

Comments

@dill0wn
Copy link

dill0wn commented Feb 26, 2018

There is a nearly identical issue that's two years old up here, but I'm having the exact same issue with the 1.0.1 release here: https://github.com/CreateJS/CreateJS/releases/tag/v1.0.1

When using the basePath property in conjunction with a manifestloader, it only seems to apply to the manifest, and not the manifests contents.

I have folder structure similar to the following:

http://localhost/games/mygame.html
http://localhost/cdn/mygame/assets/manifest.json
http://localhost/cdn/mygame/assets/data/somedata.json

So i do

var loader = new createjs.LoadQueue(false, "http://localhost/cdn/mygame/");
loader.loadManifest(
    { id: 'myManifest', src: 'assets/manifest.json', type: 'manifest' }, 
    true 
    //, "http://localhost/cdn/mygame/" // I've tried both places
);

and the manifest looks like:

{
    "manifest": [{
        "id": "someData",
        "src": "assets/data/somedata.json",
        "type": "json"
    }]
}

It loads the manifest, but then fails to load any of the contents, getting 404 instead. The url attempted was http://localhost/games/assets/data/somedata.json

Is there something obvious I'm doing wrong?

Unfortunately, the hosting situation is outside of my control, so I do not think I can change the path structure.

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

No branches or pull requests

1 participant