Log in
 Search Forum Posts
 Search Results
 

I tried double spaces; that's ignored as well. I finally just added a bunch of invisible characters to break things up. (https://www.invisible-character.net/)

Also, every time I made an edit, the site errored out trying to reload the message and I had to return to my inbox and find the message again, which doesn't seem great.

Not blaming you, or anyone in particular; just kind of ugh. Hang in there. :)

 

Totally agree.

 

If that's the case, that information should be provided to the user when they're typing their message, and stuff that doesn't work at all should be removed from the formatting options.

 

It's supposed to use markdown. I think you have to use double spaces at the end of a line so it counts the line break. :P I'm not even sure that completely works correctly though.

Formatting in PMs is broken  

When sending a PM, it looks like all line breaks are ignored, mashing all paragraphs into a solid block of text. Other message formatting seems to be ignored as well (e.g. lists, horizontal lines, etc.).

Not a huge deal, but it makes messages harder to read/write in a decent way.

 

It should be fixed now. Sorry for the inconvenience.

NULL visitoridentifierID error preventing downloads.  

When I try to download anything from the item exchange i get this error.

Unexpected Runtime Error Something went wrong: Cannot insert the value NULL into column 'VisitorIdentifierID', table 'ItemExchange.dbo.Downloads'; column does not allow nulls. INSERT fails.

I have tried different browsers, I have tried both my linux and windows 11 operating systems, I have also tried a public librarty computer. I got the same error each time.

 

I have the same issue.
New line.
Test.

Yeah it seems to be fine in the forums though.

 

I tried the solutions in this thread, but line breaks keep getting removed when I send a the private message.

 

Sorry I didn't reply here earlier. This was an issue affecting all of the sites on the MX network and it was fixed fairly quickly at the time. Thanks again for reporting it here.