Download the PHP package sulu/sulu-sales without Composer

On this page you can find all versions of the php package sulu/sulu-sales. 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 sulu-sales

sulu-sales Build Status

Configuration

The following description contains the default configuration for the different sales bundles.

SuluSalesCoreBundle

SuluSalesOrderBundle

Confirmation emails are only sent, when using CartManager for creating orders.

You also need to tell doctrine, how to resolve the target entities:

Pdf templates dynamically

The dynamically pdf template can be configured easily. That way it is possible to dynamically change the look of the pdf generated from a given order object. To add even more flexibility it is possible to configure the dynamically_base template which is the template, that will be extended by dynamically. Like: dynamically extends dynamically_base.

Since there are defaults specified and default templates exist in the bundle, it is not strictly necessary to configure those parameters.

Pdf response type

The way the order bundle reacts on http requests that return a pdf. It is possible to configure the response so that, for example, it is returned as inline so that the pdf file would be shown in a new tab, or as attachment. As an attachment it would start a download without opening the file in the browser.

These configurations can be set in the parameters.yml-file of your application under the key:

The bundle-sided configuration for this key defaults to inline.

Pdf naming prefixes

The naming prefixes, that can be configured are : pdf_order_confirmation_name_prefix and pdf_order_dynamically_name_prefix. That way it is easily configurable how the returned file is named. So if a dynamic template is rendered, the pdf_order_dynamically_name_prefix will be used and suffixed with the order number. Applying the same logic, the filename for the confirmation pdf is generated.

If not configured, the default values are applied. Those are like shown in the example config above.

Routing

The routing of the Bundle depends on the routing files that live in the respective Resources/config/routing directories.

Those are, grouped by bundle:

It is also important to know, that the routing for tests is configured separately. (Check the Tests/ directory)

How to run tests

The following command is going to run tests for all sales bundles:

Documentation

Extend Sales Order

You can use sulu persistence to extend the Order entity and repository.

Events

The following events are triggered by the system:

Constant Parameter Triggered Parameters
SalesOrderEvents:StatusChanged sulu_sales_order.events.status_changed Triggered when the status of an order changes. SuluSalesOrderStatusChangeEvent

All versions of sulu-sales with dependencies

PHP Build Version
Package Version
Requires php Version >=5.4
doctrine/orm Version ~2.5
willdurand/hateoas-bundle Version >=0.3 <2.0
oro/doctrine-extensions Version 1.0.*
symfony-cmf/routing-bundle Version 1.2.*
sulu/sulu Version ~1.2
sulu/product-bundle Version 0.17.*
sulu/pricing-bundle Version ~0.5
massive/pdf-bundle Version ~0.1
sulu/contact-extension-bundle Version ~0.6
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 sulu/sulu-sales contains the following files

Loading the files please wait ....