We sighted ProcessWire in late 2013. We were hunting for a lightweight, flexible CMS to build websites. But it wasn't until early 2014 that we started seriously experimenting with ProcessWire. There's a background to this.
We had enough headaches with the popular CMSs we’d grown with. We started with Mambo, Joomla’s precursor, way back in 2003. In 2005, we explored both Drupal and WordPress and added these to our arsenal while cruising with Joomla.
The thinking then was that we needed different horses for different courses. 3 CMSs added more flexibility than just one. And so life went on for several years.
The roadmap for it wasn’t clear. New versions were out of step with plugins. Clients had a tough time getting their heads around the system. What's more, we were convinced that its ecosystem was built for developers to make money, not for clients to save it.
Besides, WordPress could do whatever Joomla did, and a lot more easily. So did we need to carry an extra CMS and its headaches with us?
It was not the initial build with all the bells and whistles that really mattered.
The real issue was that the software upgrades virtually once a week. Vulnerabilities, malware, security issues are magnets with WordPress, if you don’t upgrade. Most clients don’t upgrade till mishap hits them in the form of a lock down by the host, by a hacker, or a malware detection.
Then we get called in. By that time, version 2.8 has become 4.x. Upgrades are tricky. The plugins, the themes and the core become problems.
We recently had an issue with one site where the auto upgrade was on. The client called up one day and said his portfolio wasn’t working. We went in to check and found that the auto-upgrade had changed some of the earlier code.
And other times, we found that the plugins had upgraded to accommodate new stuff and that had to re-styled. Sometimes, the plugins even went from free to premium.
The theme mostly breaks. All this takes a lot of time to figure out. Everyone believes that it should not take that much time given the auto-upgrade feature in WP. Really? Because auto-upgrade works 98% of the time. It’s the 2% that you need to take care of. And that’s messy.
Viewed from a developer’s point of view, WordPress is a boon. The client has to come back to you, sooner rather than later. In the long run, the maintenance costs of running WordPress really gets to clients. Plus, the headache of managing and troubleshooting WordPress eats into Developers.
All this makes you as the agency want to tear your hair.
And this is what we discovered with it.
fixmy.pw fixes ProcessWire CMS issues for developers and web entrepreneurs. Small fixes and large, scalable applications and company website builds , work overflows and outsourcing opportunities accepted gleefully.
I have worked with Pigtail Pundits for a long time because, to put it simply, they do such terrific work. Over the years, Unni has consistently provided outstanding creative, strong programming and prompt response to my projects large and small. It has been a delightful and rewarding collaboration which I look forward to continuing for a long, long time.