Tinsology

A while back I published a plugin that allowed you to insert tabs into textareas in wordpress just as you would in a text-editor. Until recently, however, there was a catch: I was only able to get it to work in Opera and Firefox. Today, however, I was contacted by Bill Bryant. He stepped in and took it the rest of the way; adding support for IE, Safari, and Chrome as well as improving the overall functionality.

Check out Tab Override

During my recent host switch I ran into a bit of a problem. After I had moved my database and content to the new server and changed the name servers, requests were still be directed toward my old server. The reason for this is that my ISP had not yet updated their DNS record cache thereby causing requests to be directed to the old server. It typically takes several days for a domain to fully propagate; the amount of time it takes for changes to take effect for an individual depends on how often their ISP updates the DNS records. There is, however, a simple way to avoid having to wait for DNS propagation.

(Note that it may be sufficient just to clear your local DNS cache using the command ipconfig /flushdns)

When resolving a domain a host will usually check for an IP address in its local DNS record first. If it cannot find an address it will pass the request on to the DNS server. The problem occurs when neither the local dns record nor the DNS servers’ records are up-to-date. In most cases the DNS servers’ records are out of our hands so the solution is to manually tell the local machine the IP address for a given domain. You can do this by editing the hosts file located in C:\Windows\System32\drivers\etc (the location should be the same for Windows XP/Vista/7). You should edit the file using notepad with administrative privileges. You can do so by selecting your Start Menu -> Accessories and then right clicking Notepad and selecting Run as administrator (This is how I did it using Windows 7).

You can now add the entries for your domain. Each entry should be on its own line and specify an IP address followed by a domain name:

123.45.67.89 mydomain.com
123.45.67.89 www.mydomain.com

You domain should now resolve to the correct host. Note that this does not in any way effect DNS propagation; users who’s DNS servers have not updated their records will still be directed to the old server. You should also note that this method assumes a static IP address; if at some point the IP address of your web server changes the domain will not resolve correctly and the entries will have to be updated or changed. This shouldn’t be much of a problem considering that the entries can (and probably should) be removed once your ISP has updated their DNS records.

I’m in the process of moving this site from my awful shared host to a shiny new VPS. Expect downtime, errors, unexpected behavior, and sudden explosions.

I’ve been making some progress on the next version of Apparatus. Along with some bug fixes there are a few new features. One new thing is the option to attach a database to allow for more advanced functionality. For now this includes something I’m calling examples generation, which allows you to store your code and output and allow others to view it. This is done without giving them access to the Apparatus interface. Apparatus can still operate in lite mode (without a database), but some features will not be available.

Also in the works is a new template which will serve as the default Apparatus template (the 0.3 template can still be selected). Here is a small preview:

Apparatus 0.4.0 login screen viewed in Opera 10.5

Hopefully the new version should be ready for release by the end of the month. For now version 0.3 is available. If you haven’t yet, give it a try; it is not too late for any suggestions you may have to make it into version 0.4.