January 5, 2016
Protecting yourself against WordPress plugin collisions
WordPress plugin collisions aren't fun What do you do when you have a stable website and then you want to install a new plugin? How do you know that it will all work? That the plugins won't destroy each other? It's not supposed to be that way. They're all running on top of WordPress...
https://youtu.be/Fbv-tae_WAQ
WordPress plugin collisions aren't fun
What do you do when you have a stable website and then you want to install a new plugin? How do you know that it will all work? That the plugins won't destroy each other?
It's not supposed to be that way. They're all running on top of WordPress right? So they should play nice, right? WordPress plugin collisions shouldn't even be a thing, right?
But they are.
And at that point, the frustration and despair sets in.
Thankfully, there is a path forward. A way that you can protect against this frustration.
I reference it in the video above.
Test locally. Run things in an environment you control. Where if things break, you won't have a near heart attack.
You could pay for an additional hosting account. Or sign up with someone who gives you a staging environment.
But the simplest and easiest way to solve this problem is to work locally. And that's why I strongly recommend Desktop Server from my friends at ServerPress.
A story. An insight. A bite-sized way to help.
Get every article directly in your inbox every other day.
I won't send you spam. And I won't sell your name. Unsubscribe at any time.
About the Author
Chris Lema has spent twenty-five years in tech leadership, product development, and coaching. He builds AI-powered tools that help experts package what they know, build authority, and create programs people pay for. He writes about AI, leadership, and motivation.
