Earlier this week I blogged about my sudden problems with the Firefox browser - which has been my No 1 browser used with this blog for many years, until a few days ago it suddenly refused to turn up any bigger than approximately the size of a stamp on my computer (laptop) screen.
As other browsers were working as they should, I've not been totally shut out from blogging - but I don't like unsolved mysteries, so it's still been "bugging" me.
Today I had a bit more time on my hands, so had another go at trying to "fix" the Firefox problem, by uninstalling and re-installing that app. Had to seek instructions on how to do that, but it worked. And after re-installing I did get the program up to full size on my screen again, managed to log in, and my basic settings and bookmarks etc seemed to have been saved.
I also managed to log into my blog ok. Or so it seemed - until I ran into a new problem that I can't recall ever having encountered before. Clicking the "Sign in" on the main page of my blog would transfer me straight to the "design" page instead. What it would not do was sign me in to the comment section on the main page... So while I could create new posts, I could not reply to readers' comments! *groan*
So more troubleshooting was required. Probably another hour or so of futile searches, but finally I came across a tip about making sure to remove any "additional" safety settings to do with blocking tracking and cookies etc. And yes! Somewhere in the setting up process I must have allowed some such extras; because after removing a couple of "suspects" of that kind, I suddenly did get back to being logged in properly, including being able to add comments.
I'm writing down this primarily as a reminder for myself, but perhaps this kind of thing may be behind commenting problems occurring for other people on other blogs/browsers as well? So if you feel yourself inexplicably "locked out" from somewhere - the "security" settings on your browser may be one place to look into...
Now I'm just hoping that when I finally click "Publish", this post (written from Firefox) will not only appear on my blog - but also allow comments, both from others and from myself...
PS. Photo from a walk in the cemetery today. Do you get why I chose it for this post?
I knew you were not going to rest until you‘d get to the bottom of this!
ReplyDeleteYou added the picture because of the one yellow tulip being the odd one out, the strange thing among all the reds.
Meike, you are right, of course - on both points... ;)
DeleteEven if I might well decide in the end to switch to primarily using Chrome instead of Firefox, it would have continued to bug me to just leave the "issue" with Ffx unsolved.
I did use to use firefox for many years, however I now use google chrome and you can import your bookmarks too. Have a nice weekend.
ReplyDeleteAmy, I may well end up doing the same but I'd still like to keep Firefox "in working order"...
DeleteIt seems to me that Firefox is now more trouble than it is worth. I had Firefox for many years. Then it messed up kind of like yours. Our computer guy said that he would never use Firefox and it had more problems than any other browser. He said it is very unreliable, So I have Chrome and Edge now.
ReplyDeleteGinny, as far as I can recall, Firefox has worked well for me until now, and it has been my primary browser for this blog from start. So I did not want to just leave the newly arisen problem unsolved. I may end up gradually "moving over" to Chrome, but would prefer to do that with Firefox still in working order, and being able to compare.
Delete