User talk:Ryan lane/LQT Archive 1

SmoothGallery
Hi, are there any examples of how Extension:SmoothGallery looks and works? It would be cool if you could link to a test/example page for this extension. Thanks --128.250.80.15 01:40, 10 January 2007 (UTC)


 * Yeah, I wish I had a publicly available test site. I may look into getting one. The SmoothGallery site has examples of SmoothGallery in action, but nothing that is user modifiable like this extension allows. --Ryan lane 21:32, 11 January 2007 (UTC)


 * I have one now. It is at my sandbox. --Ryan lane 06:55, 3 March 2007 (UTC)

Hi, I get a problem with your smoothgallery extension installed on a Spanish interface wiki http://es.antropologia.diwiki.org. When I edit any article, around 10 "undefined" labels appear after the normal edit button bar.s!? Benjamin bois 17:21, 25 June 2007 (UTC)


 * Yeah, this is a known bug, and the fix is documented on the extension page (Extension:SmoothGallery). This is fixed in MediaWiki 1.10+. --Ryan lane 19:26, 6 July 2007 (UTC)

Memorize
Hi, Ryan.

I've added references to your memorize extension to Wikiversity's quiz project. We're mainly centered around the quiz extension at the moment, but the quiz extension isn't really designed to do pair matching, and your memorize extension looks excellent (the matching mode is great).

Perhaps you could join the quiz project and tell us a bit about how your extension is developing. What stage is it at? Might it be implemented on Wikiversity? Have you got people giving you feedback about it?

Cheers,

McCormack 06:36, 15 April 2007 (UTC)


 * Hello,


 * The memorize extension is a really simple extension. It essentially just adds a parser extension tag, and adds the Memorizable javascript into the headers. People can create regular tables, and add the tag into the table headers. Most of the real development work is over at Memorizable. I believe the license on the javascript would be compatible with the Wikiversity project, and the license on the extension is GPL. If it is added to Wikiversity, I'd be happy to offer any further development necessary.


 * The extension is currently stable. The only change really needed is to make the javascript only output when the extension is actually in use on a page (which is an easy fix).


 * It would be nice if the javascript could handle more than two columns of data, and I may add support for that in the future (if memorizable will accept patches that is). --Ryan lane 13:31, 16 April 2007 (UTC)


 * Hi Ryan. I see that the JS file is released under an "X11 (aka MIT) open source license". Is this compatible with Wikimedia projects? Do you have any contact with the copyright holder of the JS file? McCormack 04:54, 3 May 2007 (UTC)


 * Suggested changes before moving to Wikiversity...
 * It should be able to start in "matching mode".
 * It should be possible to remove the choice between modes.
 * It should be possible not to have the options. (Optional options)


 * McCormack 04:59, 3 May 2007 (UTC)


 * I'll take a look at the javascript to work these changes into the extension. As for the license, it is probably up to Wikiversity whether or not they'll want to use it. The license given says it is fine to use the software in any way as long as the help section, and links to memorizable.org are kept. I'll talk to the developers about how we can meet their license requirements and still be able to modify the code how we like. --Ryan lane 18:10, 4 May 2007 (UTC)


 * One of the things I noticed on reading the licence is that it is a custom version of the X11 open source - and the custom bit is a requirement for a visible credit to the programmer (in the options section). I suspect this would have to go, although I'm sure that information about the origin of the script would be given in the help page we would build for it. Thanks for following up on this! McCormack 18:21, 4 May 2007 (UTC)

