I had $wgSMTP set up to talk to a remote exchange server, but password resets just weren’t working from the wiki. It turns out all I was missing was the ‘php-pear-Mail package’ (in fedora, for debian or other systems it may be a different package name). I started by checking any logs related to this problem… mail.php missing in UserMailer.php - dependency problem

I wanted to simplify the toolbox for a special purpose wiki, but everywhere I searched all I could find was how to change the name of the toolbox, or how to show it only to logged in users, etc. To delete one of the default toolbox links, just change the data value to something it will never see. You could remove the if statements completely for each link you want removed, or just change the data value to something that will never result in entering the if statement. It’s less intrusive than removing the code completely. Either way, you won’t be deleting the toolbox function, only the link from the interface — which is exactly what I wanted. If you want to trim the navigation part of the sidebar, that’s built right in. Just go to Mediawiki:Sidebar and edit that page.

Have you ever received an instant message from a stranger with the words Coho, Trout, or Salmon in their screen name? If the answer is yes, then you’ve been picked up by Project Upstream bot. Did you dig the hook in deep by starting a conversation…or perhaps an argument? I have run into a few Coho’s so far and they’re usually good for interesting conversation.

Check iptables or other firewall applications running on that machine. If ldap traffic is being blocked, this could be causing it to hang. That’s what happened to me. I changed the firewall rules and forgot to add the ldaps rule and it broke. I could work around it by hitting “i” while booting and it would go into Interactive mode and allow me to say No to the MessageBus service. Everything else came up fine in runlevels 3 and 5, but it would always hang when loading the dbus app.

I read in a bunch of places that you can’t use HTTP["scheme"] to redirect http:80 traffic to https:443 without using 2-3 levels of nesting with socket and host. But that’s just not true. The only reason it doesn’t work at first is because http is a subset of https, so be more specific with http$ and it works with just one line in lighttpd.conf.

Now edit the lighttpd.conf configuration file to enable ssl. Use the public facing interface’s IP address instead of mine, unless yours happens to be 192.168.1.2 too! And nmap or netstat will let you know it’s listening on port 443

Enabling LDAP authentication should take you about 2 minutes, unless you type with just 2 fingers. Then maybe 3 or 4. …If you don’t allow anonymous connections to your ldap, give it a user/password combination that has enough privs to do the lookups, or just use your master account if you’re just testing or don’t really care. … Now tell it what parts of your webserver you want to protect and how. You can specify any string you’d like for the realm. Here I require an LDAP user account name and password just to get to the wiki main page, and only admin can see the server-config page… Restart lighttpd and you’re done.

blah blah, mediawiki http://blog.rootninja.com, And finally, “To complete the installation, move config/LocalSettings.php to the parent directory.” just like it says…

I didn’t think anything of it when I read it in the news this morning. And then I went to linux.com to log in, browse the forums, and try to answer any interesting questions, and BAM!!! “Linux.com is relaunching!”

I ran into these two methods for grabbing just the unique elements from a list, one keeps the order, the other relies on sorting the list. But then I found some strange code that works really fast. Check out this amazing little one liner!