Thank you all, I can see some of you really have played most (if not all) of your moves on the beta since made available. Very helpful. I have one more update to make, then will look look at pushing this into production later next week if no further errors present themselves. As a precaution, timeouts maybe suspended for a short period when this happens.
Once that is complete (and bedded in), phase 2 can start, which is the beta.redhotpawn.com domain name will then be reassigned to a new server along with a further build of the RHP code. (The current beta is running on the existing production server in parallel.)
@beatlemaniasaid @mwmiller I'm currently using a Samsung chromebook (the screen is probably a 10-12 inch screen, so not particularly large). The main reason I posted my original post is that this is only happening on the beta and not the normal site, which I'm guessing was not intended (though I could be wrong).
Currently can't explain this! It could be because of a minor version update to a library we use, but right now, I can't reproduce it.
In case you were concerned that this has gone AWOL, I decided to update the whole RHP code base to help the integration with the new blitz code/variant support. Unfortunately, that process took significantly longer than expected!
Another build has now been uploaded. I'm confident no issues were introduced, but there is always potential for problems, of course.
Earlier I stated that the beta should function exactly as the current live version. This is no longer true, as the club pages have had a few tweaks in response to some recent feedback I requested from an active club manager. (Thank you @lstcyr)
Other than the club code, everything should be the same though currently.
@orangutansaid I notice that a forum search returns zilch.
I.e. https://beta.redhotpawn.com/board/search.php?authorname=orangutan just gets me an empty response (probably not such a bad thing, but also yields nothing for other users).