Hi there,

We noticed that your repo has a medium severity vulnerability:

• Cross-site Scripting (XSS)
• Affected package: jquery <3.0.0-beta1 >2.2.0 || <2.2.0 >1.12.3 || <1.12.0 >=1.4.0

Here is the test report for this repo.
If you’d like to fix this vulnerability, Snyk lets you generate a pull request that recommends the best upgrade path - there’s a link to fix this vulnerability on the test report.

Stay secure :-)
Snyk Community

a small install issue is that migrations wont run.
Because of the ordering of the migration files the users table is created before roles and the FK on users -> roles cant be created

[Illuminate\Database\QueryException]                                                                                                                                                                                              
SQLSTATE[HY000]: General error: 1005 Can't create table 'creuset.#sql-a63_fada5' (errno: 150) (SQL: alter table `users` add constraint users_role_id_foreign foreign key (`role_id`) references `roles` (`id`) on delete cascade)

markdown editor on one side, preview on the other. Post meta etc at the bottom

No need to have the namespace as Creuset - change it back!

CRUD for events

• use Address model for location
• maps on front end
• ical/google calendar download

Run a task to clear all unpaid orders older than a certain age

Implement an attribute structure so products can have properties assigned to them (e.g. lampshade-size: large, medium, small etc). The structure should allow filtering products according to a property, and potentially allow creating variations based on attributes (e.g. creating a small, medium large etc variation of a t-shirt).

Use the terms table for taxonomies. E.g. an attribute might be represented by:

• taxomony: lampshade-size
• term: large

The termables table can then assign the attributes to a given product.

Need create/edit pages and controller methods for these taxonomies

As it stands, the user enters their billing address and proceeds to the checkout. If the address they entered fails the card check there is no easy way for them to go back and fix this.

Devise a method for a user to fix their billing address should it fail. I.e. use the order in the current session to pre-fill the checkout page.

Devise a way of allowing custom templates and assets to be used on the front end without committing them to the repo. Themes should exist as separate packages and be registered via a service provider dependant on a config setting so they can be swapped in/out as required. The app should fall back to the standard templates should an external file not exist.

Maybe sanitize these characters as they conflict with Blade and/or Vue

A basic resource for managing uploaded media showing the model each file was uploaded to along with CRUD operations.

Lightweight markdown highlighting for the post content textarea would be nice. Preferably with browserify

Rather than have many fields in the posts table and just adding to it every time we need a new one, I see two options to get around this:

1. Meta table

This involves having 1 extra table: a metas table with fields metable_id, metable_type, key, value. This would allow us to attach whatever key-value pairs we want to whichever model implements a MetableTrait. This would contain:

public function metas()
{
    return $this->morphMany('Meta', 'metable');
}

...among methods to retrieve, save etc meta records.

This is quite nice as it allows us to limit the number of tables needed and just have a bunch of extra fields as we like and introduce as many custom post types are we want without extra migrations.

Downside is that a database query is needed for every meta field required (although caching and eager-loading could be used to mitigate this).

1. Polymorphism

We would make a separate model and table for every custom post type and make it morph to the parent post table. The posts table will need fields postable_id and postable_type to link the a post type to its parent Post.

E.g. A products table might have fields price, weight etc in addition to the standard post fields.

We would morph the Product model to Posts with

public function post()
{
    return $this->morphOne('Post', 'postable');
}

whilst the `Post` model can just have:

public function postable()  
{
    return $this->morphTo();
}

Then the api would be like

$product = Product::first();
$price = $product->price;
$content = $product->post->content; // this field is on the post model

To make a new product we'd need to new up both models:

// untested
$product = Product::create(['price' => 2500]);
$post = new Post(['title' => $title, 'content' => $content]);
$product->post()->save($post);

Ref: http://www.richardbagshaw.co.uk/laravel-user-types-and-polymorphic-relationships/

This will allow use of the authorization features.

Show number of sales, revenue, products low in stock

The test it_completes_an_order_upon_payment in PaymentTest intermitantly fails due to the mailtracking class. This test results in 2 emails being sent and the assertions to check are sensitive to the order in which they are sent. Tried just checking all recipients but this hasn't helped.

Ability to restrict shipping methods by country. E.g. UK Shipping only for UK. Customer would choose this at the payment page once the shipping address is know.

UX for setting a shipping method would need to include or exclude country identifiers using a multi-select.

Hi there, I just wanted to say that this looks like it has real promise and I like the way it's starting to look! Complements to you, still a few bugs, but for a bleeding edge build it's looking nice.