Current status: we've run into an issue with the NEWNEWS NNTP command on 
the new architecture and have had to disable it. Since this was the way 
the web view got postings into the DB I've had to work around it. The 
new method works fine but isn't automated yet. I ran it once to import 
all the posts that were made since the server came back up; these are 
now available in the webview. I'll automate it in the next day or so, 
until then new posts won't turn up.

I also noticed an issue with posts containing high ASCII (e.g. hex A0, 
which is a non-breaking space). With everything running under UTF-8 
encoding now, PHP considers these as invalid code sequences when calling 
htmlentities() or htmlspecialchars(), leading to blank lines anywhere 
one is present (e.g. http://news.povray.org/60567d33@news.povray.org has 
these in the blank section of quoted text you see. If you don't see a 
blank section of quoted text, it means we've now fixed it :)

This will likely manifest it as strangeness in other parts of the 
webview since invalid code sequences in names, titles, etc have the 
potential to get turned into blank strings.

There is a workaround for it (ENT_SUBSTITUTE, which looks fugly, or 
ENT_IGNORE (which may have security implications). We'll work out what 
to do and let you know. In the meantime if you spot anything that shows 
this issue other than in message bodies please LMK.

-- Chris

Post a reply to this message