Download the PHP package brille24/customer-options without Composer
On this page you can find all versions of the php package brille24/customer-options. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download brille24/customer-options
More information about brille24/customer-options
Files in brille24/customer-options
Package customer-options
Short Description Adds product customizing to Sylius
License MIT
FAQ
Example:
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 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.
Informations about the package customer-options
Customer Options
With this plugin the customer can add additional info to the product like so:
Installation
-
Run
composer require brille24/sylius-customer-options-plugin. -
Register the Plugin in your
config/bundles.php: -
Add the
config.ymlto your localconfig/packages/_sylius.yaml: -
Add the
routing.ymlto your localconfig/routes.yaml: - Copy the template overrides from the plugin directory
In order to use the customer options, you need to override the product and order item.
-
If you also want default data you need to copy over the
brille24_sylius_customer_options_plugin_fixtures.yamlfile from the package directory and run - Finally, generate migrations, update the database and update the translations:
Things to consider
- Saving files as customer defined values as the values are currently stored as a string in the database
Developing
When developing it is recommended to use git hooks for this just copy the docs/pre-commit to .git/hooks/pre-commit and make it executable. Then you will check your codestyle before committing.
Usage
Documentation on how to use the plugin can be found here.
