Unbalanced delimiters on href's should no longer be a problem in the test playground.

Next up: line choppage.

eta: Line choppage installed.

BTW, the line choppage works one way for Opera and Safari, and another for everyone else. Both are brutal. Long URL's (45+ characters) are doomed on Opera/Safari. All the other browsers should be able to use long url's.

Long url's seem to be preserved, in every browser.

eta: Hang off on testing ...

I hereby nominate Gus for the position of Weremonkey Rock Star.

Thanks, Karl.

Calling all testers. Whats in: tag closing/ordering, url protection in hrefs, and a protection for all browsers from too-wide words.

If you want to be a tester, just drop me a line.

Nebbermind. Still busted.

I'm going to go ahead with getting them to upgrade our Plesk (which'll give us a more recent version of PHP).

Later on we can explore upgrading MySQL.

Sounds good.

Alright. Features available for test:

1. tags should auto-close

2. tags with attributes values (color="blue", href="dogmeat", etc.) should auto-balance the delimiters (href=dogmeat" becomes href="dogmeat" ).

3. Words longer than 30 characters will be force-hyphenated. Long urls are protected from this.

4. URL's entered like this: [link] will be rendered into link . This prevents long URL's from stretching the screen sidewise.

Gus, can we make the "link" a little more obvious. When I do it manually, I use the format "[http://www.link.com...]," which is a format John H came up with back when. You don't have to do it that way, but the brackets would help make the link stand out, especially if placed in a line. Maybe "[link]"?

Maybe "[link]"?

No sweat. It's in.

eta: ION: If I was installing a button/link to the maps, where would I put it? I'm thinking the linker will be a form that posts the userid along.

If I was installing a button/link to the maps, where would I put it?

I would put it in as one of the Buffista Links, under the "Core Buffista Sites" section.

I've contacted support about the upgrade. He says it'll take about an hour (it'll be an upgrade from 5 to 6 and 6 to 7). During which time, web and database services will be intermittently available.

Of course it makes sense to have this done in the offest of our hours, but it wouldn't be gracious to put him out too much. Saturday is our lowest volume day -- are there any objections for picking a time next Saturday morning?

I'll shut the board down, do a backup, let him at it, and open it back up -- I don't think it's safe to have it half up during the pauses in what he's doing.