AjaxLife Blog

Linden Lab make a good point – you probably shouldn’t be typing your passwords into my site, regardless of my promises that I don’t read them (which I don’t).

Then again, they’ve said that several times during AjaxLife’s lifespan, so I assume you all already thought about that.

So, it turns out that this month, against all (my) expectations, donations were actually higher than expenses – hooray!

If donations continue at this rate, AjaxLife’s continued availability is ensured (barring major world-ending incidents and/or the bankruptcy of Amazon.com and/or my death and/or…)

Many thanks to all of you.

Also, even more thanks to the extremely generous French person.

Due to people insistently linking to the IP address AjaxLife redirects to (which changes often, thus breaking any links to it), I have changed the way AjaxLife redirects. Instead of actually redirecting you, it now uses a frame in order to maintain the URL. This means that refreshing whilst logged in won’t work – you’ll be sent back to the login screen.

http://ajaxlife.net/noframes is still frameless, however, should this be necessary.

I’m working on new AjaxLife features. Hoorah.

I’d hoped to have a new version out by last Friday, but I changed my mind about what I wanted to get into this one. As such, here are some screenshots of the upcoming features to make up for it:

See pictures!

I’ve worked out why I can’t use AjaxLife at school.

You have attempted to access the following web page:

http://static.ajaxlife.net/AjaxLife.Libs.IE6.js

Access has been blocked because:
Page content filters applied – score = 7576

Since this file contains only prototype.js, scriptaculous and ExtJS, I haven’t a clue why it’s been blocked. It is annoying, however.

I’m bored, so I’m going to see if I can get round this bug.

First step: reproduction. This is easy:

Step 2: Found the offending XML:

<member><name>name</name><value><i4>1</i4></value></member>

(“i4″ should be “string”)

Step 3: Give up because my internet connection’s dying.

Step 4: Roll out fix.

Step 5: Announce success.

I’ve always wanted to do this:

(click to enlarge)

Try it yourself! (To work around SL’s issue with frames, use http://ajaxlife.net/noframes.)

Okay, so I found the error. It was an error in the deploy script.

IE6 gets a different script to everyone else (grumble). I’d managed to make a typo in the deploy script that caused the following line to embed itself in the script:

//}();/* Copyright (c) 2007, Katharine Berry

Instead, it should have either been omitted or read as follows:

//}();
/* Copyright (c) 2007, Katharine Berry

Unsurprisingly, there was a syntax error on the line immediately following this one. The typo causing this has been fixed.

As an added bonus, you can now log in simply by hitting return. This will serve as an interim fix for those whose screens are too narrow for the login screen to fit until I come up with an implement a better solution. Also it’s generally easier.

Note that IE6 still occasionally hangs on “Precaching…”

This is caused by the mapapi failing to load, and can generally be fixed by reloading the page. It’s horribly inconsistent. As are many IE6 issues.

After some maintenance, AjaxLife has been restored. As a bonus, it’s now available in Japanese and Portuguese (Brazil). Just pick the appropriate language from the box at the right of the screen. Also supported: English and Hebrew.

Thanks to Alissa Sabre for the Japanese and Aurelio A. Heckert for the Portuguese.

[UPDATE] IE6 still doesn’t work. I don’t really care any more. Go get a decent browser, the 13% of you who still use IE6 with AjaxLife (IE6+7 are at 25%, Firefox is now at 62%, Safari at 8%, Opera at 3% and the built-in SL client at 0.5%).

I can’t test IE6 in the same place I can work on stuff, so it’s officially unsupported. Because it’s horrible.

I may or may not have fixed the issues with IE6 that crept up in the last update. We’ll find out tomorrow!

Also, AjaxLife is now available in Hebrew: