The best way to mess something up is to try fixing a problem that doesn’t exist. From 400 error to bug to things getting awry, how I ended up giving another chance to this SiteGround tool…
This should have been the part 13 of a never-ending mini-series, namely "SiteGround New Client Area and Site Tools". However, I am tired of the many issues with this migration and a more informative title was necessary. Besides, I wanted to keep this unlucky number for the last post on this disastrous Switch!
Given the number of brute force attacks that my security plugin blocks, I thought it was another fairy tale by SiteGround. However, when I became a victim of this system, I started to believe that it was probably not a fabricated story. Two questions remain. Why me? Why now?
At this rate, I don’t think that I will need much effort to prove Hristo wrong. I haven’t even started exploring Site Tools; yet, I have already many issues with SiteGround new control panel. Unbelievable or not, even the tools that were great before (the migration) are no more functioning. The other side of the coin is that I will not run out of material for my blog.
Nope this post will not be about SiteGround New Client Area and Site Tools. Why such a misleading title then? Read on to find out; you may even want to consider reading the previous episode of this never-ending mini-series.
Back in the day, I wrote,
In my case, SiteGround takes (good) care of WordPress core updates (both minor and major releases). This was before the migration to Site Tools, of course. I thought that SiteGround successfully migrated my account. I came around since!
Third time lucky! There is no doubt (this time); after fifteen months, the long awaited and dreaded shift to SiteGround new control panel is finally here. The decisive moment is scheduled for Tuesday, January 12, 2021.
One of the idea circulating about the GDPR is that it requires consent for all types of data processing. Is this true or just a myth? Specifically, what should I do to make my WordPress comment form GDPR-compliant?