Scheduled Maintenance

[geckzilla]

Asterisk will be migrating to a new server on Monday, January 8th between 12:00 to 13:00 EST. It will likely be unavailable during that time.

[geckzilla]

Asterisk is migrated. Some odd bits are still being looked into. If you notice anything aside from http://asterisk.apod.com/lectures being inaccessible, please do mention it.

[geckzilla]

The forum was migrated again, and there were a few issues. They are still being worked out, but the major one was that the "Discuss" link from APOD was generating new threads, and wasn't correctly pointing to old threads. That's been fixed.

[geckzilla]

Updated the board, and things look a bit funny. Need some time to fix it. Bear with me.

[geckzilla]

Well, it should look and function like Asterisk did before. It is possible there are still some small things involving the css that I have customized over the years, mostly involving video and image submissions and how they appear in the threads. Still taking a look at those, though my memory may be failing me...

If you notice anything funky, please be sure to do a hard refresh (ctrl+F5 or command+F5) before reporting it.

[bystander]

[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 121: preg_replace(): Compilation failed: unrecognized character after (?< at offset 64
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4517: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3268)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4517: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3268)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4517: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3268)

http://asterisk.apod.com/viewtopic.php?t=35562

[geckzilla]

What were you doing when you saw that? I don't see those errors. I do see some bbcode isn't parsing in the post text, though. I think some things with the way phpbb parses bbcode have changed... some of our old tricks might not work anymore, but the img3 tag just looks broken. Hmm.

[bystander]

Just following a link from google search I did. I think the problem has to do with some of the built in tags. If you take the <size> tag out of the post, it works (kind of), but the <b>, <i> and <url> tags won't parse inside <img3>.

[neufer]

What were you doing when you saw that? I don't see those errors. I do see some bbcode isn't parsing in the post text, though. I think some things with the way phpbb parses bbcode have changed... some of our old tricks might not work anymore, but the img3 tag just looks broken. Hmm.

Just following a link from google search I did. I think the problem has to do with some of the built in tags. If you take the <size> tag out of the post, it works (kind of), but the <b>, <i> and <url> tags won't parse inside <img3>.

Know the quiet place within your heart and touch the rainbow of possibility; be
alive to the gentle breeze of communication, and please stop being such a jerk. — Garrison Keillor

• Bystander made the Keillor Garrison in less than 12 parses

[geckzilla]

Sigh, well, best I can tell the BBCode engine got a rewrite, and certain things just aren't going to work like they used to. We'll have to rethink how we do them, and possibly come up with different bbcodes for the things you do, bystander.

[bystander]

Yeah, I do get a little wonky sometimes.

I changed <img3> to use a smaller italic font. I guess I'll fix previous posts as I come across them. There are still other things I don't like about the new BBCode engine (<list> for one), but I guess we'll have to learn to live with them.

I do like the link back they include when you quote someone.

[bystander]

FWIW: It seems the result of any mixing of built-in codes with self-defined codes is uncertain at best.

[geckzilla]

I think they nest properly until the nesting tags have more than one {TEXT} token, so if we can change any of them to {SIMPLETEXT}, they might start nesting better again. Don't hold me to that, though.