WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It only takes a minute to sign up.
Sign up to join this community
In the phase of developing a new wordpress-based site, I'm evaluating also future pitfalls such as upgrades. Unfortunately, there's no guarantee that a third party plugin will not be discontinued. But that's how it works! There are two possible options:
1) Develop a tight robust site, with no future updates, and cross your fingers (hackers)
2) struggle to keep updated the site, and cross your fingers (what if plugin support is dropped?)
Is there a third option?
3) Relax. You will have to update WP core anyway, so some work is inevitable. If a plugin is discontinued there usually will be an alternative. The most important thing is not to use plugins that require shortcodes in individual posts, because if these are discontinued that will really break your site.
Apart from plugins you will also have to worry about your theme, which may use functions that will be deprecated in future version of WP core.
mytheme_get_template()), so if something happens to get_template(), I only have to fix my functions.php file. If I only use a small subset of a large plugin I try to implement my own as well. Larger plugins tend to be better maintained.
Write the functionality you need in your own plugin(s). Those can be submitted to the official plugin repo and maintained by you, or you can write one off plugins (what I usually do) that are client specific and never hit a public code base. You also need to think about the plugin. Does it only have 500 active users and hasn't been updated in two years? Probably should stay away, regardless of the quality of the plugin right now. Is it contact form 7 or something like that? Go ahead. These are factors in a decision to use third party software in any project, WordPress or no.
Usually I offer some sort of maintenance contract to clients. Sometimes they want to do that, sometimes they just want a fire and forget site. Depending on that and other things, I may set WordPress to fully auto update core and everything else or I may set it to never auto update, or anything in between.
The key is to communicate to your clients/boss what the end product they're getting is and how maintenance will be handled (or won't be) in the future. You need to be upfront that WordPress is evolving software that needs to updated, and to explain that this is in fact a good thing, as it means bugs, security vulnerabilities, etc will addressed in a timely manner. Communicate all the relevant details to your clients/boss and let them make the decision, don't make it for them.
