|
|
|
Since it is fairly easy to work around this problem, I'm dropping it down to minor.
Various changes to the plugin have made this issue redundant, I believe. Re-open if it's still a problem for you.
Hi,
I had this same problem, I just installed the plugin jsecurity, now on version 0.2 at grails 1.0.2 and the problem appeared again. I made a controller with an create action to add users to my website and when the page was load, the page try to look for the js libraries inside the jsecurity folders, as describe bellow: <script type="text/javascript" src="/multilinguas//plugins/jsecurity-0.2/js/jquery-1.2.3.cust.js"></script> and at my create.gsp I defined on this way: <g:javascript library="jquery-1.2.3.cust" /> Unfortunately, to avoid this I defined base_href equals to the name of my aplication and I had to call directly the js using the tag <script></script>. The other pages that the controller does not use the Jsecurity, loads normally, without any problems to find the js library. So I think that a part of this bug remains! Thanks Rogério Carraqueira I've also just come across this issue with a fres 1.0.3 app and the lastest jsecuroity pluhin - installed the plugin, ran grails quick-start (which created grails-app/views/auth/login.gsp) and my webtests are failing (after clicking sign in on the login page) due to invalid JS library links on the pages using the main layout.
cheers Lee I'm sorry, I am confused by this issue. I too encountered a similar error when using Canoo Webtest and Jsecurity. What is the "fairly easy" workaround to which Peter Ledbrook alludes?
In my grails-app/views/layout/main.gsp file, I replaced the line <g:javascript library="application"/> with <script type="text/javascript" src="/codegrader/js/application.js"></script> since the latter is how the former is dynamically rendered at run time (unless the bug under discussion incorrectly renders it as mentioned in the previous comments). However, I don't entirely understand the former line (it was placed in main.gsp by default by Grails), and I am afraid that some future change in Grails (for instance, moving the location application.js) will break this. So what is the correct workaround for this bug? Thank you in advance, |
||||||||||||||||||||||||||||||||||||||||||
In the meantime, I would simply copy login.gsp from the plugin to your grails-app/views/auth directory. This also enables you to customise the look of it.