Saturday, 26 October 2013

Drupal 7 / Ubercart Video Tutorial 9 of 10: Creating Product Kits, Store Stock and Order Status




http://www.ubercart.org/docs/user/30436/ubercart_3x#S1E9
[related: http://veg-buildlog.blogspot.com/2015/07/shopkeeper-puzzle-how-products-are.html which is about attributes from a stall-holder's point of view]
In the 9th Drupal video tutorial of this series, we continue developing our Ubercart site by
  • configuring product kits,
  • setting up store stock and
  • looking at our order states.
This is the final video tutorial before we actually test our site and push it live.

http://www.youtube.com/watch?v=cX8wpEzhFt8


[Drupal 7 / Ubercart video tutorial 6 of 10 showing how to set UPS, Paypal, and conditional taxes]
[Drupal 7 / Ubercart video tutorial 7 of 10 showed how to use the default catalog module]
[Drupal 7 / Ubercart video tutorial 8 of 10 showed an alternative flexible method of showing a catalog]
[Drupal 7 / Ubercart video tutorial 9 of 10 shows how to use product kits, stock, and order states]
[Drupal 7 / Ubercart video tutorial 10 of 10 shows a simple checkout, reports, and suggests a theme]

Hullo and welcome back to the ten part video tutorial series on using drupal for ecommerce with ubecart. I am Pete Yarorski, the Toronto website developer specialising in Drupal, and like all the video tutorials in this series, this is brought to you in a collaboration between myself and the Ubercart.org team.

Following-up on the previous video tutorials....
We have gone-ahead and created our site. [0'23]
We are pretty close to having it finished and launched. [0'25"]
But there are still a few things we need to cover, which include
-setting up product kits, and
-stock notifications .

In this video tutorial, I hope without talking too long, we will cover
-checking-out an order, and covering the
-order status workflow [from a shopkeeper's or a programmer's point of view].

So, with that [introduction], let's dive right into it [the rest of the video].

Product Kits

The first thing we are going to do is take a look at setting-up product kits. [00'46"]

If you are not familiar with product kits: essentially what they are is an item in your store that will pull-in various Ubercart products that you have already created, so [for example] you can specify two products [as a customer] and specify that specific discount for your customer [as a shopkeeper or developer]. [01'02"]

I'll show you that in a quick second, but, just briefly, we can go to [admin] store>configuration>products>product kit settings, and we can set the default for when we are setting up a product kit.

The three different options are essentially that you can create a
  1. unit, and not list the components when you check-out, or
  2. product list and components when you are checking-out, or
  3. put all the parts in to the checkout and let people choose individual parts as they want to.
We are going to leave it [the default setting] as a unit and let people see the individual productst as they order.  [1'30"]

Now, to add a productkit  to our site we are going to
content>add content>product kit
Just briefly - when we do this: remember that we have set-up our specific urls when we went to
configuration> search and metadata > url aliases > patterns
We set these up for product kits as well, so if you don't have the proper-looking url down here at the
content>add content>product kit> ?create product kit?>pathauto settings [near the bottom of the page on the left], you can go over there and set that up.[01'56"]

Now this:
[name in the name box] will be "Super Saver"
[description in the description box] "buy two products and save big"? - I dunno. Give it a proper description, based upon what you are actually creating, but, again, for this video tutorial we are not going to do that, and,
[image in the image box] as always, we are going to put Bailey [the dog picture] up on our site.
[How is this product kit handled by the cart?
-as a unit
-as a unit; list individual products - default option
-as individual products] We will leave this as the default settings.[2'21"]

[Products
-download of purchase
-Pete's awesome product
-Pete's super awesome Drupal book
-Pete's super awesome T shirt] And what they're going to get - any customer that purchases this kit - is going to get our Drupal book and a Drupal T shirt. [because they are highlighted on the form][2'26"]
[list settings] We don't have to change the list settings.[2'32"]
[shipping settings] Interestingly we don't have to change the check-box for "make product shippable"
So you'll see, when I save this, that I will get an error-message. I will explain that to you when we do that.
[menu settings]
[meta tags] Beyond that, you know, we can add some seo tags.
[revision information]
[url path settings]
[xml sitemap]
[comment settings]
[authoring information]
[publishing information] The rest of this ought already to be set-up

[published]
[promoted to front page] We just need to promote to the front page so we can see it.
[sticky at the top of lists]

So, now we have got our image up there, let's go ahead. We will press save and continue.[2'54"]

[Notice: undefined index. shippable in uc_usps_product........line_134. ] Here is the error message that I warned you about. It is usually in relation to an undefined variable.
So looking at line 134 of this module's code, it just relates to the form of code for UPS [United Parcel Service], it just relates to
the form settings: whether or not "shippable" is set. Because the "shippable" setting is not enabled for a product kit, it looks as
as though [that is why] we are getting that error. If you ran into something like this, it would be a good time to post an issue on Ubercat's
mainenance page on Drupal.org. I have not gone-over to check whether this might be already addressed, or already pointed out: that kind of thing. So: it won't affect
us, but if you are doing this, and you get that error message, that's the issue.[3'36"]

The reason why we are not pressing "save and continue" is that we have the opportunity to apply discounts here.
So if we bought these two individual items, our total would be $109, but if we want to add a heavy discount here for users, we can do this:
[Total price box]$70.
We'll make that $70, and then if we press "save and continue", that discount is applied to both products. Not necessarilly evenly, but we can change that if we like to.
Actually, it looks like it [the default reduced price on each item] is probably a percentage of their costs, so it could have been applied evenly.
Obviously, you can change around the quantity and the discounts if you want to, but now we can go over to preview.

And of course we get tonnes of errors. This is not necesarilly a good thing. We don't really need to preview; I meant that we can go to view.
There when we are reviewing the product, we see $70. The two products that we are specifically getting here, the image for our product,  and then we had an attribute on the awesome book, so we can choose whether to use that as well. We will go to yellow.
[add to cart button] And now if we added this to our cart we can see here that we've got $70, we have got the colour yellow, and our two products are listed.[4'46]
So that is creating a product kit. It is pretty straightforward; it's pretty easy to to, and it's a nice convenient way for you to add products to your site for users, obviously, not to have to purchase the items individually.[5'00]


Stock


From that, which is a pretty basic look at those [kits], we are going to look at stock notifications
Just briefly, we will step into Pete's Awesome Product here. Actually: I am sorry. Before that,
we are going to go to

store> configuration>stock notifications

This is just the default setting for the stock notification system itself.
[send an email when stock reaches a certain threshold] we will send an email when stock reaches a certain threshold, because I want to maintain my stock levels, so I want to know that.
There is the subject [of the email] that I would get, and the text.
[presses "save and continue"]
So: pretty basic; nothing complicated.[5'35] We'll save those configurations,
[content> ] and now if we go to our content, we can actually enable stock notifications for a specifict product.[5'43] So...
[looking at a list of products with links] What we were going to look at was Pete's Awsome Product, I think,
[clicks on the link for Pete's Awsome Product]
[clicks on the view |edit tab on the product page] and we will edit this, and when we edit the product we will see that there is a
[product | attribute | features | stock ] tab for stock, so we will go-ahead
[check box under heading "Active"] So we will check "stock". This check-box would normally be un-checked [6'00"], but we will go-ahead and check that off.
[box under heading "STOCK] And we will add our stock [amount] here. I have already created an order, and that is why I am at minus two. So let's say that I have 100 in stock
[box under heading "THRESHOLD"] and my threshold is 10. So when I have 10 left, I get an email that says "you are getting low".
[button "save changes"] So I save those configurations,
[screen returns to the view wnd edit product page] and review the product. Nothing changes here for the product the customer or anything. They have no idea what your stock levels are at, and ubercart by default will allow customers to continually purchase the item, regardless of the stock level.  This can be a good or a bad thing. This can be a good or a bad thing for you. You know, if you are dealing with a physical product, you could have something that goes to back-order, but you don't really want them to know it, but then you don't really know when it is going to ship, and you can create some issues there. [06'50']

If you are looking for a solution where customers can't purchase if there is no stock, there is this module, which is the out of stock module. [7'00"] This will replace the add to cart button with an out of stock message. The good thing about this is that customers can no longer order something that is out of stock. The bad thing is that you don't know if someone is trying to order a product that is out of stock; you are not really sure what your demand is.  Nonetheless, I will briefly show you here: I have installed the module to give you some kind of idea of what we are looking at.
modules>
So I scroll-down to Ubercart Extra modules... Out of stock notifications [button: save configuration]. Then we will enable this. [enables module].
Then when I go back to my product [view | edit screen], I have 100 in stock, so the customer knows that. And if you go-over to [the stock page] stock, [stock column] press zero. Save changes.  Go back to our home page. You see an "out of stock" message. [7'57"] That "out of stock" message is actually customizable. [08'00"]
store> configuration > store > out of stock notification
...over at out of stock notifier. Or notification. Sorry.
[on to a page of options]
[tickbox: display throbber = moving wheel on the button] And we can display this "throbber". which is a kind of annoyance, so we can take it out.
[tickbox: display customer stock information] We don't have to show customers the stock information, so customers will not see that.
[pre-filled message box reads "out of stock"] What we see here is what customers are going to actually see.
And this is dependent upon our html here. So this is, by default, filtered. So if you saved that, you would see this whole thing. By default we have the red [text]. But you can set that as whatever.
[button: save configuration] go ahead and save the configuration. And there we go. So if we go back to our home page. [8'33"] you will see "out of stock", and that we have removed the actual notification for the throbber and for the actual stock level. But we don't see that because we are out of stock anyway.

So that was that module. Again, there are positives and negatives to both [ways of displaying out of stock items] . It [the best option] depends on what your preference is.


So that was product kits , and that is stock notification.
That's typically it for the Drupal set-up with Ubercart.

Now, wrapping things up, what we are going to do is walk you through the process of making an order and  walking-through the order status, just so you are aware of how that works, and some of the options that you have. That we will be it for the tutorials.



order process


So lets go ahead and do that, by going back to Products, and I think we have already added that [product] to the cart, but we will go ahead and add to cart.  So we are going to add two of these. We are going to have the $5 and the $2. Just as a point of reference, we had the $5 which added another $5 - sorry
we had the colour attribute black which adds a $5 charge to our products so it adds $75 as opposed to $70 (the yellow does not have an increase). So we will go ahead and checkout, and if you remember....

...we've got some issues here with our out of stock module, so maybe it wasn't as great as I recommended: use at your own risk! I apologise for that.

But we will go ahead. We will check-out here [10'01] This is all set-up on my sandbox site, so I can checkout with that. Again, I would recommend that you do this in a sandbox site, just to check that your order statuses work and that you can checkout. So: we are reviewing our order. Everything looks good. We are shipping to Hollywood. And now we can go-ahead and submit that order. Again, I have my sandbox customer ID. This was set-up in one of my previous video tutorials so, hopefully, if you followed along the entire series, you know what I am talking about there. Now I can check-out here. [10'34"] I can go to "pay now".

Just briefly, here, again, you see the individual product items [in a paypal shopping cart and payment screen], rather than having the product kits listed. So if we had changed that and we had just listed product kits, it would not be the individual products [showing] here.

So we can go ahead and pay now. We have just completed our order so we will go-ahead and return back to the site. [which says "order complete"]. So we can now go to our orders and check them out
store>orders>view orders
and you will see here that the newest one at 1.45 was completed.
The reason why it is completed is that the products that we had were not actual shippable products. We did not set those up to be shipped by UPS or anything, As a result, if we go to our order status here, you will see that we got that payment. We got the payment and boom! the order was completed. There is not much [else] going-on there. We could send, you know [11'30"] an order comment, and then send that (by pressing "update") to the customer himself or herself, and that would be it. Again, if you take a look quickly at the log here, it shows you how this proceeded through our system.

Now that is all great for the one product that, you know, isn't shippable, and is available online, like your product roles, or your downloadable products. But if you have a shippable product, there is going to be another product that you are going to go through.  So let's go ahead and do that. [11'55"]

content>

I am going to go to my content and [click on] I think "super awsome T shirt" - this is a T shirt with Bailey's photo. It is an actual shippable product. So we will go ahead and add this to the cart. We will check-out. And we will choose "1 Main Street". My billing address is the same as my delivery. We have got our shipping options here - so we will keep it [the option] at $15. We will go to review. We will submit the order. Enter a password. Pay now. And [12'39"]
when we return back to the store, when we go to
store>orders>
You will see here [next to the order] that we have "payment recieved"; we are not actually completed. The reason for that is that this is a shippable product, and we actually have to package and then ship. So, the next step here, if you are administering a site like this, is you go to your
|VIEW | EDIT | INVOICE | PAYMENTS | PACKAGES | SHIPMENTS |
"packages", and we will make a package, [12'59"]. This is going to be in packet one. So that is done. Now we go to
|VIEW | EDIT | INVOICE | PAYMENTS | PACKAGES | SHIPMENTS | ...
[dropdown menu: ship manually] We are going to ship it manually, and so in doing that, we have the saved address - the ordering address, the destination - where it is going which is to the customer, the package and we obviously have one,
[box: package type] you can enter a package type if you want to here
[box: declared value] you can enter a declared value, again, if you want to
[box: tracking number] if you have a tracking number - so if you are using UPS - you can manually enter that in.
[boxes: weight, dimensions] Weight in pounds. Again, all of that information which can be included.
[boxes under a "shipment data" heading] Now: shipment data. Because we are doing this manually, we would be entering this data in for whoever our shipping [company] was - you know, perhaps we are using [?] data, and, you know, we don't have that installed in our site, so we go ahead and do that.
[drop-down menu for number of days' delivery] Expected delivery will be - say - the 31st.
[box: shipping cost] Shipping cost is  - I don't know - let's say $10.
[button: save shipment] We will save the shipment

We can also go and them print the packing slip.
And if we checkout the log, we see that nothing - we see that here we don't actually have the completed [order] or anything beyond pending - right? That's right. And "payment recieved".

So if we now go back [14'21"] what we can do here, is that now we can go to
[box: order status] completed, and we can add an order comment and say "order shipped October 27th" "tracking number is..." and then enter a tracking number
[checkbox: send an e-mail notification on update] make sure we send an email notification to the customer
[button: update] press update.

And now our order has been updated. We see that here, the order status has been changed to shipped, our customer has been notified, and then when we go and actually check our store orders [it's done]. So the one thing [to remember] here is that we went from the order completed meaning "payment recieved" to mea


We might want to indicate that there is a step between them when we are actually shipping. So if we went into confuguration unders
store>orders>workflow
you will see here that we have the order statuses. We can go ahead and add a custom one, and we will say
[box: order status id] shipping
[box:title] Shipping
[drop down: payment recieved] payment received
[button: create] So we will go ahead and we will create this.
And now you see that we have "payment received" here.
So now what we can do, is that we can go back to our orders themselves, look at this [order], and it is not completed; it is actually shipping. So if we update this and we go back to our orders, we now see that this is shipping. Right? Once we have confirmation that it has been delivivered from our courier and we know that we are good, we can come back in here and then enter it as completed. Again, it's a minor thing; it's totally up to you. You could also add another status that says, you know, that is is packaged, so then you know during the day - maybe you have a pickup every other day or something along those lines, maybe you could have something hanging around in your warehouse that is packaged but not actually shipped.

So that's it for this video tutorial.

In the last video tutorial what we will do is wrap everything up, to take it to [being] a production site, which is not very complicated. It is pretty much just our UPS [United Parcel Service] and our  and our Paypal that we want to change-over. But we also want to walk-through as an anonymous user to make a purchase, and a few other things.

So, again, if these video tutorials are helpful, leave a comment, let me know. Hopefully we will see you in the next video tutorial. Thanks very much


[Drupal 7 / Ubercart video tutorial 6 of 10 showing how to set UPS, Paypal, and conditional taxes]
[Drupal 7 / Ubercart video tutorial 7 of 10 showed how to use the default catalog module]
[Drupal 7 / Ubercart video tutorial 8 of 10 showed an alternative flexible method of showing a catalog]
[Drupal 7 / Ubercart video tutorial 9 of 10 shows how to use product kits, stock, and order states]
[Drupal 7 / Ubercart video tutorial 10 of 10 shows a simple checkout, reports, and suggests a theme]

Drupal 7 /Ubercart video tutorial 8 of 10: Over-riding the Catalog and Creating Product Attributes


So if we go to

We are going to call this [name] "Product Type", because we are going to sell different product types on our site - we are going to sell T shirts , CDs, whatnot.[4.08"]

Now we've done that let's go ahead and add some terms. So. Name: "T shirt". We could add some meta-tags and relations [?} if we want to , but we don't really need to do that [at this stage]. We have added T-shirts.  [Name] "CDs". [save]. I guess people don't really want to sell CDs any more but we are going to go historic here. And now, I guess, books. People still sell books. And three should be enough, so that's fine. [4'48"]

Now we have taxonomy terms but we don't have them associated with our content . So if we went to...

> structure > content types > Product > Edit | Manage fields | Manage display tab | Comment fields | Comment Display


...you'll see that we don't have any fields, so we will have to add that [association].  We are going to add a new field here.


> structure > content types > Product > Edit | Manage fields tab | Manage display | Comment fields | Comment Display
Add new field

label
We are going to call this "Product Type". And [5'11"] you actually can't see what I'm doing here. But I am going to make this a term reference - that should be on your [drop down menu] list.
And let me make this a select list because I only want to be able to choose one. [5'20"]
(If you want to make this a free tagging [site], where, you know, you have thousands of different tags; you never know what you are going to have, you can make this
 
a free tagging field so that you can always type-in a new one, and it will automatically create the new term. I am sure that I am only going to be selling three different product types, so that's all that I want.)
So it is actually going to use a product type vocabulary . [scrolling down the page looking at options]

required field

It's going to be a required field.

Default value
The default value for this field, used when creating new content.
It's not going to have any default [value]. We are only going to allow one value. And it [the value] is going to be out of the product types. So I am going to go ahead and save that. Obviously you could change that if you wanted. And I'll leave that. That's fine. [05'58"]

Product Type field settings
These settings apply to the Product Type field everywhere it is used.
Number of Values

Maximum number of values


*The vocabulary which supplies the options for this field.

Now we have our actual contents. [from the admin>content menu]. When we go over to add a product ( we are going to do this afterwoulds, actually, but I just want to show you) .
?missed a bit?


Now: if we go over to Views, the Views module comes with a taxonomy over-ride.
What this will do is: -
  • The system actually has urls for taxonomies.
    They are always: taxonomy / term / termID 
  • So when we create these taxonomy terms using the url pathauto module...

    If you remember we set-up the data:
    we had url aliases and patterns set-up for taxonomy terms.
    >configuration > search and metadata > url aliases > patterns















Enter the path you wish to create the alias for, followed by the name of the new alias.

Existing system path


http://uc:8082/
Specify the existing path you wish to alias.
For example: node/28, forum/1, taxonomy/term/1.


http://uc:8082/

Specify an alternative path by which this data can be accessed.
For example, type "about" when writing an about page.
Use a relative path and don't add a trailing slash or the URL alias won't work.

So it will be the taxonomy vocabulary plus the term [that is] what we will see [in the url]. [6'40"]


What will happen here
>structure>views>taxonomy term>path  ...is

Views [module] will over-ride [urls set-up as above] using .../taxonomy term /....
and then it will take an argument [technical term from maths?], and that will be based on the default menu , so we can over-ride what our actual View will be or what our page will look like for the specific taxonomy term .

(I know that this is probably going over way your head [and I have just enabled the redirect module? Yes? No?]  I know that his is probably going way over your head and it is way beyond what this module originally envisaged, but I just want to do this because it is a great way to customize what you are doing, so: just trust me and bear with me!)

So now we have a taxonomy term over-ride. [7'16"] Let's go ahead and we will edit this.

>structure>views>view>taxonomy term>edit [on a drop-down menu at the end of a line]

We are going to take a quick look into Views.
What Views actually is, as I think I mentioned before in another video tutorial; Views is a graphic interface for creating database queries. Rather than write your constant query - like "select from  where", you can do it all through Views [module] and it will actually develop a query for you, run it,  and you can create pagers [third line from the bottom] out of that.


#overlay=admin/structure/views/view/taxonomy_term/edit
Taxonomy term (Content)
Modify the display(s) of your view below or add new displays.
Displays      Page Feed Add

Display name: Page
Title:        None
Format:       Unformatted list | Settings
Show:         Content          | Teaser
Fields:       The selected style or row format does not utilize fields.

Page settings
Path:
         /taxonomy/term/%

Menu:
         No menu

Access:
       None

Header         Add

Footer         Add

Pager
         Use pager: Full | Paged, 10 items

More link:     No


The default taxonomy over-ride, when you launch [a site] is an unformatted list of teasers. [short first parts of paragraphs encouraging a click to further reading of blog posts]. [7'42"]

Show:   Content          | Teaser
Fields: The selected style or row format does not utilize fields.
I don't want to do that; I am going to change that. So the taxonomy over-ride will use...
[clicks on Show: Content to get some options on a pop-up menu][7'46"]I want fields.

Page: How should each row in this view be styled: All displays (except overridden)
[no longer selected]


You may also adjust the settings for the currently selected row style.


I am going to apply to all displays for this taxonomy term. [pop-up closes]
And now I am using Fields [there is an Add link next to Fields: , which leads to a pop-up menu of about 20 names of fields next to tick boxes = check boxes]
Format: Unformatted list | Settings
Show:   Fields           | Teaser
Fields: Add
The selected style or row format does not utilize fields
So I am going to go ahead and I am going to add two fields. [a drop-down Filter finds them on a long list]

Add fields
[search box ]
[drop-down menu to filter results eg content or product]


Content: Title - the content title
Product: List Price - the manufacturer's suggested price
Product: SKU - the part number or bar code





This is just quickly [choosing options out of about 20] - obviously you can change it a little bit yourself.
First I want my
Content: Title - the content title
Then I want my
Product: List Price
And the
Product: SKU- so I lied: I am going to add three fields.[8'19"]

[another menu pops-up automatically labelled Configure field: Content: Title]
Right: So we will keep the title..


And I am actually going to make this a table, so we will keep all these labels that we have. [on a follow-up screen] So that actually makes sense for someone who is going to read the page. Instead of making this an unordered list we are going to make it a table.
[clicks on Format: Unformatted list |. A menu pops-up]
Page: How should this view be styled
For [dropdown menu: all pag
es]
 
Unformatted list [no longer selected]
If the style you choose has settings, be sure to click the settings button that will appear next to it in the View summary.
You may also adjust the settings for the currently selected style
You have some other options here [on the "Page: how should this view be styled" pop-up box] if you want to chase those up [experiment]. So that is my View.

One thing I am going to do is that I am going to make sure that it's only products that are going to be shown on this. This is a bit of a caveat.  Bear with me for one second here, and I am going to explain this to you.

 >structure >views >view >filter criteria >add [on a drop-down menu at the end of a line]

Add filter criterea
[search box ]
[drop-down menu to filter results eg content or product]


Content: Type - the content type
(for example a "blog entry", "forum post", story", etc)







Content: Type - the content type (for example a "blog entry", "forum post", "story", etc)
[after pressing the "apply" button, a second menu pops- up][8'58"]
Configure filter critereon: Content: Type
For [dropdown: all displays]

Operator

Is one of Is not one of

Content types
Select All
Article Basic Page Product Product Kit

More

I am going to add content type.
OperatorIs one of
I am going to make sure that this is an acutal product.
Content types
Select All
Article Basic Page Product
I go-ahead and hit "display".

High Five!
We are not actually going to see a preview because we are going to need to generate some arguments . [9'18]

If you are only using one taxonomy on your site, so you are only using products and you are only using  taxonomy terms related to those products, this solution is fine. [9'39"]

If
  • you are using blog posts, and
    you are using taxonomy terms to categorise the blog posts, and
  • you are using articles and
    you are using taxonomy terms to categorise your articles,
you are going to run into a problem here. Because
this overrides all taxonomy term views
, and so all the different vocabularies and terms;

  • your other content is not necessarilly going to have these prices and SKUs, and
  • you might want to have a teaser for that specific article or blog post.
If that is the case, then you are going to have to look-into another module called the
View Field Module
. What that will actually allow you to do is create
different taxonomy overrides for different vocabularies
. I actually haven't used it, so I am sorry: I cannot go into the details about it.  But there is a great post here ... that details what you have to do in order to override this [thing]
http://drupal.org/node/424168#comment-5082962  [...]This will tell you how to go ahead and do that [other thing] . The project itself is available at http://drupal.org/project/viewfield
So this is the module. I'd advise you to go ahead and get the Drupal 7 version, so you can test that out. So that is a brief side-note. For the sake of this video tutorial that [problem and solution] is not going to be an issue because we are only going creating products on our site.[10'47"], so we can override all taxonomy term fields.

That's why we had a content type filter there.

Let me go-ahead and I am going to save this [screen of settings using a save button top right]. [10.58"]
Now we have our over-rides set-up. So that's great.


Attributes
>store >product >attributes
[11'10"]

Before we actually go ahead and create some products with tags, to look at this different view, I am going to go-on to the next part of this video tutorial and we are going to go about configuring attributes.

So to do that we are going to go to
>store >product >attributes
Attributes
home>administration>store>products
Name Label Required List position Number of options Display type Operations








color color Yes 0 4 Select box edit options delete
In the previous video tutorials in this series, we went-ahead and we created [the attribute] color. You will see that we have got grey, black, and red. And so, for the sake of users who, maybe, missed that video tutorial, I am going to create a new one. I am going to call this a "yellow" colour here. And you will see here that the default list position. This will come-up when we add our products. Don't worry about that. You can change it if you want to. [11.46"]

Default Adjustments: 

Default Adjustments
Enter a postitive or negative value for each adjustment applied for each product selected.
Any of these may be overriden at the next product level
Cost
Price
Weight
This is an interesting and helpful field. What it allows us to do is: you'll see that if you do sizing, you may want to have a 
  • default cost, and you sell an XXL, there is more material so it can then charge an extra $2 for a XXL shirt. So it will add $2 to this; every time you have a product that has an attribute of XXL, it will add $2 automatically on to that cost. And you can associate the same thing with the 
  • sale price, so that it adds $2 on. Alternatively, if you are doing something associated with a specific
  • weight: if there is a specific weight for this attribute, you can go ahead and add that in here. These are all defaults.You can also do this [adjustment] individually on
  • specific product; you can do that as well. So that is a great thing about attributes here.

So we will go ahead an we will submit this. That makes four attributes for our products.


Now let's go ahead and add some new content.[12'31"]
>content >add content >product

Just as a reminder: if you already have content then you will now be going back to it, as new taxonomy terms that we create for our product [??].

>content >add content >product So: creating a new product. Back here. So we are going to call this - I dunno


Product Name*
Summery
Description (edit summery)

[13'00"]
It's something on a CD, Right?
So now what are we going to do now? I guess we are not going to need an image, but we will add an image anyway. We don't have an image, so as always in this video tutorial I am going to upload one of our dog Baily.

Image:
Add a new file


Now, I am going to say [in the Product Type box with drop-down options: select option, books, CDs or T shirts] this is a CD.
Product Type*
So the SKU [in the SKU box] is going to be "pete's CD", right?
SKU*

product SKU / model

The sell price is a whapping...

List Price $ Cost Price $ Sell Price*$
the listed MSRP    Your store's cost  Customer purchase price

...because everyone wants to hear me sing.  And the maximum package quantity
Maximum Package Quantitiy*
Default setting. So we are going to leave everything as default , because we are just doing this to take a look at Views[module]. We are just waiting to for the image to upload: it's almost done.
There. Now, with the magic of editing, that took no time, so we are just going to [press] save and Continue.
[13'43"]

Where do we go? [to the shippable box] This is a shippable product. [clicks] It is not shippable product any more [lie], so we press save and continue.

adding an existing attribute to an existing product
>content >add content >product (using attributes configured on >store >product >attributes)

Now: the reason why we went-ahead and pressed save and continue is because I want to remain on the products page so we can go to our attributes. So: we have to add an attribute to this product. We are going to add our colour attribute. Now, once we do that...
We can go to our options, and you will see here that we can choose the options which are associated with this particular product. So every colour is going to be available for the cover of my CD, except for red. Now...
We are going to go ahead and save that.

If I wanted to adjust my cost for my price and my weight, for this specific product, rather than using a default, [in the cost boxes next to each option] I can go-ahead and do that. The default [radio button] will select which option will be selected by default when a user selects this [CD] item. It will be defaulted to black. So I will go-ahead and I will submit that. And I will save that.

If we go and look at [the] adjustments [page], we can see here that we can use alternateive SKUs. [by filling-in the  boxes]: Pete's CD black; Pete's CD grey, and Pete's CD yellow. Again we are going to go-ahead and submit. [15'07"]. And then if we go back to the product [page], we are still good: we have our product CD, we have our regular default SKU, we have our sale price. So we will go-ahead and we will save that.[15'17"]

Right. There's our list of products. So if we click on "CDs", here, it is going to show us all our product types... here is our actual View. We see title, we see list price, we see SKU. So that is defaulted, rather than the catalogue [default setting]  that we had before. You will see that we have a product type of CDs.

If we go to
>configuration >search and metadata>url aliases>
you will see that we have one [url alias] for each. Taxonomy terms 7, 6, and 5: these are the taxonomy terms that we created. Bulk CDs and T shirts. And we are good to go. [15'55"]

Screen revolves.[16'02"]

replacing the catalog

OK. So now we are actually set-up I am going to go ahead and show you how to replace the catalogue.

You will notice that we are on a different screen, because I actually screwed-up the video tutorial, so I paused it, and I am going to show you what I am doing. I have erased that part of the video tutorial, so we are starting here.

Right now what we have done is that we have over-ridden the taxonomy term pages so that we have a specific look for our product types and a we have gone and done that  with attributes. What we don't have is a list of all the different product types , that we can go into, kind-of like a kind of product catalogue , and then go-down by specific fields. And so we are going to do that. [16'31"]

Let's go-ahead. We'll go to [admin>structure.] Views. And we have to add a new View. [View Name box] "ubercart product". It's going to be actual Content [in the show box]; it is going to be of type product [in the type box], [in the sorted by box] newest first. In the Page title box: catalogue. This is going to be at [in the path box] "product type".

Let's just confirm this. [on admin>configuration>search and metadata>search settings>] because what we want this to be is the beginning of our actual [alias: product-type:books].... yup!

So what we actually did was [to make sure that] if we went to [path] product types, it would work as a url, and if we went to [path] /books, it would also work as a url. That's just good development practice.

  • We are going to create this as a table. With fields [these are the default settings] times-ed by ten. We are going to use a pager. [there is a ticked box called "use a pager" - maybe for page breaks?] And we are going to go ahead and edit it. So, now, what we want this to do is kind of create all of our products on the page, and allow users to filter them. [17'41]

So, what we are going to do is to create a similar View  to what we did on the other View.
Then when we go-over to get that View you will notice that I have changed a few things, but nothing overly crazy. [using an Add fields pop-up, working down the options]

We are going to add the add to cart form - so I can show you what that looks like.

We are going to add the display price.

We are going to add the image [ticking a box marked Content image (uc_product_image: delta) Delta: appears in - node product, node product_kit ]

I think that's it. Obviously you would want your two Views to match-up, so it look consistent between the two. It's not a huge concern, but it's just a good way of doing this.

[create a label box is ticked, followed by a "label" box]
We are going to call this [label] "image" [filling-in the box][18'32]
Ah. The Delta. We are not going to use this.
So we will use the add to cart. Wait for that to display.
Price: we will go-ahead and edit that.
Then we'll go back to add that image. Hold that window. [18'52"] [ticks a box]
We want this image. Not the Delta one. We chose the Delta before. We want the Content Image.
So it is image, then we are going to select thumbnail; link this image to content [from a dropdown box labelled "link this image to" with content as an option]
We'll add to display [clicks an accept button at the bottom of the page]

Now the cool thing about this; the thing that gives it a twist, is that, right now, this will show all of our products. So if we went-over to this, let's save it [presses a save button] and go and take a look at it.  [The screen reverts to a browser default page until the path the the site is re-typed] [19'26"]
Right: here are all of our products; we can add all of them to the cart.



But if you have, let's say, a thousand different products displayed in a haphazard way. So, what we can actually do, is a pretty cool thing with Views,  is to add an exposed filter for users to specifically choose: if they only want to see your T shirts, only show them your T shirts. [19'53"]

We are going to go-ahead and go-into content, [on the "add filter criteria" pop-up menu] and we are going to choose taxonomy terms. We are going to apply that. And now: it is going to be[from vocabulary options of "product type" or "tags"] a product type, and it is going to be a [selection type either dropdown or autocomplete] dropdown. So [press button] apply and continue. [20'04"]

[next screen is called "configure filter criterion. Content: has taxonomy term]
You are going to expose this to the users. So now they have control of this.[20'07"]
[in the "label" box types] "only show the following products" [20'13"]
[looking at an "operator" selection - "is one of", "is all of", "is none of".... ] "is one of" [20'16"]
[looking at a "select terms from the vocabulary Product Type" form including "allow multiple selections"] We are going to allow multiple. [20'16"]
["remember last selection" is a tick box] You can remember the last selection, so you show them T shirts if they have always had T shirts before. It is entirely up to you.
[presses "apply" button] press apply and it is all displayed.[20'26"]
[presses "save" button top right] Now we are going to go ahead and save this. [20'31]
[presses F5 in windows] We are going to go-ahead and re-load this page. [20'33"]
Now they can go ahead and say "I only want to see CDs"
[selects "CDs" from the new drop-down menu and presses an "apply" button.] And there you go. We only have one CD. [20'39"]
And go-in to this, [shows picture of dog Bailey],
And they want to see the other CDs.[shows summery of CD as for a list]
And you will see now [in the path] that we have "product/CDs"[20'46"]
So this is our other View that we created. And from this they can use the add to cart form, right-away, and if they decided that they wanted to see all your product types, if they removed "CDs", and then they are back to all of your products. This is why I like using Views and doing it [the catalogue] myself: just because you have complete control over this. [21'02"]

One thing I should mention again, is that if you are using multiple taxonomy terms for products , you are going to have two different exposed filters here, and you want to create another View for, you know, product types, or lets say just the licences. So: just the licences.  And then you would want to remove your and you kind of get into trying a template for that in PHP. That is a little bit beyond the scope of this video, but you can actually choose which exposed filter is shown. You know, if you are interested in that, I'm happy to do a tutorial on it, supplimentary to this video tutorial series: I just need to know that you are interested in it.[21'32"]