In the dictionary export feature in some lines the tabs that are supposed to be inserted are missing, meaning that the export file cannot be reimported as-is.

I'm not sure what happened here, other than the blank thread name (which was intentional). The thing that happened, and my resulting descent further into madness, is chronicled in the thread.

edit: Also I can't give the thread a title because the original first post got overwritten by the first post bug.

re buggy Unicode support, this looks relevant: http://mathiasbynens.be/notes/mysql-utf8mb4

also, putting this here from my test thread so I don't lose it to overwrites:
Triggered the post overwriting bug after creating a second post and deleting the first post. Post overwriting bug inserted post into the space after the second (but appearing as first) post. Then deleted that post and both posts disappeared.

??

I think the ZBB used to have this bug; if you entered any characters beyond a certain Unicode code point, it wouldn't save your message. ? *ℱ??????????ℯ???ℊ* I think that has been solved there, though. Good to know also for other MySQL stuff, though …

It hasn't been. I tested it yesterday.

quoting Nortaneous:

It hasn't been. I tested it yesterday.

Are you sure? 'cause I definitely fixed something after you left according to your provided documentation.

quoting Rhetorica:

quoting Nortaneous:

It hasn't been. I tested it yesterday.

Are you sure? 'cause I definitely fixed something after you left according to your provided documentation.

On the ZBB, that is. Here, it works.

Aah, yes. Right.

The new thread displayed at the forum's top page is not getting updated properly, as it is currently displaying the premodern conlang thread as the newest thread, when there are definitely threads that have been made more recently than that (which have not been deleted).

Furthermore the top page of the forum is for me displaying that an unread post is present in one of the threads, when it is not displayed as being unread when going to the section page containing the thread, and indeed has already been read.

Conversely, there have been posts in threads which did not show up as being unread at the top level of the forum, which turned out to be unread when I actually opened up the section of the forum containing the thread.

How often does the RSS fetcher in the profiles check for new articles in the feed?

quoting Travis B.:

The new thread displayed at the forum's top page is not getting updated properly, as it is currently displaying the premodern conlang thread as the newest thread, when there are definitely threads that have been made more recently than that (which have not been deleted).

Furthermore the top page of the forum is for me displaying that an unread post is present in one of the threads, when it is not displayed as being unread when going to the section page containing the thread, and indeed has already been read.

Conversely, there have been posts in threads which did not show up as being unread at the top level of the forum, which turned out to be unread when I actually opened up the section of the forum containing the thread.

Myself I was attributing this to the wonkiness of new post indication in general.

quoting Jipí:

How often does the RSS fetcher in the profiles check for new articles in the feed?

Twitter feeds update hourly, causing the users page to take longer to load when it's stale. RSS blog feeds shouldn't be cached, (i.e. they should always be fresh) but I forget the details. I'll look it up.

quoting Rhetorica:

Twitter feeds update hourly, causing the users page to take longer to load when it's stale. RSS blog feeds shouldn't be cached, (i.e. they should always be fresh) but I forget the details. I'll look it up.

OK – I posted something on my blog yesterday; the feed hasn't yet updated here, though. Not that it's terribly important, but since we're gathering bugs, I just wanted to let you know.

Oh wait, nevermind. I had the RSS URL wrong.

New posts are still showing up for me in the top level of the forum even after I have viewed the posts themselves.

After updating things such as documents, the user is not automatically taken back to the document but rather has to click on a link to go back. This should be changed.

I think that's the redirect bug.

Actually in this case it's just old code—the auto-redirects are kind of a recent thing. The new Recursive Wiki Page template uses them, so after I'm done integrating it, I'll update everything else to follow suit.

Oic. Good to know!

Tiny bug I found while pointlessly updating a blog post: an immediate box formatting tag (ie [box] - apparently brackets in the to-be-displayed link text breaks the link) in the body covers up avatars; I've seen other formatting, headings I think, do this partially before.