April 2, 2019 at 11:10 am
Title says it all here, but when quoting a post with line breaks in, the line breaks are lost. This actually can easily make the previous quote an unreablemess, depending on it's contents.
I'm not sure how this appears with code inserted, so I'll add some below and quote this afterwards for testing. Random Function on my instance I don't mind sharing:
ALTER FUNCTION [dbo].[ValidatePCode_fn] (@Pcode varchar(8))
RETURNS TABLE AS
RETURN
SELECT @Pcode AS PostCode,
CASE WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][A-z][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9][A-z] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1
ELSE 0 END AS IsValid;
Hopefully that, at least, doesn't look too bad.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
April 2, 2019 at 11:11 am
Title says it all here, but when quoting a post with line breaks in, the line breaks are lost. This actually can easily make the previous quote an unreablemess, depending on it’s contents. I’m not sure how this appears with code inserted, so I’ll add some below and quote this afterwards for testing. Random Function on my instance I don’t mind sharing:
ALTER FUNCTION [dbo].[ValidatePCode_fn] (@Pcode varchar(8))RETURNS TABLE ASRETURN SELECT @Pcode AS PostCode, CASE WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][A-z][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9][A-z] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1 ELSE 0 END AS IsValid;Hopefully that, at least, doesn’t look too bad.
Well the code block went very wrong and the quote box ended prematurely. It looks like "Hopefully that, at least, doesn’t look too bad." is part of this post, however, it is not; it is quoted from my original message.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
April 2, 2019 at 1:42 pm
Title says it all here, but when quoting a post with line breaks in, the line breaks are lost. This actually can easily make the previous quote an unreablemess, depending on it’s contents. I’m not sure how this appears with code inserted, so I’ll add some below and quote this afterwards for testing. Random Function on my instance I don’t mind sharing:
ALTER FUNCTION [dbo].[ValidatePCode_fn] (@Pcode varchar(8))RETURNS TABLE ASRETURN SELECT @Pcode AS PostCode, CASE WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][A-z][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9][A-z] [0-9][A-z][A-z]' THEN 1 WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1 ELSE 0 END AS IsValid;Hopefully that, at least, doesn’t look too bad.
Ditto on Thom's observation.
It would also be nice if the "xxxxx Wrote:" in the quote was actually the site name of the person rather than the post number.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2019 at 3:03 pm
This appears to be working now. The quote items are a permissions issue, as we work on what we allow/don't by non moderators.
April 4, 2019 at 3:15 pm
Title says it all here, but when quoting a post with line breaks in, the line breaks are lost. This actually can easily make the previous quote an unreablemess, depending on it's contents. I'm not sure how this appears with code inserted, so I'll add some below and quote this afterwards for testing. Random Function on my instance I don't mind sharing:
ALTER FUNCTION [dbo].[ValidatePCode_fn] (@Pcode varchar(8))
RETURNS TABLE AS
RETURN
SELECT @Pcode AS PostCode,
CASE WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][A-z][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][A-z][0-9][0-9] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9][A-z] [0-9][A-z][A-z]' THEN 1
WHEN @Pcode LIKE '[A-z][0-9] [0-9][A-z][A-z]' THEN 1
ELSE 0 END AS IsValid;Hopefully that, at least, doesn't look too bad.
Here's hoping Steve. 🙂
Edit: Looks better, but the code sample breaks the quote trail still.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
April 4, 2019 at 4:21 pm
This appears to be working now. The quote items are a permissions issue, as we work on what we allow/don't by non moderators.
Cool... That and the names appear instead of the post number. Thanks folks.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 8, 2019 at 2:08 pm
This is still slightly flaky, but still working.
One thing we were hoping to get less of in the change is quoting. Far too much quoting takes place and creates long threads that aren't helpful. In working on the code, not sure that it's useful to keep repeating old code and perhaps confusing people looking for help.
Most threads are single threaded for a reason and don't need quoting.
April 8, 2019 at 2:43 pm
Understood but the really helpful nature of quoting is that you don't have to go back through the entire thread to see what someone is talking about even if it doesn't seem to be totally related. I will admit that it's become a lazy habit (including myself in that) that's used/abused where it's sometimes not needed but is incredibly helpful when trying to build a (hopefully) better answer. The casual reader may miss that but people writing answers don't.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2019 at 2:51 pm
here is a quote using BBCodes
and another with line breaks:
this one will have a line break
new line and now the ending quote tag
So what exactly was fixed? I really don't get how these tags should be used.
April 10, 2019 at 7:41 pm
The tags surround things. A few examples. This is bold with brackets around b, ending with brackets around /b
For code, you use brackets around code like this
select *
from test
but some of the formats are broken, or they work differently between quoting and initial posting. Styles are complex here, more than I ever wanted to know about, and Windows against other platforms and different browsers is a mess. Supporting them all is, well, a pain. We're working through some of these. Still some cases where things are broken.
I get the quoting item, and there is a bug on how the quote stuff is put in. I thinking quoting, especially multiple people being quoted, is worse now. I get that you use that to craft a response, but I'll also say that it has confused lots of people and cluttered up the ability to read through a thread. What I wish is that everyone deleted the quoted part before you post if it doesn't add to the post. Often someone says "that's great" and it gets quoted ten times. There's not a lot of value in how that displays in the thread.
But that's me. I know others feel differently.
Believe me, I am not thrilled with a few of these bugs. Quoting should have worked better, and we should have tested it more extensively. A lot of that is on me as life and travel and weeks of trying to manage the site AND test things burned me out a bit. I was less diligent near the end in going through my list of 200+ items to check. While things are getting fixed, as of today, I have 104 items open, which is a growing list since we migrated. Maybe 20-30 of those are infrastructure things, so the majority are items you or I have found.
I can only apologize for my lack of testing and validation and hope we get more things fixed soon. I have tagged most of the forum items as high priority.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply