Topic: More site bugs

I've posted before about parts of regular reviews not posting. If you copy and paste even one sentence, the rest won't show up. Here's my latest example with the review I just left jp lundrstom. I've message Sol about it too.

Here's my review (122 words)

I've been waiting for this! It's a really good and fast-paced re-write.

I found two commas that are not needed and one little sentence that needs fixing that I'll put at the end of this review because if I put it here, the rest won't show up.

Really good description of the doped up feeling.

I lied--two

“Silk kimono—I love it!”<<Who said this. Needs a tag. Or if it's Roger (which I think it is), let him caress the material.

“This is bad—the pills never did this before.” Mel kept losing her balance. They stopped for coffee again. “I have to pee.”<<Not sure if Mel is speaking in both places.

Here's what actually posted!
62 words
I've been waiting for this! It's a really good and fast-paced re-write.

I found two commas that are not needed and one little sentence that needs fixing that I'll put at the end of this review because if I put it here, the rest won't show up.

Really good description of the doped up feeling.

I lied--two

“Silk kimono—I love it!”

2 (edited by Tom Oldman 2015-10-03 22:21:11)

Re: More site bugs

Janet:

Try making the same comment WITHOUT the double angle-braces. This is because HTML interpreters "see" the angles as a precursor to HTML commands and try to interpret it. Since there are two, both facing the same way, the interpreter thinks they are nested and tries to find the ending angle-brackets facing the other way. Since it didn't find them, it tossed the remainder of your comment on the floor.

I've had this happen to me also. Don't use "< - -" either, because that can be a comment. I suggest using "[" and "]" to bracket your question.

~Tom

Re: More site bugs

Thanks, Tom. I was using them like an arrow the way I used to on the old site. Computer speak didn't translate!

Re: More site bugs

BUT the software that accepts the review should turn those double-brokets into the appropriate ampersand-codes (character entities).  This is a long-standing bug, going back to the old site.  NOTE: bugs in chararcter interpretation, whether HTML or encodings of Unicode, are a fertile source of security problems..

Re: More site bugs

Tom Oldman wrote:

Janet:

Try making the same comment WITHOUT the double angle-braces. This is because HTML interpreters "see" the angles as a precursor to HTML commands and try to interpret it. Since there are two, both facing the same way, the interpreter thinks they are nested and tries to find the ending angle-brackets facing the other way. Since it didn't find them, it tossed the remainder of your comment on the floor.

I've had this happen to me also. Don't use "< - -" either, because that can be a comment. I suggest using "[" and "]" to bracket your question.

It's easy enough to remember never use any brackets other than ordinary parentheses on a site that is designed for ordinary, not technical, writing. Square brackets "[" and "]" around BBcode (like b ... /b and  i ... /i) here, for example, changes text from ordinary to emphasized bold or italics.

6 (edited by Tom Oldman 2015-10-04 14:21:51)

Re: More site bugs

I have never had square brackets do anything in any forum/review I've given. In fact, I usually quote the sentence fully, using [xxx]  to indicate the error and (yyy) to indicate the proper word. In this manner: "I see [your] (you're) happy now."

Works every time - even here on this site.

~Tom

Re: More site bugs

Tom Oldman wrote:

I have never had square brackets do anything in any forum/review I've given. In fact, I usually quote the sentence fully, using [xxx]  to indicate the error and (yyy) to indicate the proper word. In this manner: "I see [your] (you're) happy now."

Works every time - even here on this site.

Yes, there are no BBcodes available for review, but there are such, like those enclosed by square brackets, in forums like this one. You have it right that writing, or accidentally importing from reviewed content, brackets or other code signals causes problems, and my suggestion was to avoid those problems for the machine or for the poor reviewed writer who must interpret a reviewer's personal code language which is never obvious.

Re: More site bugs

I just entered an inline review for Don Chambers's Mysterious Ways.  I was told that I had entered 96 comments.  Now, I'm prolix and sometimes outright logorrheaic, but ninety-six is a lot.  I went back and checked; there were 28 comments.  It's not as though we're paid by the comment, but it would be nice to have an accurate count.

Re: More site bugs

njc, did the site seem sluggish while you were entering comments? Hammering the submit button when the site is taking too long to save the comments can cause the count to go way up. Double and triple-clicking is also very therapeutic. :-)

10

Re: More site bugs

So problem one is caused by problem two?

If you want performance in a computer system, you must design for it.