Skip to content

Latest commit

 

History

History
267 lines (202 loc) · 12.5 KB

products.md

File metadata and controls

267 lines (202 loc) · 12.5 KB

Products

Creating Products

One of the very few abilities of the admin panel is to create products. It should be straightforward enough, so not detailing that part here.

However if you need to create products from code, here are some examples:

Minimal Product

use Vanilo\Product\Models\Product;

// A product must have at least a name and an SKU:
$product = Product::create([
    'name' => 'Dell Latitude E7240 Laptop',
    'sku'  => 'DLL-74237'
]);

echo $product->name;
// "Dell Latitude E7240 Laptop"

echo $product->slug;
// "dell-latitude-e7240-laptop"

The slugs are generated using the Eloquent-Sluggable library.

All Product Fields

Product::create([
    'name'             => 'Maxi Baxi 2000',
    'sku'              => 'MXB-2000',
    'stock'            => 123.4567,
    'price'            => 1999.95,
    'original_price'   => 2499.95,
    'weight'           => 1.3,
    'width'            => 27,
    'height'           => 21,
    'length'           => 60,
    'slug'             => 'maxi-baxi-2000',
    'excerpt'          => 'Maxi Baxi 2000 is the THING you always have dreamt of',
    'description'      => 'Maxi Baxi 2000 makes your dreams come true. See: https://youtu.be/5RKM_VLEbOc',
    'state'            => 'active',
    'meta_keywords'    => 'maxi, baxi, dreams',
    'meta_description' => 'The THING you always have dreamt of'
]);

Fields

Name Type Notes
id autoinc
name string Required
sku string Required
slug string Nullable, default value is auto generated by Eloquent-Sluggable using product name
stock decimal(15,4) Default value is 0
price decimal(15,4) Nullable
original_price decimal(15,4) Nullable
weight decimal(15,4) Nullable
width decimal(15,4) Nullable
height decimal(15,4) Nullable
length decimal(15,4) Nullable
excerpt (aka "short description") string Nullable
description string Nullable
state ProductState See product state section for detailed info
ext_title string(511) Nullable, see product title section for detailed info
meta_keywords text Nullable
meta_description text Nullable

Product Title

Product title is either the ext_title field's value or the name if ext_title is empty.

$product = Product::create([
    'name' => 'I am a product',
    'sku'  => 'N1'
]);
echo $product->title();
// "I am a product"

$product->ext_title = 'I am a product with attitudes';

echo $product->title();
// "I am a product with attitudes"

// It can be accessed as property as well:
echo $product->title;
// "I am a product with attitudes"

Product Stock

$product = Product::create([
    'name' => 'Yet Another Product',
    'sku'  => 'YAP',
]);

echo $product->stock;
// 0

echo ($product->isOnStock() ? 'On Stock' : 'Not on Stock');
// "Not on Stock"

$product->stock = 34;

echo ($product->isOnStock() ? 'On Stock' : 'Not on Stock');
// "On Stock"

Product State

Product state is an enum.

use Vanilo\Product\Models\Product;
use Vanilo\Product\Models\ProductState;

// Supported product states out of the box:
print_r(ProductState::values());
//[
//    "draft",
//    "inactive",
//    "active",
//    "unavailable",
//    "retired",
//]

$product = new Product();

// Product's state field is an enum:
echo get_class($product->state);
// "Vanilo\Product\Models\ProductState"

// Default value is draft:
echo $product->state->value();
// "draft"

// State can be set via scalar:
$product->state = 'inactive';

// State can be set via enum object:
$product->state = ProductState::INACTIVE();

// Products also have an 'isActive()' method:
echo $product->isActive();
// false

// Alternatively, this can be accessed as property too:
echo $product->is_active;
// false

// The isActive()/is_active flag is actually obtained from the state:
$product->state = ProductState::ACTIVE;
echo $product->isActive();
// true

For extending the product model and the product state enum, refer to the models and enums sections, respectively.

Meanings of Product States

You may wonder, what do these product states represent, why not just go with an is_active flag?

The answer is that in many ecommerce businesses products may go through different lifecycle stages, which need slightly different handling. Vanilo doesn't enforce any workflow for this, but here's the interpretation of the built-in states, and how they can possibly be handled:

State Meaning Common way of handling the state
draft The product data is incomplete Never display it on the StoreFront, do not allow it in any transaction, but allow editing in Admin
inactive The product data is complete but has not been published yet Hide from the StoreFront, eventually allow in transactions; eg. backorders, early closed-group sales, etc
active The product is active Make it available everywhere
unavailable The product is temporarily unavailable; due to supplier issues, legal reasons, quality problems, production blockages or any other reason that prevents the product from being ordered and shipped Display it on the StoreFront, but disallow new orders
retired The product is permanently unavailable and will never come back to the product range Do not list it on the StoreFront, but allow opening it when directly accessing its product link. Disallow new orders.

Product Images

Refer to the Modules vs. Framework page for understanding the difference between the two approaches.

Product Module Only - Without Framework

In case you're using the standalone product module only, then there's no product image support by default.

The contracts package defines the Buyable interface which extends the HasImages interface that has 6 image related methods:

  1. hasImage(): bool
  2. imageCount(): int (since v2.1)
  3. getThumbnailUrl(): ?string
  4. getThumbnailUrls(): Collection (since v2.1)
  5. getImageUrl(string $variant = ''): ?string
  6. getImageUrls(string $variant = ''): Collection (since v2.1)

The support package offers 2 traits for implementing the image related functionality of the Buyable interface:

  • BuyableNoImage: "Null image" trait for products that don't actually have images
  • HasImagesFromMediaLibrary: adapter for using images with Spatie's Laravel Media Library

BuyableImageSpatieV7 and BuyableImageSpatieV8 traits are deprecated as of Vanilo v2.1, please use the HasImagesFromMediaLibrary trait instead

In case you want to compose your own product model with Spatie image support:

namespace App;

use Spatie\MediaLibrary\HasMedia;
use Spatie\MediaLibrary\InteractsWithMedia;
use Vanilo\Contracts\Buyable;
use Vanilo\Product\Models\Product as BaseProduct;
use Vanilo\Support\Traits\BuyableModel;
use Vanilo\Support\Traits\HasImagesFromMediaLibrary;

class Product extends BaseProduct implements Buyable, HasMedia
{
    use BuyableModel; // Implements Buyable methods for common Eloquent models
    use HasImagesFromMediaLibrary; // Implements Buyable's image methods using Spatie Media Library
    use InteractsWithMedia; // Spatie package's default trait
}

It is also possible to add your very own implementation of these methods. The traits from the support package provide a convenient and common default implementation.

With The Framework

If you're using the Vanilo Framework (and not just the product module), it already ships with an extended product model (Vanilo\Framework\Models\Product) with image support via Spatie Media Library.

Refer to the Spatie Media Library Documentation, to discover all the possibilities.

Add Multiple Product Images

// Example: in a controller action
public function store(Request $request)
{
    $product = Product::create();
    
    if (!empty($request->files->filter('images'))) {
        $product->addMultipleMediaFromRequest(['images'])->each(function ($fileAdder) {
            $fileAdder->toMediaCollection();
        });
    }    
}

Define Image Variants

For more details about Vanilo Image handling, refer to the Handling Images section of this Documentation.