“Why isn’t plugin X part of the Zen Cart core?” is a question that comes up frequently. Although the reasons are complicated and varied, here are some common explanations:
The functionality is not universally needed
Although a specific modification may seem vital to you, many people are successfully running online stores without it. Such a modification would be rejected for inclusion into the core for that reason.
The functionality is OS dependent
A plugin like Backup MySQL requires extensive logic to check various OS-specific settings. This is difficult to maintain and subject to change outside the release schedule for Zen Cart, so it’s not a candidate for inclusion into the core. A similar logic applies to URL rewriting plugins, which are often tied to a particular web server such as Apache.
The plugin uses a third party API
The reason that the USPS shipping module is no longer bundled with Zen Cart is that it changes on a schedule set by USPS, not Zen Cart. Thus, any particular release of Zen Cart which included USPS could be shipping an obsolete version of the software.
For this reason, USPS and UPS functionality is now provided by plugins.
Desire to keep the core small
The smaller Zen Cart is, the easier it is to maintain, for both the developers on the core team and for individual store owners. For this reason, even very powerful and popular plugins are often rejected for inclusion into the core.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.