LDAP Authentication
Hi Ryan. Any idea when you might be able to get to "1.1f: Add options to specifiy search bases for users, and groups"? We need to specify a different base for our groups. &mdash;JEREMY 16:05, 6 June 2007 (UTC + 8.00)


 * I'm out of the country for work right now. I've been working on the plugin some out here though, and I just added that in a couple of days ago. I'll send it up to the SVN server when I get back (a few days from now). --Ryan lane 05:15, 10 June 2007 (UTC)


 * Good stuff! Thanks for that! &mdash;JEREMY 15:45, 11 June 2007 (UTC + 8.00)


 * Sorry for the wait, I've added that change in the latest SVN version. The version in SVN (revision 23338) is currently stable. I'll be releasing it soon, but you don't really need to wait for the release. Just make sure to use revision 23338. --Ryan lane 21:06, 24 June 2007 (UTC)


 * Thanks again. Err... So, how do we actually go about implementing groups search? Where do we specify the base, for example? &mdash;JEREMY 11:41, 26 June 2007 (UTC + 8.00)


 * Wow, you want documentation too!? ;) Kidding of course. I just added the config options to Extension:LDAP Authentication --Ryan lane 14:27, 28 June 2007 (UTC)


 * When we $wgLDAPUseLDAPGroups = array("Interzone"=>true); we get Warning: in_array: Wrong datatype for second argument in LdapAuthentication.php on line 1401. Where we should start debugging? &mdash;JEREMY 10:32, 04 July 2007 (UTC + 8.00)


 * Well, that looks like a bug, but it may be happening because you may be missing some configuration. What does the rest of your configuration look like?


 * Like this:

$wgLDAPDomainNames = array("Interzone"); $wgLDAPServerNames = array("Interzone"=>"spike.per.[SLD].[TLD]"); $wgLDAPUseLocal = false; $wgLDAPEncryptionType = array("Interzone"=>"clear"); $wgLDAPSearchAttributes = array("Interzone"=>"uid"); $wgLDAPBaseDNs = array("Interzone"=>"ou=People,dc=[SLD],dc=[TLD]"); $wgLDAPGroupBaseDNs = array("Interzone"=>"ou=Groups,dc=[SLD],dc=[TLD]"); $wgLDAPGroupUseFullDN = array("Interzone"=>"false"); $wgLDAPLowerCaseUsername = array("Interzone"=>true); $wgLDAPGroupObjectclass = array("Interzone"=>"posixGroup"); $wgLDAPGroupAttribute = array("Interzone"=>"memberUid"); $wgLDAPGroupNameAttribute = array("Interzone"=>"cn");
 * 1) $wgLDAPUseLDAPGroups = array("Interzone"=>true);
 * (Actual [SLD] and [TLD] redacted.)
 * When we uncomment the $wgLDAPUseLDAPGroups line, we get the error. &mdash;JEREMY 10:34, 10 July 2007 (UTC + 8.00)


 * I've summed up how to do group synchronization as well here: Extension:LDAP_Authentication I'll try to track down the bug, make it output a warning, and fail gracefully. --Ryan lane 19:24, 6 July 2007 (UTC)


 * Ah; it's the quotes around "false" in the line following the one commented-out in the listing above. We remove those and it works!&mdash;JEREMY 14:38, 12 July 2007 (UTC + 8.00)

Working with the Access Control extension?
Hi Ryan. We've got the group restrictions stuff working (thanks!) but we're now trying to use the LDAP groups with the Access Control extension. It's not working out of the box, and we're having difficulty verifying that the LDAP groups are actually being exposed to mediawiki in such a way that the GBAC extension can see them. Any tips for beginners?&mdash;JEREMY 15.06, 18 July 2007 (UTC + 8.00)


 * Hmm... I haven't looked at this much (as those extensions really just provide an illusion of security). I think the author of the plugin wrote a patch to work with the LDAP plugin. Although, I may be thinking of another one of those access control extensions. I'll take a look when I get a chance. --Ryan lane 21:08, 23 July 2007 (UTC)


 * Is there some easy way for us to view/expose the groups that your plugin has grepped from the directory?&mdash;JEREMY 12.20, 01 August 2007 (UTC + 8.00)


 * As far as I can remember, the groups are actually created in the wiki when you add group permissions in LocalSettings.php. Once the groups have permissions associated, they should be exposed in the interface. --Ryan lane 19:06, 6 August 2007 (UTC)

Password Encryption
Ryan, In your example you have the following

$wgLDAPProxyAgentPassword = array( "testLDAPdomain"=>"{SHA}KqYKj/f81HPTIeAUav2eJt85UUc=" );

What method are you using to encrypt the password? And are there any requirements for changes made to a core mediawiki install to allow for this?


 * Although this should work, it seems to be hit or miss depending on the LDAP server and configuration. I got that password using phpldapadmin though. --Ryan lane 21:06, 23 July 2007 (UTC)