-
Notifications
You must be signed in to change notification settings - Fork 19
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
replace jquery.pstrength #58
Comments
Upgrading to asset pipeline could be a big change and break those deploymnts who are already using it with resources. I am thinking wht can we do. Seriously i personally dont like asset pipeline, there are some limitations, like css / js cant be specified in same bundle, bundling cant be disabled in production etc, but if resources is not going to be maintained, we will have to replace |
by putting the right manifests in the assets directory it is possible to support both as assets-pipeline will look in the web-app folder as well as the assets folder. it took me two days, but that included a whole bunch of other stuff. in my app i use: my application.js file is: //= require modernizr/modernizr-2.7.1.js i use bootswatch to provide my bootstrap theme. my application.css file is: *= require bootswatch/${grails.util.Holders.getGrailsApplication().config.theme}/theme.less |
i'm updating to asset-pipeline because resources is no longer supported/maintained.
i was having issues when the javascript was minified. so i looked around on the internet to see if other people had the same problem.
during my travels i discovered that the jquery.pstrength component was released around 2006 and has not been changed/supported/upgraded since then. there also does not appear to be anyone claiming ownership (that i could see).
so you might consider replacing it with one of the other password strength plugins.
i am using jquery-pwstrength-bootstrap which was a trivial change.
The text was updated successfully, but these errors were encountered: