Magic: The Gathering Gatherer Autolinker is a WordPress plugin that takes special tags in your posts and converts them into links to the beta version of Gatherer, the official Magic: The Gathering online card database.

Installation

1. Download and unzip the plugin.
2. Upload mtgautolinker.php to wp-content/plugins.
3. Activate the plugin inside of WordPress.

Usage

Anywhere inside of your post you can put [mg]Card Name[/mg] tags and it will appear as Card Name on your blog. The card name you use does have to be exact and there isn’t a way to speicify custom link text, but anyone with even basic PHP knowledge could add one with little effort. If you’d like it to work in comments too just add add_filter('comment_text', 'mgreplacer'); under the addfilter line at the bottom of the file before ?>.

Source

This plugin really couldn’t be any simpler, you could have done it with minimal time and effort.
<?php
/*
Plugin Name: MTG Gatherer Autolinker
Plugin URI: http://tragicallynull.com/2009/02/14/magic-the-gathering-gatherer-autolinker-wordpress-plugin
Description: Autolinks Magic: The Gathering cards to the newly released version of the Gatherer (card database) using [mg]Card Name[/mg] tags.
Version: 0.3
Author: John Stone III
Author URI: http://tragicallynull.com
*/
function mgreplacer ($text){
$mgreplace = '/(\[mg\])(.+)(\[\/mg\])/';
$mgreplacement = '<a href="http://gatherer.wizards.com/Pages/Search/Default.aspx?name=+[&quot;\\2&quot;]">\\2</a>';
$text = preg_replace($mgreplace, $mgreplacement, $text);
return $text;
}
add_filter('the_content', 'mgreplacer');
?>

It’s really so simple just about anyone can edit it to make other custom “autolinkers” of their own.

It turns out that my VPS’s Debian install has been configured with exim4. I don’t know when I installed it, but it might have been included as a dependency somewhere down the line. For some reason PHP wasn’t feeling the love. So out with the exim4 and in the the postifx. I went in and used apt-get to install postfix. This automatically removed exim4, installed and configured postfix, allowing me to use PHP to send emails.

apt-get install postfix

Don’t do this if you’re actually using exim4 for your real email service, this is just a fix for people who need PHP to send email and use an external service like Gmail for their domain’s email.

To fix your problem all you need to do is right click on the Nod32 system try icon, then click “Advanced Setup…” navigate the tree to “Antivirus and antispyware > Web access protection > HTTP > Web Browsers” and make sure uTorrent and any other torrent programs are unticked (red X).

The problem is that Nod32 thinks uTorrent is a browser and then scrutinizes the traffic as such creating a very narrow bottleneck choking your normal internet traffic to a crawl. It doesn’t effect normal web browsers because of the low amount of throughput they have.

Symptom(s)

When you try to add, play (Video will play for about 6 seconds) or transfer .mov or .mp4 (mpeg-4) video files (even from the iTunes Music Store) one of three things will happen.

• iTunes gracefully crashes and Windows Vista continues to function
• Windows Vista completely hangs and ceases to function forcing a hard power-down.
• Windows Vista will crash resulting in a Blue Screen of Death (BSOD) with the error KERNEL_STACK_INPAGE_ERROR.

The same outcome can occur when trying to transfer a large amount of photos to an iPod using iTunes.

I am using an HP A1510N with the A8N-LA Nagami2 (nForce 430 (MCP51)) mother board. I also have an additional SATA and USB HardDrive, an additional 512MB RAM and a PCIe ATI Radeon x1950PRO, I believe this error may be hardware specific as this error doesn’t occur on my Dell notebook.

The Solution

I reformatted and reinstalled Windows Vista, without installing anything else, even Windows Updates, I installed iTunes, but the video problems (above) persisted. I then installed all of the Windows Updates (Including optional drivers except for a Realtek sound driver) and the latest driver for my graphics card, restarted my computer and iTunes could play, transfer and add video perfectly, except for a slight problem with audio sync. Reformatting may not be necessary, check to see if you have an update in Windows Update named NVIDIA nForce Serial ATA Controller and install if it’s not already, restart and test your video files.

The key to the solution seems to be the NVIDIA nForce Serial ATA Controller which seems to have been released yesterday. It would make sense if iTunes was trying to access a harddrive function that the driver/ couldn’t handle resulting in Windows Vista crashing because it suspected a damage Page File. Of course, I can be SURE that this was the fix. I will update this post if anything breaks later on because of a program incompatibility.

The Symptom(s)

You plug in the Wireless Gaming Receiver and power on the controller, all 4 quadrants of the controller’s LEDs blink, you attempt to sync the devices by first pushing and holding the button on the Receiver until it begins to blink and then you push and hold the button on the top of the controller until the leds spin, they stop blinking/spinning at the same time, yet the controller continues to blink, 3 quicker blinks after the attempted sync and then continued slow blinking.

The Solution

The only solution I’ve found is to use a powered USB hub, the side USB ports on a Dell monitor also work.

Ok, so you’ve got your FreeBSD installed on your computer, you’ve booted up for the first time and you’re looking at the login: prompt. You’ll need to login as root to configure sudo to allow yourself to run commands as root from your normal account though SSH. So type root at the login: prompt hit enter and then type in your password. Don’t worry that the letters or *s don’t appear for your password, they’re not suppose to. Once you login you should be at the default shell, something like freebsd#, where freebsd is the host you entered during the installation.

Now, from the freebsd# prompt and type visudo and press enter.
freebsd# visudo

You should have the default sudoers file in Vi. Use your arrow keys to move down the page until you see the line root ALL=(ALL) ALL, with your cursor on that line type o, this should create a new line. From there you can type the following line where [yourusername] is the normal user account you setup during the OS installation without the brackets…
[yourusername] ALL = (ALL) ALL

For for example, mine is…
john ALL = (ALL) ALL

From here you press escape then “:” without the quotes, then “x” without the quotes and then hit enter, this will save the file and exit Vi. And now you know why you installed Pico.

This will allow you to run any command as root, as long as you know the root password thus allowing you remotely administer your system completely through SSH. Now you can type exit to logout at the freebsd# prompt and turn off the monitor. From here we will be using SSH.

The page they provide is very helpful but they don’t always work, sometimes it has nothing to do with your network connection setting at all. This is what worked for me, and hopefully they’ll work for you. It’s a simple fix, but will require you to “restream�? the Guild Wars data again.

Step 1: Make sure there are no instances of Guild Wars (Gw.exe) running
Step 2: Rename the file Gw.dat to Gw.old in your Guild Wars directory.
Step 3: Run Guild Wars (Gw.exe).

That fixed my problem, but it might not fix yours, so I’ve also included a guide below to help you asses where the problem is occurring and what steps to take to receive support.

First thing we need to do is see what kind of network issue you’re having. You can do this by going to start Start then clicking on run Run, and then typing cmd to open the command prompt. Once there you need to navigate to the Guild Wars install directory, you can do this by typing cd and then the directory of your Guild Wars install in quotes, by default this will be cd "C:\Program Files\Guild Wars".

Once there we need to run the Guild Wars diagnostic tool by typing Gw.exe –diag, this will output a file called NetworkDiag.log in your Guild Wars install directory. To make sure you’re able to connect to the Guild Wars servers, you need to open NetworkDiag.log with a text editor, then find the “= Checking server connectivity�? section. There you will see a list of servers with either “connect succeeded�? or “connect failed�? by them.

If you’re showing a large number of “connect failed�? messages, or you’re showing all “connect succeeded�? messages but you’re still unable to connect, you should contact Guild Wars support. You can do this by going to this web page, filling out your information and attaching your NetworkDiag.log file. They should get back to you within 24 hours.