WebmasterWorld Beta Bugs and Comments

Post all of your issues with the new beta here

[incrediBILL]

This thread is for discussing all of the bugs and issues with the new WebmasterWorld beta that's RWD (responsive web design) for mobile using Twitter Bootstrap.
See this thread for more details: [webmasterworld.com...]

Note that only WebmasterWorld registered members are allowed into the beta site.
It's currently not viewable if you're not logged in or by search engines.

So login! :)

The beta site location is here: [webmasterworld.com...]

Your current user name and password are all you need, it's the same data, just a different version of WebmasterWorld's layout.

[Fotiman]

Yeah, again, that "top" link has been broken since the new site launched. It's something that has a lot of visibility, so I'm surprised it hasn't been fixed yet. It really would be nice to get that working. :-/

[lucy24]

not working for Yandex browser.

Well, that answers an unrelated question about the Yandex browser. It's webkit ;)

[keyplyr]

It's webkit ;)

it's Opera, so yes some of the framework may be Webkit (or WebCore to be more precise.)

[smallcompany]

You mean, other than manually editing the "site:" operator so it says, for example, "WebmasterWorld.com/apache"?

Yes! Sorry for late reply.

For example, if I'm browsing through Apache forum, I want to enter a phrase to search for and get results for webmasterworld.com/apache/ only. Maybe same search box with the check box that says "Search this forum only?"
Or it could be the whole new search section within some kind of advanced tab/link.

[tangor]

A maintained and well indexed internal site search (as opposed to using Bing, Google or other) is a tremendous (not impossible, just huge) undertaking. Will consume storage landscape three to five times the size of the site itself. Not sure we want our coders working on something like that when there are so many other things still left to do.

Or, conversely, in the Control Panel, allow the member to set their search engine of choice, then code the forum search button to provide THAT result to the member. ... that's just a bit of code and not reinventing the wheel.

[keyplyr]

One more pitch about this...

On a multi-page thread, after editing a post, I am taken to the top of the FIRST page in that thread. This is unintuitive. I must then navigate back to the bottom of the thread, choose the page I posted on, and then down to the post. This is especially frustrating with mobile.

Tested on 5 desktop browsers, 2 mobile browsers.

[lucy24]

On a multi-page thread, after editing a post

This issue predates the current software. So it wasn't newly introduced; it's just something members didn't make enough of a stink about earlier.

Except, that is, for the missing navigation arrows at the top of the page. That detail really is new.

[keyplyr]

I agree, I've been bitching about it for years and I'm not going to take it any more!

[lucy24]

And speaking of bitching for years, I'm going to keep nagging about this because honestly it makes WebmasterWorld look inept and can adversely affect some posts. It also means that the author of the next revision, in 2022 or so, can't say they had no idea it was an issue.

When you use a character outside the 8859-1 (ISO-Latin-1) or 1252 (“Windows-Latin-1”) * character set, it is immediately converted to a decimal entity beginning in &#, as in

πσευδοᐃᓄᒃᓱᒃ

πσευδοᐃᓄᒃᓱᒃ
Before the post is displayed, there is a further, separate process that converts all & ampersands globally into &. This prevents the non-Latin-1 characters from displaying as intended. It would be TRIVIAL** to add a snippet of code that prevented the & expansion from taking place when the & is followed by a # --or, if easier, to let the initial conversion take place and then retro-convert those that have already been changed.


* Browsers are encouraged to interpret 8859-1 as its superset 1252, giving access to characters in 8x and 9x such as curly quotes and ś (happy news for French members whose skin crawls at being obliged to type "oe"). More common characters such as ć and é are in the 8859-1 subset so they’d be available in any case.
** Where “trivial” = “I’ve done it myself”. My log-wrangling functions include ampersand conversion because the end result displays in a browser. I've found by experiment that some changes are easier to do globally and then change back in selected cases. One step forward, two steps back. In any case, it can't possibly be any more complicated than the process which inserts <!-- --> empty comment tags into any ") sequence-- a behavior I was unaware of until I studied the page source for this post. (What would otherwise happen? I'm drawing a blank.)

[Fotiman]

When you use a character outside the 8859-1 (ISO-Latin-1) or 1252 (“Windows-Latin-1”) * character set

Wouldn't it make more sense to just use UTF-8 instead?

[lucy24]

Wouldn't it make more sense to just use UTF-8 instead?

Yes, it would make a hell of a lot more sense, but earlier in the process The Powers That Be made a conscious decision to stick with Latin-1. Maybe in 2022...

One step forward, two steps back.

Where, uhm, er, I actually meant "two steps forward, one step back", though in the specific case of Latin-1 vs. UTF-8 my fingers may have had the right idea after all :(

:: holy ### what is that NEW ANNOUNCEMENT in the corner? I thought they were going to tell us the server had exploded ::

[whitespace]

Ok, cool, so the "NEW ANNOUNCEMENT" is that we're out of Beta! Curious though that the few (what I would call "trivial") display bugs that I've noticed, that have been around for "weeks" and I'm pretty sure have already been mentioned a few pages back, have not yet been fixed...

- Need to check the page layout between widths 768px and 1230px (which incidentally is where the iPad (portrait) falls somewhere in between)... The "search box" in the top right falls onto a second line, pushing the heading down and the "Post Reply", "Post New Topic" and "Forum Options" buttons wrap onto 2 or 3 lines until snapping back.

- Still seeing "Content-type: text/html;charset=ISO-8859-1" in various places. Are you missing an HTTP response header by chance because it sure seems to be lost?

- The "goto top" arrow button does not work in Chrome.

- Needs some pagination at the top (not just at the bottom).

I do like the responsive theme though - nice one! :)

[whitespace]

PHP syntax highlighting does not seem to be quite right? Just posted a CODE block in the following thread and the last half appears to have turned "comment gray" - although I can't immediately see what has triggered it?

https://www.webmasterworld.com/php/4749759.htm#msg4749807 [webmasterworld.com]

Also, editing the post chops two preceding spaces from every line?!

One last thing... I think auto-linking of URLs should at least make the URL into the content of the anchor (as in the above URL - for which I've had to use BBCode!), otherwise you just get a snippet of the domain in square brackets, which is not particularly helpful?!

[lucy24]

PHP syntax highlighting does not seem to be quite right?

It's the // isn't it? The syntax highlighter doesn't understand that // doesn't need a closing tag, as /* does.

[keyplyr]

Closure can be difficult.

[whitespace]

Lol! Ah yes, it does look like it could be the line comments // ...?! (Although that would be a bit of a fundamental issue affecting many languages?)

And I've just noticed that I seem to be unable to scroll the large code block (that has a restricted height) in Safari or Chrome on iPad? (Puffin browser is OK.)