Moreover, if I inspect the code in Chrome or Firefox, the routes are same (<link href="/grav-admin2/user/themes/future2/assets/css/main.css" rel=“stylesheet”>, for example)
@pmoreno , Are you working on a fresh install of the latest Grav v1.7.0-rc.20?
If so, did you add the |raw filter to the output of assets, like {{ assets.js('bottom') | raw }}?
Since Grav v1.7.0-rc.20 all output is auto-escaped for security reasons. When using |raw you are telling Twig the output is safe and should not be auto-escaped. This escaped code may look OK-ish in de dev console of the browser, but isn’t…
For example, with {% do assets.addJs(‘theme://assets/js/main.js’, {group:‘bottom’}) %}, the result in html is: <script src="/grav-admin2/user/themes/future2/assets/js/main.js">.
With <script src="{{theme_url}}/assets/js/main.js">, the result is same: <script src="/grav-admin2/user/themes/future2/assets/js/main.js)">.
However, with the second options all works fine and the first option doesn’t work.
I have not any idea what happens in this case.
@pmoreno, After looking at the repo, it appears to be an issue of the order in which javascripts were loaded using the Asset Manager. jQuery was being loaded after the other scripts needed it and errors showed up in the dev-console of the browser.
Updating the order in which javascripts are being added to the Asset Manager solved the issue.