Setup question

Hi,

I'm using Canvas in an asp.net core project.
functions.js is loaded with:

``

My homepage is www.mysite.com/en

Your scripts and all subscripts are loading fine.
However, when I navigate to another page like www.mysite.com/en/projects I see that functions.js try to load subscripts incorrectly. When checking in console, I see for instance that it tries to load /en/js/fn.logo.js instead of /js/fn.logo.js. This is quite surprising since I explicitely requested functions.js to be loaded from the root.

How do I solve this?
Thanks

Nicolas

After checking the functions.js file, I am wondering why you load plugins relative to the url path...
To my mind, it would be better to either load them from a base path like /js or by smartly loading them from the same path than functions.js was loaded.

As a workaround, while waiting for your solution, I modified functions.js loadJS function to prepend '/' before the path.

Also, why is there no unminified functions.js. This would allow for better investigation and your customers could help you find bugs or debug the code easily.

Thanks

Nicolas

Thank you.
Indeed, some files can now load correctly but not all of them. For instance, on my page, jquery.js and the parallax module are not loaded correctly. Eager to download your fixes on this. Thanks for the fast reactivity.

Nicolas

Unfortunately, with the latest version of this WE, jquery and other plugins.* files are not loaded correctly with an absolute path. modules.* files are loaded correctly.

I have no live web site yet.
So here is what I did: I unminified functions.js and put a breakpoint in LoadJs.
As you can see on the screenshot, the function tries to load "js/jquery.js". Note the absence of leading slash. So it still tried to load the script relatively to the current url.

In short, after seeing your code, it can't work for you, me and other users if the url has multiple segments.

Note also that if I set jsFolder in functions.js equal to '/js/' instead of 'js/' it fixes my issue.

On a side note, I wonder how js loading could work before I reported this bug. if I load a page with url /user/details/123, it does not make sense to request /user/details/js/xxxxxxxx.js. Javascript files always have to be loaded from the root, not relatively to the current url path. I am puzzled with that.

Hi,

You don't need a live server from me because you can replicate it locally on your dev machine.
In your template distribution, here is what I did this morning to reproduce the issue:

Alongside all the html files, js and css folders, create a new "test" folder. Copy index-classic.html in the test folder.
Modify the html file so that it links to the needed files as absolute paths instead of relative paths (especially replace js/functions.js by /js/functions.js - css and images paths are not necessary to replicate the issue).
Using Visual Studio code and your live server extension of your choice (I'm using ritwickdey.LiveServer), or your own local server, start the server (from the "Canvas7 Files" folder) and navigate to https://localhost:port/test/index-classic.html.
In the Network tab of the browser debug panel, check that jquery and other plugins are not loaded correctly since it tries to load them from the test folder instead of the root.

Note that if there is an issue with js files, there may be an issue with css files when referenced as absolute paths too... But I don't know in which circumstances it could happen. I understand that your code loads plugins when needed. Do you also load CSS dynamically sometimes?

Hi,

Some news about this please?
I saw a new update mentioning loading JS in different manners, but there is nothing in the doc about it.
Thanks

Nicolas

Thank you. It seems to work, but:

1. It's a pity you could not make it as a simple /js/functions.js instead of explicitely loading jquery and then scripts instead.

2. It's a pity that your doc does not even mention this notion of absolute path. People with the same issue, and I guess they are numerous since this is not everybody that simply loads all web pages with a single level from the root, won't know that they have to replace functions by jquery+scripts.