- Plugin Thoughts Episode 1: Making Your Plugins More Extensible
- Plugin Thoughts Episode Two – Use Filters for Plugin Text
- Plugin Thoughts Episode 3 – Don’t Forget About Core Functions
- Plugin Thoughts Episode 4 – Learn How Core Does It
- Plugin Thoughts Episode 5 – Take Responsibility for Your Products
- Plugin Thoughts Episode 6 – Contribute to the WordPress Codex
- Plugin Thoughts Episode 7 – Remember Core CSS
- Plugin Thoughts Episode 8 – Create Clean Code
- Plugin Thoughts Episode 9 – Write Better Code; Release Better Plugins
I am an avid proponent of developers supporting their products, and supporting them very well. I am also very strongly opposed to those developers and studios that choose to ignore support, or simply refuse to ever take responsibility for issues in their work. These are the kinds of developers and studios that always seem to say “it’s the plugins fault”, “it’s not our problem”. Please don’t be one of those developers or studios and take responsibility for your work, and even step up to the plate and help solve a problem with someone else’s work when they choose to ignore it.
Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.
This episode is mostly about caring about your work and your customers. Have you had experiences where someone refused to acknowledge the problem might actually be with their system?
I couldn’t agree more with Pippin in regards to conflicts with other plugins, one of our most recurring problem.
This said, it’s often faster to simply integrated a workaround in our code than get in touch with other devs. Our users are in a hurry. Fast support is key!
This has got to be one of our most visited pages on our support site:
http://support.wysija.com/knowledgebase/list-of-plugins-that-may-cause-conflict/
I’m not saying you should always get in touch with the other dev to try and solve the problem, just that problems should not always be blamed on the other dev just because it appears that their system causes a conflict with yours. If you can contact the other dev, great, by all means do it, but at least take the time to get an idea of what is actually causing the problem.
For sure.
We do take the time every time.
Internally we say this to ourselves: our plugin has 2 equal parts. Quality of the plugin. And support for it.
Is there meant to be a video here?
It’s audio only, but I just noticed the audio player wasn’t working. It’s fixed now.