Update on the problems with the old Blogger blog
Thanks for all the suggestions to solve my problem accessing my original blog on Blogger, the one I used until 2007 (read the link if you haven’t seen it and want to know what I’m talking about).
Just to respond to a few things—
I have the newest versions of Firefox and Chrome, so the problem is not that. I found this page last night that describes the problem and offers a supposed remedy. But I have not been able to follow it and do what it says because it’s loaded with inside-baseball-type jargon that I simply do not understand.
I did some more exploring, though, and discovered a few things. It seems that, on Chrome, my cell phone shows the old posts, unlike my desktop. But the format on the phone is a bit screwy, and trying to get to any post that’s not already on the blog’s front page gives me the dread blogrolling redirect again. That also happens if I try include to access comments that way.
On the browser Brave, which I downloaded last night, it’s better than Chrome on the cell phone. Even on my PC I can see the archive lists on Brave, and I can get to those old articles too when I click on them. But sometimes comments don’t show and sometimes they do (I haven’t figured out the pattern for that).
I also discovered that even on Firefox on my PC, if I make sure I add an “s” to “http://” in the URL, it will take me to the old blog and not transform to the blogrolling page. But again, any link to anything that’s not a post that’s showing already on the front page transforms to the blogrolling ad, so I can only read a very limited number of posts.
That’s what happens with the front end of the blog, the part the public sees. No approach I’ve found can get me to the back end that shows anything but the skeleton blog with the four posts. I can’t get to the template on the back end no matter what I do, nor can I can’t get to any of the previous posts or comments from the back end. All that ever shows are those four recent posts. Blogger makes you sign into the blog back end with Google now, which wasn’t the case when I first set up the blog. But after I sign in, it just converts to neoneoneocon.blogspot.com no matter what I do and shows those four posts and no template pathway that I can see.
So for anyone out there who still has an interest in this dilemma, do you have any suggestions on how to get to the real and complete back end instead of this stripped-bare back end? (Hmm, that sounds raunchy.)
The link you provided about blogrolling likely explains why it is happening. How to fix it is still the problem when you cannot access the blog’s settings page.
I found this link … How Can I retrieve an old blogspot account?
https://support.google.com/blogger/thread/2026355?hl=en
which led me to this …
https://too-clever-by-half.blogspot.com/2013/05/identity-crisis.html
One of the steps was trying this …
https://www.blogger.com/forgot.g
What happens with the old blog name AND/OR the old email address.
Of all the sites I visit, yours is the only one indicated as not secure. Are you aware of this?
About front end problems.
Seems I was wrong – default settings do not block the redirect. I just created a fresh Firefox profile, not changing any setting, and finally got the redirect behavior you were complaining about. The easiest way around this is to download the HTTPS Everywhere addon (Control+Shift+A to get to addons page in Firefox). Once installed, it will direct everything to the https resource if available.
The problem of comments not appearing appears to be a separate problem. I spoke too soon yesterday when I said they worked fine. Comments on blog posts before June 28, 2006 seem to be intact. After that, comments are not available on most posts. They may or may not still exist if the pages are accessed through the http protocol, it’s hard to tell since the insecure pages roll over immediately to blogrolling.com.
stu:
My site here at thenewneo has an “https” designation and all the security stuff is in place. I don’t know why you’re getting a “not secure” message, but that isn’t what I get and it doesn’t seem to be what most other people get.
If you’re talking about the Blogger blog, the old site, that’s a whole other story.
I also replied on the earlier thread neo… this is a simple suggestion that might fix your problem (without the copying and pasting links, and editing http:// to https:// I mentioned in the earlier thread comment).
When you go to
https://www.blogger.com/blogger.g?blogID=0000000#usersettings
… and change the seven zeros to your blogID ## (you’ll have to login to your Google account too)
… you might try changing Settings –> Basic –> HTTPS Redirect from “No” to “Yes”.
Who knows. Might be a simple fix.
(Mine is set to “no”, but I don’t have the issue… probably due to the vaguely recalled “thing” Google had blogspot users do many, many years ago.)
Again: you can email me if you need more help.
Make sure you’re going to https://www.thenewneo.com/ and things should be secure. The site doesn’t re-write your request from http to https automagically. Testing the ssl setup via https://www.ssllabs.com/ssltest/analyze.html gives the site an A, tho the site supports TLS 1.0 and 1.1 which it should not since they’re deprecated, but does not support TLS 1.3.
Netcraft says you’re running apache. Bonus, they report no know web trackers deployed here. Nice. 🙂
I have the newest versions of Firefox and Chrome, so the problem is not that.
“Newest” versions of anything, causes loads of problems. There’s a reason why certain pc specialists like to turn off windows automatic updates.
Ymarsakar:
In this case, though, the problem was also present with the older versions. I can’t remember exactly how long ago I discovered it, but it was before I used the versions I have now.