Ever been constructing a verbose and complex reply to an email on a webmail site, only to have the browser crash when you were about to hit send? Or perhaps putting the finishing touches on your Wikipedia edits to the particle physics article (I know I have) and have all of your hard work lost in the blink of eye?

Fear not, salvation is at hand! Although many Web 2.0 sites providing text-editing will save drafts and provide a reasonable text editor, nothing beats your favourite text editor of all time, Vim. Or Emacs. Or whatever you would prefer to use. Why shouldn’t you be able to use any text editor you like? It’s your computer and your time after all!

If you are using Firefox, your problems are over. Introducing It’s All Text. Install this handy plug-in to your Firefox, set the default editor to your liking and you are off and running! Now any text box on any webpage will show a small edit button on the bottom right corner allowing you to launch the editor of your choice. Edit to your heart’s content using the tools you are most familiar with, then save and exit the editor and have all your work sent back to the browser text box.

Even if the browser crashes mid-edit, your editor program will be unaffected and your work will be safe. You can save your work in the editor in addition to any swap or draft files it creates for even more safeguards.

It’sAllText works in Firefox 3.0. If you have older versions of Firefox you may wish to check out MozEX which is a similar plug-in.

We’ve discovered some interesting things about Windows, and they never fail to cause some head-scratching. We had cause to go rooting through a customer’s wordpress installation recently to hunt down the cause of PHP errors, and discovered two WTFs here.

The first was the breakage of various scripts in the wp-admin directory. Through means unknown, every array definition was broken by the addition of a file path. If you grok PHP, you’ll recognise that this isn’t syntactically valid:

$defaults = array(

'show_option_all'../../../wordpress/wp-includes/ => '',
'show_option_none'../../../wordpress/wp-includes/ => ''

);

Python is our preferred in-house language, but breadth of knowledge is more important for a sysadmin. Cleaning up the PHP was a snap, but it’s a mystery as to how this happened in the first place; according to the customer it “just stopped working”. It looks a bit like someone got busy with a site-wide find-and-replace. This isn’t implausible, but it seems far less likely given that this is on a Windows machine.

(more…)