Moving to New Server

I just paged through the humor thread (lots of images) and couldn't duplicate the problem, even with Safari 15.6.1, but it's not impossible there's some Javascript issue that only presents itself under certain circumstances. If you can provide an example image link I'll see what I can figure out.

Should be working now, but only after you do a hard reload, which for Safari I think is hold down CMD and Option while clicking on the refresh icon in the address bar. In Chrome you only have to hold down Shift. The display of images in old messages won't change unless they're rerendered (do an edit/submit cycle).This problem affected smilies because their path was defined using "http" instead of "https". For security reasons, "https" pages wont fetch "http" images. This is fixed.Also, missing images are now a link to the missing image's URL, and if you right click on the missing image you can copy the URL for the image by selecting "Copy Link Address" (Chrome) or " Copy Link" (Safari) in the context menu.

I poked around a bit and wasn't able to find an old message with peek misbehavior. If you give me the message ID (in faint text in parens next to "Message m of n" at the upper left of the message) I'll take a look.

Thanks, I got it. It affects all messages in the message ID range 884952 to 894171. I'm cleaning up something else right now, will clean this up next.

Should have responded to this: Messages are rendered into their final form before being saved to the database. Bread crumbs of the original form entered by the user are left behind so that the message can be transformed back for editing and peek.This year I made a change in stages to the way messages are represented in their final rendered form, and somehow messages from roughly March 16, 2021 to May 3, 2022 were all affected in this way. It's probably a case of me carrying out one of the transformations on the wrong range of messages. It's easily fixed by a script that rerenders the messages.This transformation required that different message ranges be treated differently because of the way dBCodes and formatting evolved over the years. For example, few remember that you used to be able to refer to a message in another thread by saying [msg=4,6153,17] where the first argument is the forum ID, the second the thread ID, and the third the message number. This form is still accepted but deprecated (and it doesn't produce a link to the right message right now, something else I'm looking at). Now the recommended way to link to a message in another thread is to use the [mid] dBCode.When I'm done all messages should be represented in the same form in the database. It shouldn't cause any changes visible to users, assuming I make no more mistakes.

Peek and edit should now work properly for all messages. Please report any problems to this thread.AbE: I think the message you were most interested in was Message 110.AbE2: You're going to prefer the edit version if you're interested in the <pre> section because peek doesn't preserve the white space.

Edited by Admin, : AbE.

Edited by Admin, : AbE2.

The way the peek text of a message is displayed when you hit the peek button beneath the message has changed so that white space is now preserved.

Thanks for noticing. I forgot to mention that you'll need to do a hard reload so that the CSS loads again. For Chrome hold down shift and hit the reload icon. For Safari I think it's CMD+Shift plus the reload icon. Other browsers are similar. Let me know if that works for you.Also, when replying to a message the message you're replying to can be optionally displayed in peek mode by selecting the Peek Mode radio button. This has also been updated so that it preserves white space.

I just released a minor improvement to the message hoverboxes. They now contain the message date and author.Messages in search results didn't used to have hoverboxes and now they do.The size of webpages with many hoverboxes, such as a page of messages for a thread, are about 4% or 5% smaller, not enough to be noticeable.Please report any problems here.

Thanks for calling attention to this. I again forgot to note that you have to do a hard reload in order to get the new version of the Javascript code. On Chrome and Firefox hit reload while holding down the shift button. On Safari hold down Cmd+Shift. Other browsers probably something similar.

Not that he's not special, but it worked because he tested it after I released the fix around 10:30 EST this morning. All hoverboxes should be working now. Please report any non-working hoverboxes here.

I see the problem, will try to fix it this morning.

Problem is fixed.My guess is you were logged out. When logged out the date was being fetched incorrectly, causing Javascript syntax problems.

If you think you were logged in then it is extremely likely that you were. The default is to log people out automatically after a year of no activity. The cookies that determine login status have a 1-year lifetime.There may be other causes of the behavior other than not being logged in, but that was the only one I was able to identify.

The hoverboxes for thread names now include the originator and the origin date. Do a hard reload to also see extremely minute improvements in formatting.