I gotta tell ya, this WordPress software, for all I’ve commiserated with other blogger friends of mine about certain decidedly unlikeable aspects of it, is one hell of a piece of blogware. Remember how last night I mentioned, in the throes of exhaustion and eyeball-ache, that I’d need to find a way to offer a Desktop/Mobile choice since this new-to-me theme I’m using was utter shite when viewed in my Android browser?
WELL. Easy-peasy lemon-squeezy: all’s I had to do was install a theme-switcher plugin—of which there are dozens available out there, free of charge—capable of detecting what platform the site is being viewed in and then automagickally switching back to the old theme I’d been using for years for any sail-foam OS so as to display the site to much better advantage, albeit sacrificing some of the newer theme’s functionality. Tested it on my own phone, works like a charm, no glitches, no hassles. Amazing thing, this modern world we live in, innit?
And to think, before you know it it’s gonna be time for the Halloween à la Coop theme, then Scrooge Picard. Oh, the fun we shall have…
- Entries
Looks fine to me, and the better half also reads and says she likes it, so you have a winner.
Also checked on my phone and it works just like always.
Note: It’s a bit hard to see the “post comment” button. Maybe change the shade of the text…
It’s much easier to read once you’ve logged in. Even before you log in, it’s OK±, but after login – far better.
I did notice it was kinda tough to make out myself when I was posting my test comment, but GOD, finding what to change and where to change it? Sheesh. Here’s just PART of the code controlling the “Submit” button:
“input[type=”submit”], .button, div#infinite-handle span {
display: inline-block;
zoom: 1; /* zoom and *display = ie7 hack for display:inline-block */
*display: inline;
vertical-align: baseline;
margin: 0 2px;
outline: none;
cursor: pointer;
text-align: center;
text-decoration: none;
padding: .3em 1em .35em;
text-shadow: 0 1px 1px rgba(0,0,0,.3);
-webkit-border-radius: .25em;
-moz-border-radius: .25em;
border-radius: .25em;
-webkit-box-shadow: 0 1px 2px rgba(0,0,0,.2);
-moz-box-shadow: 0 1px 2px rgba(0,0,0,.2);
box-shadow: 0 1px 2px rgba(0,0,0,.2);
color: #505050;
border: solid 1px #b7b7b7;
background: #fff;
background: -webkit-gradient(linear, left top, left bottom, from(#fff), to(#ededed));
background: -moz-linear-gradient(top, #fff, #ededed);
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=’#ffffff’, endColorstr=’#ededed’);”
The various colors are those letters and numbers following each “#” symbol, RGB code to be specific. Being gradients, it couldn’t possibly be just black text on a colored background, oh no. And like I said, that there is just part of the submit-button CSS…of THREE. But what the heck, I’ll have a go at some point. It’ll get to bugging me and I won’t be able to stop myself. 😉
Heh, well I know where it is so no problema. Just thinking about someone less familiar with the sight.
Just checked, and the “Subscribe” option above the comment box has the same dang problem. Put in an email to the WP hoping to get hold of either the theme developer or my old friend and blog-colleague Mark Jaquith, one of the original designers/coders of the WP software and a really good guy. He helped me out quite a bit back in the day, even wrote the javascript for me to run Muir’s DBD strip here. Hopefully he’s still kicking around out there someplace where he can be reached; if Jaquith can’t fix it, then it simply can’t be fixed.
Can’t see the sidebars at all on my android tablet now, sorry to say, old buddy.
Scroll down and you should. Way, waaay down. How you doin’ these days, old friend? Glad to hear from ya.
I should say, it oughta work if it switched you back to the old theme. On my Android phone, the new theme put the sidebars on top of the content box, which just sucked. The layout was fucked eight ways to Sunday, really. Maybe the theme switcher dealio ain’t working right on tablets. I’ll look into it and get back to ya, Mish.
I can’t see the sidebars on my iphone, but then I never could and never thought about it. It looks the same on the phone as it always did.
I rarely use the phone for this stuff however.
Well dang: just checked my phone again, and now the sidebars are NOT showing up for me either. Oh well, it’s still better than having to scroll down through all that to get to the posts, I guess.
Hinky, as they said in one of the movies, The Fugitive IIRC.
Nope, no joy. Still, I mainly do my reading on the PC.
Doing OK, thanks, hope you’re doing well too, my fellow OG’er!
Another thing to add to your “To Do” list, Mike 🙂
The emoji list gets cut off at the bottom by the next post such that you can’t select a “thumbs up”
Oh yeah? Shows a scroll bar on the right-hand side of the box for me, so the thumbs-up, the “racist” OK sign, etc are all still available.
Now for some reason a little bit shows up, but it’s clearly cutoff for me, picture attached.
This is with it scrolled all the way to show the bottom.
I’ll try it with another browser and report back…
Same thing with MS edge and Brave.
Also, how much is cutoff depend on which post you are trying to give the thumbs up (or in the case of my own personal downvoter the “rolling on the floor laughing” emoji)
So the pic I posted has a bit of the bottom row showing which depends on which post you select.
Hrm. My best guess it’s a Windoze thing, maybe. I’m on Brave myself, but the Mac version. I think the individual-post boxes have a “float” CSS tag in ’em, which places them over everything else in the Z axis. Windoze handles several CSS positioning properties in its own special way; I do know that there’s a shit-ton of Windoze-specific fixes in the theme’s stylesheet. Most stylesheets do that nowadays, beginning way back when Win7 came out.
It’s not a biggy, just thought I’d let you know. I’m familiar with several software packages and how they place windows but not wordpress. There are properties for windows in what we use (VB, C) that determine it’s location and if it is in the front. If more than one gets the “front” position setting, it’s the last one called/refreshed that ends up there. I’ll have to start studying the WP stuff in order to be of some use in the future.
You’re probably right, the mac system is probably treating it differently.
The problem wasn’t there before the change.