“They broke it again!”
A friend of mine who owns a successful printing business was complaining about some new “features” that were just released for his iPhone.
“I don’t know where my buttons are anymore!” he exclaimed.
“Will you techies please stop breaking stuff? It worked just fine before!”
If you’ve ever experienced something like the conversation above, I’ve got some bad news for ya:
Your WordPress Might Be About to Break!
There’s this new WordPress “feature” that the techie youngsters behind WordPress built.
And they’ll force it upon your existing WordPress site, as soon as this month (Aug 2018)!
This new WordPress “feature” the techies are pushing on us is called, “Gutenberg”, and it might automatically break your WordPress website.
This new feature will be added whether you like it or not. (Though you can opt out through a series of confusing techie steps).
NOTE: If you are a techie or WordPress enthusiast who is comfortable troubleshooting WordPress issues, then you’ll love this feature update. You’ll also have some work to do to fix broken things on your site and to learn about the new layout of WordPress.
If you are a small business owner, you’ll get a headache!
All of your buttons will move.
And maybe worse – you might find your WordPress site broken!
All the things you hate about technology will come to bear.
Again: If you take no action, you might experience this headache.
But thankfully, you can opt out of this madness.
How Small Business Owners Can Eliminate These Headaches
If you are a small business owner, then do this:
- Confirm with your web developer that you have monthly validated backups. (Not sure? Send me a quick email.)
- Have your web developer install & configure the Classic Editor WordPress plugin.
- Work with your web developer to train you in on the new Gutenberg plugin experience on your schedule rather than the WordPress dev team’s schedule.
- Sign up for this FREE “Beginner WordPress Classes by Email” course. It’ll include Gutenberg how-to’s once this new feature is released into WordPress.)
That’s it! Congratulations! You’ve just avoided scores of headaches and thousands of lost dollars!
If you are a Website Amazing member, then my team and I will be by your side during this Gutenberg transition – Zero headaches for you!
Just reply to this email with questions or schedule a quick call with me to make sure you are covered.
More posts from themightymo.com
Today I checked the “proxy” box for a website on Cloudflare, and I got a “ERR_TOO_MANY_REDIRECTS” error when I visited the website. The solution to this issue is simple: Click the “SSL”->”Overview” menu option in Cloudflare. Select the “Full (Strict)” option. Wallah! Done. Is this helpful? UPDATE: I learned that there is also a free…
How to solve Local WP’s “Error in query (1153): Got a packet bigger than ‘max_allowed_packet’ bytes”
I was trying to import a 115MB database via Local WP’s Adminer tool, and I kept getting the following error: After a lot of trial and error, the solution was to: Update the “max_allowed_packet” variable in Local Sites->[site name]->conf->mysql->my.cnf.hbs to max_allowed_packet = 1000M Add/update the “max_allowed_packet” variable in Local Sites->[site name]->conf->php->php.ini.hbs to max_allowed_packet = 1000M…
I was tracking down some strange inode action on a shared hosting provider today and discovered that Divi WordPress theme created 70,000+ unnecessary inodes. As you can see in the inode count in the above screengrab, Divi theme created over 70,000 inodes in a temp folder above the web root. For comparison, this WordPress install,…