I find this unexpected ─ namely, even though my younger brother has been over on Vancouver Island visiting his friend Frank since the afternoon of Monday, I have yet to get to bed early.
Last night's bedtime was 12:12 a.m., but I suppose I am legitimate in blaming the extended difficulties I had with finally getting my website at JustHost to safely upgrade its PHP from version 5.6 to 7.0.
I had thought I had already succeeded in doing the job a few days earlier with a mere two hours' effort at very most, but I since discovered that the website had disappeared ─ there was nothing but a blank white page anytime I tried to access it as a visitor or even through my WordPress administrator login.
It is already the most poorly-visited website of the six I have online (the other five are on one account at HostGator), so the last thing I needed was for absolutely no one to be able to find it because it had essentially ceased to exist.
It took much work, but I was finally able to find out that the culprit was the SEO Video Sitemap & Ranking Plugin the website contained. Once I deleted that non-essential tool, my website suddenly displayed under PHP version 7.0 for all the world to once again see...should anyone, of course, choose to want to.
So yes, that kept me occupied during the latter part of yesterday, along with my blog post here.
But I was to find early this morning that I was still not done with troubles at that very website!
I am presently putting together one of my extremely long posts at that website ─ my posts typically take over two weeks to finish and get published.
And so when I went to log in to my WordPress dashboard, I was taken aback that none of the fields in the login prefilled as they had always done for untold months or even years.
When I did some scurrying about to try and find those credentials, I evidently latched onto the wrong ones.
All it took was one failed attempt, and my Wordfence Security plugin locked me out.
The liars indicate that they will send an E-mail with instructions on how to bypass the block, but even though I submitted two different E-mail addresses, no such response ever arrived.
I found very limited help while researching online, although I did learn that I could access the plugin through my JustHost cPanel, then locate the plugin within my website's database, and then simply rename it. That would allow me to once more log into my website.
I was so annoyed that I renamed the plugin "bollocks."
This did indeed disable Wordfence, and I was able to log into the website's WordPress dashboard.
I then renamed the plugin through cPanel to "wordfence," and got busy with the day's content assignment. That generally takes three hours at the very minimum.
I knew that if I logged out of my website, I would likely run the risk of finding myself still barred from accessing it again. Nevertheless, I gave it a try, knowing that my cPanel was still open and I could just rename the plugin to "bollocks" again.
So I logged out...and immediately I was met with that same Wordfence screen indicating that I had been blocked out.
What was now happening was that I was not being allowed to log out of my website.
This was becoming aggravating beyond my ability to properly describe.
I had read that somehow a plugin called Wordfence Assistant could help with blocking issues, so I downloaded one of them.
As instructed, I then located a button that would allow me to disable the Wordfence firewall.
Please keep in mind that none of this came to me immediately ─ I spent a lot of time researching and mucking about with some 'trial and error.' This even involved renaming the Wordfence plugin to "bollocks" again to deactivate it before I downloaded the Wordfence Assistant plugin.
So I disabled the firewall...and then guess what my next step was instructed to be? ─ How bloody helpful is this?
Now you can rename the Wordfence folder back to the original name and you won’t be locked out. Once Wordfence has been reactivated, disable or adjust the feature of Wordfence that locked you out. Then reactivate the Wordfence firewall by going to the Wordfence options page and checking the box to activate the firewall and hit Save. You can then optionally uninstall the Wordfence Assistant plugin.
What the hell good is saying to "disable or adjust the feature of Wordfence that locked you out" if I have no freakin' idea what feature it was that locked me out?
How stupid can the people be who put these instructions together?
It had been an utter waste of time, and so I just deleted the Wordfence Assistant plugin.
More time was then wasted researching, but no solutions were forthcoming. Meantime, I was considering just doing away entirely with the Wordfence Security plugin to be rid of all of this aggravation.
But one last idea I had was to deactivate and then delete the Wordfence Security plugin, and then install a fresh version.
So I did that, and then logged out of my website...and was again met with the Wordfence notification that I had been blocked out. Yet just as before, I wasn't blocked from my website ─ all I was blocked from doing was logging out of it.
Was I really going to have to do without Wordfence?
More research.
Finally I came across this:
If you are removing Wordfence permanently, or if you want to do a fresh reinstall of Wordfence you can enable the option “Delete Wordfence tables and data on deactivation”. If you then deactivate the plugin, all the Wordfence tables will be deleted. You can then choose to activate Wordfence again to get a fresh installation, or you can choose to delete the plugin.
Apparently just deleting the Wordfence Security plugin did not delete various Wordfence data "tables"; and so when I installed a new version, it simply assumed those already-existing data tables, and I found myself right back in the very same mess.
I couldn't immediately find that option, but I finally did. I checked or ticked the applicable box and then saved or updated my choice.
Then I deactivated Wordfence Security, deleted it, and installed a new version.
Hallelujah ─ I was freed from this ridiculous vexation at long last and could fully log out of my website. I could also log back in with no trouble.
I had been awake since before 4:00 a.m., so I needed to get back to bed. And so I did ─ but at 10:30 a.m. And I was to only manage to nap and remain in bed until 12:30 a.m.
No one can accuse me of sleeping too much.
By the way, my eldest stepson never bothered getting up and going to work today.
We had very light rain overnight and into the early morning, and the day remained overcast until mid-afternoon ─ it is now 3:06 p.m., and I notice some brilliant sunshine out there.
I want to have some exercise out in the backyard tool-shed, so I am going to take a break and do that. And if it is possible, I may sit outside for awhile if that sunshine is more than just an interlude in what will otherwise be an overcast day.
oooooooooooooo
It is now 4:39 p.m., and I've had my exercise and then a meal. However, sunning was out of the equation ─ I never experienced any sunshine when I was outside.
I am wondering if my younger brother is going to be spending a third night on the Island with his friend Frank and Frank's wife Sandra. It would certainly be to my convenience ─ it is quite nice not having to just watch T.V. all evening with my brother because he doesn't know how to operate our T9 Android 8.1 TV Box for himself.
It is also freeing up my mornings, for I generally have to watch two or three hours of T.V. beginning around 10:00 a.m. as a courtesy to my brother.
I wish he had bothered to learn how to use a computer in his past.
I want now to include some information in this post about the health benefits of the fruit of a plant called the Indian gooseberry or amla (Phyllanthus emblica).
Apparently other parts of the plant are also used by herbalists for medicinal purposes, but the specific study that I am including articles about, found that the fruit seemed able to protect against cardiovascular disease by helping the body to manage the levels of blood lipids or fats, thereby preventing these lipids from accumulating and coalescing onto blood vessel walls:
JacksDailyDose.com
NutraIngredients-USA.com
PRNewswire.com
NutritionalOutlook.com
I'm unsure if I have before come across the term dyslipidemia ─ the condition of having excessive or abnormal blood fats.
As far as I know, I do not suffer from this. But then, I do not get medical checkups, despite being 69 years old.
Many people are told by the medical profession that their cholesterol is too high ─ maybe amla extract is the way to go, and not any prescriptions for statins.
To that end, I made two Amazon searches to see what would turn up. The search I made using just the term "amla" is at the top of this post; and a second search using the botanical name Phyllanthus emblica is beneath this post.
To cap off today's post, I have a few more photos that were taken on February 25, 2018 ─ probably in in Udon Thani.
That was the day a niece of my wife got married:
No comments:
Post a Comment