Posts Tagged ‘dirty’
Howto workaround not secured password field alert from Google Chrome 56
Since Google Chrome build 56, password fields will trigger a warning if the page in not secured (read: HTTPS).
If your are a webmaster, you may even have received this kind of alert message from Google like this one :
Unsecure password collection will trigger warning display in Chrome 56 for “your site”
The password field is a specific HTML field type, that will automatically mask the typed in characters, like the one below (yellow background) :
password field hides typed characters
To avoid this warning, the best option is of course to move that page to HTTPS. However, if you cannot migrate the page to HTTPS yet because it is too expensive, or requires too much code changes, or you simply don’t want to implement HTTPS because it’s not worth the effort (nothing important behind this password field), here are 2 tricks to avoid the chrome 56 password warning message.
Avoiding the Chrome 56 password warning Read the rest of this entry »
Dirty hack: force primary category for wordpress post permalink
I’m not especially proud of this hack. However, I was getting crazy by how the category used for a post permalink is choosen. And I could not figure out a clean way to control which is the primary permalink (I hope it’s not part of Wordpress 3.0…).
You may need to set the primary category for permalink in two situations:
- First, you want some consistency among your posts, having them in the same primary category.
- Second, it’s never fun when, by adding an additional category to an existing post, it changes the post permalink!