An simple app to manage the products in a catalog (portfolio for example)
[under development …]
Requirements
Django 1.11
django-mptt 0.8.7
Pillow 4.2.1
django-extensions 1.9.1
Quick start
Add “product_catalog” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [ ... 'product_catalog', 'mptt', 'django_extensions', ]Include the product_catalog URLconf in your project urls.py like this:
url(r'^catalog/', include('product_catalog.urls'))Run python manage.py migrate to create the product_catalog models.
Start the development server and visit http://127.0.0.1:8000/admin/ to create a product / categories (you’ll need the Admin app enabled).
Visit http://127.0.0.1:8000/catalog/ .
Optional
if you want to use front-end product management, you must add product_catalog.context_processors.product_front_management to the context_processors:
TEMPLATES = [
{
[...]
'OPTIONS': {
'context_processors': [
[...]
'product_catalog.context_processors.product_front_management'
],
},
},
]
Settings parameters
- PRODUCT_CATALOG_PAGINATION
Default value: 10 Integer used to paginate the products.
- PRODUCT_CATALOG_PRODUCT_BASE_MODEL
Default value: ‘product_catalog.models.product_abstract.AbstractProduct’ String defining the base model path for the Entry model.
- PRODUCT_CATALOG_UPLOAD_TO
Default value: ‘uploads/product_catalog/%Y/%m/%d/’ Path to upload image
# Add / Update / Delete on front settings
- PRODUCT_CATALOG_FRONT_MANAGEMENT
Default value: True If ‘True’ allow to manage (create/update/delete) products in front. False to deactivate
PRODUCT_CATALOG_PERMISSION_OPTIONS_SUPERUSER = 0
PRODUCT_CATALOG_PERMISSION_OPTIONS_STAFF = 1
PRODUCT_CATALOG_PERMISSION_OPTIONS_OWNER = 2
- PRODUCT_CATALOG_ACCESS_PERMISSION
Default value: PRODUCT_CATALOG_PERMISSION_OPTIONS_OWNER
- PRODUCT_CATALOG_FORM_FIELDS
Default value: [‘title’, ‘status’, ‘excerpt’, ‘content’, ‘categories’, ‘image’] list of available fields in update and create product form
- PRODUCT_CATALOG_FORM_UPDATE_FIELDS
Default value: FORM_FIELDS list of available fields in update product form
- PRODUCT_CATALOG_FORM_CREATE_FIELDS
Default value: FORM_FIELDS list of available fields in create product form
Metadata
Release files for django-product-catalog 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-product-catalog-0.1.0.tar.gz | 19.4 kB | Without provenance | Details for django-product-catalog-0.1.0.tar.gz |
Release files / django-product-catalog-0.1.0.tar.gz
| Download URL | django-product-catalog-0.1.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef46c78aae88da49ac1ee71622587f5f980d096325ecff3b4521980c9f559efc
|
|
BLAKE2b-256 checksum How to use checksums |
de8ae12184c3c677c354df90ce7f44b4c3465f63d20ad618dbd7d7158324fe1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-product-catalog 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.