Darth
Forum Replies Created
-
Posts
-
It night be an anomaly but percentage of mobile phone readership of the blog has doubled in the last 2 days. I take it you don’t find zooming in slightly in the browser any help? Craig actually got me to change font sizes while he refreshed the page. This is the font size he picked. Maybe we could enlarge a bit more?
For the small percentage of visitors on extreme high resolution monitors, who find the whitespace at screen edges distracting, one suggestion might be to zoom the page slightly. Ctrl/+ works on most Windows browsers as a shortcut.
It’s because there can only be 5 levels of nested comments including the top. You can always reply to a less indented reply in the thread and make it clear who you are replying to if context requires. We could up this limit but it is not advised.
Thanks for your earlier kind words. All the feedback here is being collected and, after a break, we’ll play around with things on the test system this week. If we can come up with some modifications that Craig likes and help readers having a problem with this site then they will be implemented.
For those especially struggling with the font, be aware that things like noscript etc will block loading of the Google Fonts and a fallback will be used. The actual main font we use is the second most popular web font in the world but I know that doesn’t help for people who hate it 🙂
Or I could just paste it appropriately modified into the site style sheet 🙂
Seriously we’ve had some suggested css sent in already and are open to any suggestions anyone else fancies posting.
It’s a pity WordPress doesn’t support multiple themes/skins to be active at one time. Users could then pick the one they want. WordPress Customizer seems to be moving in that direction and has even more added stuff in upcoming WP 4.5 to allow Admins to play with alternative themes without making them live. I do wonder if an eventual goal of multiple available themes is at the back of their minds.
Another bit of feedback we’re looking for. Has anyone tried the site on a phone or a tablet and how does it look there? Can you try rotating the phone/tablet to get both portrait and landscape views?
We’ll experiment with fonts on the test site and try out some other tweaks. Also any comment on the “sticky” page header – is that fine or should we unstick it so it scrolls off the top of the page like any other content?
We’ve upped the font size a bit on the blog pages. Font’s themselves are easily changeable and may be tinkered with based on feedback. Colour scheme is based on Craig’s guidance.
Sadly we can’t do much about comment links. If we’d kept 100 top level comments per page, by the time threaded replies were added the page would be ridiculously long. Displaying 100 comments/threads is also fairly cpu intensive.
Why WordPress doesn’t have a comment permalink that doesn’t include the page number is beyond me.
Could you be a bit more specific? What bits are particularly hard to read? Happy to take any suggested changes to make it better.
Even google make it too easy
Funny you should mention TOR. We were all set to test with Cloudflare when a fight broke out between them and TOR developers. Cloudflare served sites had suddenly started blocking TOR or giving never ending captchas. So the test was put on hold. May be resolved by now.
Google search results due to non mobile friendly theme is one of the least of our problems with the theme to be honest and we hope to kill several birds with one (or two) stones. No real birds harmed during the course of the comment 🙂
Glad we were able to sort it out for you.
Anyone else having similar issues then please also clear your cache.
Can you try clearing your cache to see if that helps. Also try opening a new private/incognito browser window and try in that. Does it behave differently or the same?
For a time last night the blog software was incorrectly sending 301 Permanent Redirect on comment page numbers higher than page 1. If your browser cached that response last night it will go straight to the redirected page. We think the problem is fixed now for new accesses and we see the page being retrieved correctly in the logs.
