2.0 suggestion:
How default extensions are deployed: a different mechanism for obtaining and installing the core default extensions should be consider for the 2.0 versions.
Examples of current issues:
In the case of extensions like FedEx, Stripe, etc. the APIs can have changes enacted by the companies that render the current version non-functioning.
Although we all like to think our coding is infallible, at times it is not and there needs to be a fix to an existing extension, again the current default version is non-functioning.
Issues:
Default versions within the Admin panel have no easy way to update to a working version. Having to wait until a new version of AbanteCart is released may not be quick enough or Admin may not wish to update at the moment.
Expecting novice users to understand how to pick a code line from GitHub and fix and existing file is often overwhelming.
Expecting AbanteCart users to always update to the latest cart version to get a working default extension is also overreaching.
Proposed Solution:
Core extensions deployed and available within the marketplace with a free price still. Also consider having updated API versions (FedEx, Stripe) the work for several AbanteCart versions. Perhaps a core/default section in the marketplace?
Thanks for reading, and hopefully considering a different way of handling default extensions.
Lee
