Extension talk:AjaxLogin

It is not working. Sachein 09:09, 24 May 2009 (UTC)

More information would be usefull. It's working for me. Have you set $wgUseAjax = true; in your localsettings? --Danwe 03:18, 2 December 2009 (UTC)

It is not working for me too..I have Ajax enabled, since it is used by Category Tree Extension. And Special:Version does show that it is installed. Instead of using Ajax, it just shows the login fields twice: once for the normal login, another for the ajax login. I have the following extension: UNC Path, Widget Namespace, Renameuser, Category Tree Extension, FCKeditor, AjaxLogin. Might there be some conflict? Any help would be appreciated.

You can check for conflicts by disabling those other extensions and then testing the login again. Very simple. --Danwe 14:25, 2 January 2010 (UTC)

Prettier login window

The extension is great although the login window doesn't look this nice. Perhaps this could still be a point to improve it in detail --Danwe 03:31, 2 December 2009 (UTC)

Have it set as in the Read Me

Hi, I have been trying to get this to work and it just keeps going to the regular login page. I even tried using monobook to rule out my theme and it still does the regular action of going to the special login/register page. When I go to the example page of the Usability Initiative it doesn't have an ajax login box either. Is this extension still being used and functional? Thanks, --Demetelski 13:10, 11 May 2010 (UTC)

More details please. MW version? You have to set $wgUseAjax = true; and make sure the extension is activated. Is it listed in the Special:Version page of your wiki? --Danwe 17:02, 11 May 2010 (UTC)

Hi thanks. I found it through web developer error console. I was missing the call to jquery.js in the theme.--Demetelski 12:40, 18 May 2010 (UTC)

I know this is a year later, though I am having troubles getting it to work, and this might be the solution. Could someone elaborate on what this solution is and how to do it? Thanks. --Critch646 23:22, 23 May 2011 (UTC)

Login links

Hi, I have the extension working for when the user clicks on the login link in the upper left hand corner. I was wondering if this extension could be set to popup whenever a link to the login URL is clicked regardless of where it may appear? --Demetelski 12:38, 18 May 2010 (UTC)

Error messages on AjaxLogin.php

When I test the extension I obtainb a blank page with this text :
Warning: Missing argument 2 for GetAjaxLoginForm() in /my_site/mediawiki/extensions/AjaxLogin/AjaxLogin.php on line 97 Fatal error: Call to a member function getTitle() on a non-object in /my_site/mediawiki/extensions/AjaxLogin/AjaxLogin.php on line 102

same here. I get:

Fatal error: Call to undefined method OutputPage::getTitle() in /Applications/XAMPP/xamppfiles/htdocs/w/extensions/AjaxLogin/AjaxLogin.php on line 58

MW 1.17 Error

I keep getting this error as part of my PHP Stack trace in Apache error logs. I don't have enough experience or SVN access for extensions. Untoldpromise 01:52, 11 November 2010 (UTC)

PHP Notice: Undefined index: skin in /home/xxxxxxxx/xxxxxxxx.com/wiki/extensions/AjaxLogin/AjaxLogin.php on line 81, referer: http://xxxxxxxx.com/wiki/Special:SpecialPages

This line is part of the efAddAjaxLoginVariables( $var ) function which yields.

$vars['wgEnableAjaxLogin'] = ( is_array( $wgEnableAjaxLogin ) ) ? in_array( $vars['skin'], $wgEnableAjaxLogin ) : false;

I got the same problem when I installed AjaxLogin for MediaWiki 1.17. I managed to solve it by doing this fix.

--- AjaxLogin.old20110913.php   2011-09-13 21:30:37.997401022 +0200
+++ AjaxLogin.php       2011-09-13 21:31:38.407420633 +0200
@@ -78,7 +78,9 @@
 function efAddAjaxLoginVariables( $vars ) {
        global $wgEnableAjaxLogin;
 
-       $vars['wgEnableAjaxLogin'] = ( is_array( $wgEnableAjaxLogin ) ) ? in_array( $vars['skin'], $wgEnableAjaxLogin ) : false;
+       # Fix for MediaWiki 1.17.
+       global $wgUser;
+       $vars['wgEnableAjaxLogin'] = ( is_array( $wgEnableAjaxLogin ) ) ? in_array( $wgUser->mSkin->skinname, $wgEnableAjaxLogin ) : false;
        if ( $vars['wgIsArticle'] == false && $vars['wgEnableAjaxLogin'] ) {
                $vars['ajaxLogin1'] = wfMsg( 'ajaxLogin1' );
                $vars['ajaxLogin2'] = wfMsg( 'ajaxLogin2' );

But I got a javascript error saying "Exception Caught: Internal error in ApiAjaxLogin::execute: Unhandled case value" when I tried to login so I gave up and tryed the trunk version instead. Worked much better! Added that to the instructions btw. --John Ericson 20:25, 13 September 2011 (UTC)

Login Freezes

I can click on login so the window appears, however when I put in the username and password it just disables all the fields/buttons on the dialog, then doesn't do anything else.

After Click "Log In" button, nothing happens

MW 1.16.2, Vector Skin (default for all users). Ajax enabled (using CategoryTree Ajax Extension). After I click the "Log In" button, the buttons gray out, but nothing further happens. Tested in IE 8/9, Firefox 4, and Chrome 10. Lynxcub 21:33, 24 April 2011 (UTC)

Same problem happened to me when I tried the 1.17 version. Try trunk instead, worked for me. See my answer above. --John Ericson 20:27, 13 September 2011 (UTC)

tried the SVN, tried 1.17 version, tried 1.16 version, tried your updated listed above, but still not working. svn/snapshot brings up a login page with a double display of the login fields. 1.16 version, brings up the ajax window, but fails to send the data through for successful login. 65.100.172.25 06:39, 14 September 2011 (UTC)