On Thu, Jan 12, 2012 at 11:00 PM, Daniel Friesen
li...@nadir-seen-fire.comwrote:
On Wed, 11 Jan 2012 14:09:23 -0800, Chad innocentkil...@gmail.com wrote:
On Wed, Jan 11, 2012 at 4:43 PM, Happy Melon
happy.melon.w...@gmail.com wrote:
Yes, no user-editable scripts are run on pages where
On 12 January 2012 02:47, Daniel Barrett d...@vistaprint.com wrote:
On 11 January 2012 21:51, Daniel Barrett d...@vistaprint.com wrote:
* Remove any trailing @companyname.com from the username. Users in
our company are accustomed to logging in this way on
their Windows boxes, and we'd get
Of course, if the login form code wasn't such a swamp, there'd be a hook
you could use to preprocess the usernames server-side... :-(
The getCanonicalName function in the auth plugins will do this. I was
actually thinking of adding a hook to LdapAuthentication in that
function to let users
In 1.18.0, the page Special:UserLogin no longer runs the JavaScript in
MediaWiki:common.js. Is this an intentional change from 1.17, and if so, is
there a workaround to make custom JS run on the login page?
(I tested this by putting alert('foo') in MediaWiki:common.js. The alert
appears on
On 11 January 2012 21:27, Daniel Barrett d...@vistaprint.com wrote:
In 1.18.0, the page Special:UserLogin no longer runs the JavaScript in
MediaWiki:common.js. Is this an intentional change from 1.17, and if so,
is there a workaround to make custom JS run on the login page?
(I tested this
You could probably hack around it by using one of the many hooks in the
page rendering stack to add the JS module on the pages where it's not
already there, but before doing so it's worth thinking about the reason why
it was removed in the first place.
Thank you HM. In our case, we are using a
On Wed, Jan 11, 2012 at 4:43 PM, Happy Melon happy.melon.w...@gmail.com wrote:
Yes, no user-editable scripts are run on pages where password forms reside,
because it is trivially easy for users to use them to introduce
password-sniffing JS attacks, either deliberately or inadvertantly. Or
On Wed, Jan 11, 2012 at 3:51 PM, Daniel Barrett d...@vistaprint.com wrote:
You could probably hack around it by using one of the many hooks in the
page rendering stack to add the JS module on the pages where it's not
already there, but before doing so it's worth thinking about the reason why
it
On 11 January 2012 21:51, Daniel Barrett d...@vistaprint.com wrote:
* Remove any trailing @companyname.com from the username. Users in our
company are accustomed to logging in this way on their Windows boxes, and
we'd get several support calls per week from people who can't log into the
On Wed, Jan 11, 2012 at 6:18 PM, David Gerard dger...@gmail.com wrote:
The way we do it on our Mantis bugtracker is to use the LDAP server
for all logins. Something like that for MediaWiki would do the job
too. One password!
Ryan's been maintaining such a feature for years :)
On 11 January 2012 21:51, Daniel Barrett d...@vistaprint.com wrote:
* Remove any trailing @companyname.com from the username. Users in our
company are accustomed to logging in this way on
their Windows boxes, and we'd get several support calls per week from people
who can't log into the wiki
11 matches
Mail list logo
