MediaWIKI – Chage Mediawiki Logo

How to change my MediaWiki logo image?

In order to change the MediaWiki default logo you should do the following:

1. Create an image for your logo with dimensions of 135×135 pixels.

The recommended format for the image is .png, but other formats like .gif or .jpeg are also ok. Please note that if you upload image with different dimensions it may not be displayed.

2. Upload your logo image somewhere on your web hosting account.

For example you can upload it directly in the public_html folder.

3. Add or edit the $wgLogo line in the LocalSettings.php to contain the path to your logo

The LocalSettings.php file is located under the directory where your MediaWiki is installed. If it is installed directly in the public_html, this file will also be there. If it is installed in a subdirectory of the public_html, the file will be located in the subdirectory.

You should open the LocalSetting.php and look for a line that starts with $wgLogo. If there is no such line you should add it yourself and if there already is such a line you should edit it to contain the path to your logo. For example if we suppose that your logo is named logo.png and you have uploaded it directly in the public_html folder the line should look like:

$wgLogo = “logo.png”

If you have uploaded the logo in a subdirectory of you public_html, be sure to paste the whole path. For example if you have uploaded you logo logo.png in the skins/common/images/ directory the line should look like:

$wgLogo = “skins/common/images/logo.png”

4. If you have followed the instructions above and you still do not see your logo, please make sure that in the LocalSettings.php the image upload is allowed.

To do this open the LocalSettings.php file and change the line

$wgEnableUploads = false;

to

$wgEnableUploads = true;

NB: It is possible to simply overwrite the default logo installed with MediaWiki, but this is strongly advised against, as an upgrade may end up overwriting it or change the default location of this file.

Redhat – Fully Disable SELINUX

Fully Disabling SELinux

Fully disabling SELinux goes one step further than just switching into permissive mode. Disabling will completely disable all SELinux functions including file and process labelling.

In Fedora Core and RedHat Enterprise, edit /etc/selinux/config and change the SELINUX line to SELINUX=disabled:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted

… and then reboot the system.

For the other Linuxes which don’t have the /etc/selinux/config file, you just need to edit the kernel boot line, usually in /boot/grub/grub.conf, if you’re using the GRUB boot loader. On the kernel line, add selinux=0 at the end. For example,

title SE-Linux Test System
       root (hd0,0)
       kernel /boot/vmlinuz-2.4.20-selinux-2003040709 ro root=/dev/hda1 nousb selinux=0
       #initrd /boot/initrd-2.4.20-selinux-2003040709.img

You will have to reboot to disable SELinux, you just can’t do it while the system is running.

VMware – Canot Shutdown VM ( another task in progress)

I tried to do a shutdown of a VM from VirtualCenter (vSphere client) only to recieve an error: “another task is already in progress”.

Looking through my event-log in VirtualCenter, I saw that an earlier task (a cloning of same VM) had failed due to a timout.

The solution seems to be to log into the ESX servers service console and stop and start the mgmt-vmware service by doing:

# service mgmt-vmware stop

wait 30 seconds or so and start the service again

# service mgmt-vmware start

It seems that the wait is important. A mere “# service mgmg-vmware restart” did not resolve the issue.

This procedure will temporarily disconnect your esx-server, and VM’s running on, it from Virtual Center but otherwise it will not disturb your operation.

Squirrelmail — Error while opening Mailbox

Error message

"Thread View" does not work
ERROR: Bad or malformed request.
Query: THREAD ORDEREDSUBJECT ISO-8859-1 ALL
Server responded: Error in IMAP command UID: ORDEREDSUBJECT threading is currently not supported.

Solution

You need to log into Squirrelmail then click on “Options” then “DisplayPreferences” and make sure that “Enable Thread Sort by References Header” is set to “yes”.