Download the PHP package classicpress-research/classic-commerce without Composer

On this page you can find all versions of the php package classicpress-research/classic-commerce. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package classic-commerce

Classic Commerce Build Status

Welcome to the Classic Commerce repository on GitHub. This is a fork of WooCommerce and is still in development.

Classic Commerce is a simple, powerful and independent e-commerce platform. Sell anything with ease.

You can browse the source, look at open issues and keep track of development here.

We recommend all developers follow the Issues and Pull Requests for the latest development updates.

Roadmap

You can follow up on the development cycle by reading our roadmap.

FAQs

Can I install WooCommerce together with Classic Commerce? Yes, you can have both WooCommerce and Classic Commerce installed as plugins. However, you can't have them both activated. You will need to deactivate one before activating the other.

What are the differences between WooCommerce and Classic Commerce? Classic Commerce is a fork of WooCommerce with all the WooCommerce Services and Jetpack integrations removed. This means there will be no "nags" or "upsells" at any stage when you are using Classic Commerce. You won't find any plugins or products that are promoted or pushed in any way.

Can I import my products and settings from WooCommerce to Classic Commerce? There is no need to import anything when changing from WooCommerce to Classic Commerce. They share all the same classes and hooks so your existing WooCommerce records will be recognised by Classic Commerce and immediately available.

What version of WooCommerce is Classic Commerce based on? Classic Commerce is a fork of WooCommerce 3.5.3.

What plugins work with Classic Commerce? All of the extensions compatible with WooCommerce 3.5.3 should still be usable, provided they do not rely on Jetpack or WooCommerce Services. However, we strongly recommend that you test and monitor any extensions or plugins that you may need to provide extra functionality.

How do I switch over from using WooCommerce to using Classic Commerce? Is it safe to uninstall WooCommerce? To try out Classic Commerce you can manually install it as a plugin. Make sure you deactivate WooCommerce before activating Classic Commerce. If you want to uninstall WooCommerce completely you can do so safely, but we recommend you take a full backup of your site first. Note that deactivating and deleting WooCommerce normally only removes the plugin and its files; the settings, orders, products, pages, etc are retained in the database. However, there is a possibility that a setting in your site’s wp-config file may over-ride this, so it is worth checking to make sure the following condition has not been included anywhere in that file: define( 'WC_REMOVE_ALL_DATA', true);

Documentation

Reporting Security Issues

To disclose a security issue to our team. ([email protected])

Support

This repository is most suitable for development but can also be used for support. We will add a support tag to your issue. However, this might take a little longer to get a response. You can also use the dedicated support area on the ClassicPress community forum.

Contributing to Classic Commerce

If you have a patch or have stumbled upon an issue with Classic Commerce core, you can contribute this back to the code. Please read our contributor guidelines for more information about how you can do this.

All versions of classic-commerce with dependencies

PHP Build Version
Package Version
Requires composer/installers Version ~1.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package classicpress-research/classic-commerce contains the following files

Loading the files please wait ....