Posts Not Showing UP

Interesting. I just tried to reproduce the error, which I've never had, in a test thread ( www.turns-all-year.com/skiing_snowboardi...ndex.php?topic=32727 ) without success.

Is there a particular way in which the UTF-8 characters need to be entered/a browser configuration for UTF-8 that might matter?

I'm guessing the bug was fixed before you started posting. Thanks Matt for sorting this out and getting it fixed!

Woohoo! Thank you!

Awesome, thanks for the observations all, and for the help getting them patched up Matt. Please continue to post here if you have issues.

I can confirm that the problem seems fixed (or at least reduced).

Several weeks ago I tried to update a link in this old post and had the post eaten:

www.turns-all-year.com/skiing_snowboardi....msg104290#msg104290

I just tried again and my modification was posted successfully.

Good work!

Things are still not all well in the TAY software! There is a major display bug now visible in many older posts, especially all of those which contain 2 or more consecutive spaces. In the case of multiple spaces, every other space is being rendered as a "square box" symbol (on iOS) or as a "black diamond with question mark" (on Mac OS), as are non-ASCII characters like degree signs.

I can see this problem in any browser I use (checked with Chrome, Firefox, and Safari on Max OS X, and also Chrome and Safari on iOS). I have no idea whether other OSes have this issue or not. The problem does not appear to be occurring in new posts made now like this post, but does appear to affect all older posts to some extent.

Basically, this renders unreadable all of my weather and snowfall posts over the last decade, anything where I have posted nicely-formatted telemetry data, and also affects most of my dozens of Rainier TRs which include that day's Rainier NWS rec forecast, which also is formatted using multiple consecutive spaces. Posts by all other users appear to be affected similarly too, if they contain multiple consecutive spaces or non-ASCII characters.

Examples of posts rendered unreadable by this bug:
Mt Rainier Paradise reaches 200" snow depth (2014)
How unusual is the current low PNW snowpack?

I think that this bug appeared recently during whatever fix was implemented to try to solve the disappearing posts issue, but it may have existed before that since the software update which caused the disappearing posts issue, I don't know for sure. But clearly the current state is not an acceptable solution if all older posts with multiple consecutive spaces and formatted columns of data are rendered unreadable by it.

New posts appear to be unaffected by the issue, as multiple spaces appear fine like this:  (there are 2 spaces to the left of this)
Or this:          (there are 10 spaces to the left of this)
Even non-ASCII characters like this degree sign (°) render fine.
Or even a part of the Rainier forecast:
[tt]MOUNT RAINIER RECREATIONAL FORECAST
NATIONAL WEATHER SERVICE SEATTLE WA
415 AM PST WED DEC 17 2014

TEMPERATURE AND WIND FORECASTS FOR SELECTED LOCATIONS.

                       WED    WED    THU    THU    FRI
                            NIGHT         NIGHT

SUMMIT   (14411 FT)      1      1      8      2     -7
                     SW 20  SW 25   W 50  SW 60   W 45

CAMP MUIR(10188 FT)     18     15     19     20     10
                     SW 20  SW 20  SW 25  SW 50   W 35

PARADISE  (5420 FT)     35     29     36     32     33
                      CALM   W  5   W 10   W 10   W 15

LONGMIRE  (2700 FT)     40     33     40     35     39
                      CALM   CALM   CALM   CALM   CALM

++ TEMPERATURES AND WIND FOR THE SUMMIT AND CAMP MUIR ARE AVERAGE
   CONDITIONS EXPECTED IN THE FREE AIR AT THOSE ELEVATIONS.
++ TEMPERATURES FOR PARADISE AND LONGMIRE ARE THE EXPECTED HIGHS AND
   LOWS. WIND IS THE AVERAGE WIND EXPECTED DURING THAT PERIOD.
[/tt]

Even my signature at the bottom of every single post was affected by this bug (it contained 2 pairs of spaces), so as a test I decided to edit it now, by deleting the pairs of spaces and retyping each pair new. The problem in my signature was fixed by this test.

It also appears that older posts can be fixed by modifying and reposting from a saved backup copy, but that is not a reasonable method for fixing hundreds of posts. See the tests I just did in this thread from September, I was able to reply (#2) and post the same data properly, as well as edit my original reply from Sept (#1) to fix the rendering issue:

NWAC telemetry bug/missing data?

So reply #1 now contains both the original data table which is rendered unreadable, as well as the same data table pasted in now which is rendering properly. Truly bizarre.

Even more bizarre, the multiple spaces problem only occurs in most older posts, but not in all of them! The issue with non-ASCII characters like degree signs does appear to occur in all older posts which I have glanced at now.
Examples from 2 TRs earlier this year:
Apr 29 + May 1, 2014, Mt Rainier, Muir to Bridge? (degree signs and Rainier forecast are rendered unreadable)
April 7, 2014, Rainier, Muir to Nisqually Bridge? (degree signs are rendered unreadable, BUT the Rainier forecast looks fine!)

Hopefully this will provide enough info for you to fix this serious problem, Matt and Marcus. Thanks.

Amar, one thing that seems possible is that the character encoding scheme was changed during the backend software upgrade. So your old posts were persisted with a different character encoding than what's being used now to display them.

Or maybe it's just aliens who have been cloaking their spaceships in the lenticulars common to Mt. Rainier and using their superior powers to flip the bits of your posts about their secret Earth base deep inside the mountain.