I have an install of 6.1.6, I installed 1.2.1 of Optimus, and the package installed, but when you try to load any of the Optimus views in the settings section, it's broken, as the paths to all of the CSS and Javascript are broken.
The page is looking for assets with an extra "/index/" in the path. So instead of looking for /appplugins/optimus/scripts/xxx.js, it looks for /appplugins/optimus/index/scripts/xxx.js.
If I go into the views, and manually change all of the CSS/JS links to have a ../ in front of them, it works, as that gets rid of the extra "/index/".
The only special thing about my site that I can thunk of is that there's a default controller with a method of index that loads in some stuff for all front end requests (footer and header links etc) into a custom model (similar to the Hybrid Framework), but I wouldn't have thought that would affect stuff in the back end?
1.2.1 Not working in 6.1.6
Hiya,
I have an install of 6.1.6, I installed 1.2.1 of Optimus, and the package installed, but when you try to load any of the Optimus views in the settings section, it's broken, as the paths to all of the CSS and Javascript are broken.
The page is looking for assets with an extra "/index/" in the path. So instead of looking for /appplugins/optimus/scripts/xxx.js, it looks for /appplugins/optimus/index/scripts/xxx.js.
If I go into the views, and manually change all of the CSS/JS links to have a ../ in front of them, it works, as that gets rid of the extra "/index/".
The only special thing about my site that I can thunk of is that there's a default controller with a method of index that loads in some stuff for all front end requests (footer and header links etc) into a custom model (similar to the Hybrid Framework), but I wouldn't have thought that would affect stuff in the back end?
Has anyone else seen this?
Hey Tim,
I've not seen this nor have I been able to recreate it which is most strange.
I even removed the default bundling in the Hybrid framework and then I was able to install and use Optimus no problem.
Is it specific .js files that are 404ing or all of them, anything else you could suggest on how to recreate?
Cheers,
Jeavon
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.