3. Jonathan Lackey
Known in virtual social circles as zuno
•
Creative director at Zuno Studios
•
Based in Redondo Beach California
•
Over 10 years experience in design &
•
web
CMS Expo 2009 - Chicago
5. Websites, Stores &
Store Views
Ability to manage multiple websites &
•
stores from the same back-end
Display the same products in dierent
•
stores
CMS Expo 2009 - Chicago
6. Websites
Made up of one or more stores that
share the same customer information
(i.e. Order information shopping cart)
resource: How multiple websites work
magentocommerce.com/knowledge-base/entry/overview-how-multiple-websites-stores-work
CMS Expo 2009 - Chicago
7. Stores
Can be set up a variety of ways,
but as long as they are part of a website
they share certain information.
CMS Expo 2009 - Chicago
8. Store Views
Mainly used for multiple languages
So if you wanted to display a store in
English and Spanish you create one store
and two store views
CMS Expo 2009 - Chicago
9. One website with multiple stores
Main Website
Website
Store One Store Two Store Three
Store
Store View Store View Store View
Store View
CMS Expo 2009 - Chicago
10. Two websites with two store views each
Main Website Sec Website
Website
Main Store Sec Store
Store
English Spanish English Spanish
Store View
CMS Expo 2009 - Chicago
11. One website with one store and store view
(most common)
Main Website
Website
Main Store
Store
Main Store View
Store View
CMS Expo 2009 - Chicago
12. Extensions
One or more files packaged together
•
to extend functionality
Do not modify core code
•
Installed through the admin panel or
•
Magento Connect
resource: Magento Connect
magentocommerce.com/magento-connect
CMS Expo 2009 - Chicago
13. Modules
Extend features and functionality of the
core
i.e. additional payment gateways,
MailChimp
CMS Expo 2009 - Chicago
14. Interface
Collection of themes that determine the
visual output and front-end functionality
of your store
Can be assigned on either the website,
store or website and store levels
CMS Expo 2009 - Chicago
15. Themes
Combination of layout, template and/or
skin files that create the visual
experience of your store
Default and Non-default themes
CMS Expo 2009 - Chicago
16. Components of a Theme
Layouts - Basic XML files that define
•
the block structure for dierent pages
Templates - PHTML files that contain
•
XHTML markup and PHP for visual
presentation
Skins - Block specific JavaScript, CSS
•
and images that compliment template
files
CMS Expo 2009 - Chicago
17. Interface Collection of themes
Theme One
Combination of files that
Theme Two create the visual output as
well as front-end functionality
Theme Three
Layouts Defines block structure
Templates PHTML (XHTML and PHP)
Skins JavaScript, CSS and Images
CMS Expo 2009 - Chicago
18. Blocks
Blocks are a way by which Magento
distinguishes the array of functionality in
the system and creates a modular way to
manage this array from both visual and
functional stand points.
There are 2 types of blocks
CMS Expo 2009 - Chicago
19. Structural Blocks - Blocks created for the
purpose
of assigning structure to a page
Header
Left
Content
Column
Footer
CMS Expo 2009 - Chicago
20. Content Blocks - Blocks that create content
inside each structural block. i.e. mini cart, tags,
category list
Links
Header
Global Navigation
Category
List
Product Listing
Left
Content
Compare
Column
Products
Related Products
Promotions
Footer
Newsletter Links Callout
CMS Expo 2009 - Chicago
21. File Structure
Set up to keep core, community and local
files separate for easy upgrading and
maintenance
CMS Expo 2009 - Chicago
22. Core
The core code is a collection of
modules developed by the
Magento core team.
Editing core files is
NOT recommended
CMS Expo 2009 - Chicago
23. Local
Customizations that only
reside
on a user’s local copy
Kept in the “local” directory so
they do not interfere with
upgrades to the core code
CMS Expo 2009 - Chicago
24. Community
Community contributed
extensions
Reside in the “community”
directory again to make
upgrades clean and easy
CMS Expo 2009 - Chicago
26. The Heart of Your Site
The catalog is the most important part of
your Magento site and it includes...
Categories
•
•Products
•Attributes
•Tags
•Reviews ratings
CMS Expo 2009 - Chicago
30. Select the store view the
new category will be
displayed in
CMS Expo 2009 - Chicago
31. Select a parent category.
Choose “Root Catalog” if the
new category is not a sub-
category
CMS Expo 2009 - Chicago
32. 1.Name
2.Choose a parent category
3.Description
4.Image
5.Meta data (page title, keywords,
description)
6.Display mode and CMS block
7.Is anchor
8.Is active
9.URL key
CMS Expo 2009 - Chicago
33. Assigning products
at the category level
Products can be added to a category
while the category is being created, or
anytime after.
CMS Expo 2009 - Chicago
34. Assigning designs
at the category level
You can customize the design of each
category individually in the “Custom
design” tab
CMS Expo 2009 - Chicago
35. 1.Choose a custom design
2.Choose how the custom design is
applied to child elements
3.Set a timeframe for the custom design
to take eect (good for holidays and
specials)
4.Choose a page layout
5.Custom layout updates
CMS Expo 2009 - Chicago
36. Special landing pages
for categories
You can create custom landing pages for
categories. Instead of the standard
product listing page you can display a
static content block
CMS Expo 2009 - Chicago
37. CMS as a category
landing page
Standard category
landing page
CMS Expo 2009 - Chicago
39. There Are 2 Kinds of Attributes
Simple Attributes System Attributes
Created by the Required
store owner and attributes that
are specific for every product
individual must have. These
products. cannot be
deleted.
Color
•
•Size Name
•
•Megapixels •Price
CMS Expo 2009 - Chicago
•
40. New Attribute - Catalog Attributes Manage
Attributes
CMS Expo 2009 - Chicago
41. Attribute Properties
1.Attribute identifier
2.Scope
3.Catalog input type for store owner
4.Default value
5.Unique value
6.Values required
7.Input validation for store owner
8.Apply to
9.Use to create configurable CMS Expo 2009 - Chicago
product
42. Front-end Properties
1.Use in quick search
2.Use in advanced search
3.Comparable on front-end
4.Use in layered navigation
5.Position
6.Visible on catalog pages on front-end
CMS Expo 2009 - Chicago
48. Selecting the attribute set will load all of the
corresponding groups (tabs) and attributes into
the product creation/management page
CMS Expo 2009 - Chicago
50. There Are 3 Types
of Products
1.Simple
2.Configurable
3.Grouped
CMS Expo 2009 - Chicago
51. Simple
Is the simplest type of product to sell on
your website; one individual product,
where the attributes are determined by
the store owner
CMS Expo 2009 - Chicago
52. Configurable
Configurable products oer much more
customer interaction. Attributes are
determined by the customer.
i.e. color, size, style
CMS Expo 2009 - Chicago
53. Other Places
Used to display multiple simple products
on one product page and allow the
customer
to purchase any combination
CMS Expo 2009 - Chicago
54. Creating a Simple Product
1.Catalog Manage Products Add
Product
2.Select an Attribute set
3.Select Simple Product
4.Press Continue
5.Enter all product information
CMS Expo 2009 - Chicago
56. Name - Product name as it will appear on the front-end
•
Description - Displays on the main product page
•
Short Description - Displays on category list pages and
•
main product page
SKU - Unique identifier for product across all stores and
•
websites
Weight - Product’s weight. Usually used for shipping
•
Set Product is New from/to Date - Date range the
•
product will be promoted as new
Status - Enabled/disabled. Enabled displays normally on
•
front-end
URL Key - The search engine friendly URL identifier
•
Visibility - Where the product will display. Category,
•
search, both or neither
CMS Expo 2009 - Chicago
Allow Gift Message - Can allow customers to enter a
•
58. Price - Price of the product as it will display on the
•
front-end
Special Price - Sale price for the product. On the front-
•
end this will appear under the original price which will be
crossed out
Special Price From/To Date - Date range for the special
•
price to be active. Automatically activates and deactivates
Cost - Amount you pay your supplier
•
Tax Class - The product tax class
•
Tier Price - Special pricing for higher quantities
•
CMS Expo 2009 - Chicago
60. SEO-related Meta Information is controlled from
here. Page Title, Meta Keywords and Meta
Description can be entered for this product. The
Page Title will display in the browser’s title bar
when this product is being viewed. Meta
Keywords and Description will show in the tag of
the product’s HTML source.
CMS Expo 2009 - Chicago
62. Magento requires 3 image types: Thumbnails, Small and
•
Base
If you do not upload any images a Product Image
•
Placeholder will be used. (To configure these go to
System Configuration Catalog)
By default, all images uploaded for a product will be
•
listed under the main product image. Clicking any of the
additional images will open a pop-up with the ability to
view all the images
Images will automatically resize to fit the dimensions of
•
the
image type
The base image has the ability to be zoomed in and out
•
You can add a Sort Order to determine CMS Expo 2009 - Chicago
the order of the
•
•
images
64. Like categories, you can control the look
of an individual product page from the
design tab
If your product page has a separate
design than the category page, the
product level design will over-ride the
category design
CMS Expo 2009 - Chicago
65. Product Info: In Websites
If you are managing
multiple websites you
can choose which sites a
product is associated
with by checking the
checkbox next to the site
CMS Expo 2009 - Chicago
66. Product Info: Categories
You can assign a product
to as many categories as
you like. Simply check
the checkbox next to the
category
CMS Expo 2009 - Chicago
67. Related Products, Up-sells
Cross-sells
There are 3 types of product relations in
Magento:
Related Products - meant to be purchased in
addition to the current product
Up-sells - are items customers would buy
instead of the current product
Cross-sells - are impulse buys similar to candy
at the register in grocery stores
CMS Expo 2009 - Chicago
69. For each subscriber, both alert lists show the
• Name
• Email
• The date they subscribed to this alert
• The time that the most recent notification
was sent
to them
• The number of times a notification was sent
to them
For the Price Alert, there is also one additional
column. For each subscriber, it shows the
price that the product had at the time that
they subscribed. This includes Special Prices.
CMS Expo 2009 - Chicago
71. Tax Rates
Magento allows full control over your
store’s Tax Rates, from a single
statewide rate to rates per zip code
CMS Expo 2009 - Chicago
72. Country - Select the country associated to this shipping
•
rate. Magento locates the appropriate Tax Rate by
matching the customer’s shipping country to the Tax
Rate country
State - Specify if the country has dierent tax rates in
•
dierent states
Zip/Post Code - Specify if the country or state has
•
dierent tax rates in dierent zip codes (you can specify
a zip code even if you have not specified a state)
Rate 1-5 - Once you’ve defined which region a Tax Rate
•
applies to you have the ability to define up to 5 dierent
tax rates
CMS Expo 2009 - Chicago
•
74. There Are 2 Kinds Tax Classes
Customer Tax Classes Product Tax Classes
Associated to Associated to
customers by products. This
assigning them to allows dierent
customer groups types of products to
have dierent tax
Sales Customer Tax
rates
Classes
Sales Product Tax
Classes
CMS Expo 2009 - Chicago
75. Tax Rules
If you have dierent tax rates for your
dierent combinations of Customer Tax
Classes and Product Tax Classes, you can
define a Tax rule for each scenario
Sales Tax Manage Tax Rules
CMS Expo 2009 - Chicago
77. Origin
Country, Region/State, Zip/Postal code
and City from which the shipments will
be sent
i.e. the location of your company/
warehouse
CMS Expo 2009 - Chicago
78. Options
Allow shipping to multiple addresses.
•
Shipping method can be dierent for each
address as well
Maximum qty allowed for shipping to
•
multiple addresses
When an order with multiple shipping
•
addresses is complete, it will split into
multiple orders
CMS Expo 2009 - Chicago
80. Flat Rate
Enabled
•
•Title
•Method Name
•Type
•Price
•Calculate Handling Fee
•Displayed Error Message
•Ship to Applicable Countries
•Ship to Specific Countries
•Show Method if Not Applicable
•Sort Order
CMS Expo 2009 - Chicago
81. Table Rates
Condition - Determines which aspect of
the order will be used to select proper
shipping price. Table rates are calculated
using destination, but destination can be
figured in conjunction with either weight,
price, or number of items
CMS Expo 2009 - Chicago
82. Free Shipping
Minimum order amount - You can
designate that free shipping is only
oered if the order is over a certain
amount
CMS Expo 2009 - Chicago
83. Shipping Methods
UPS Over 30 global shipping
•
methods available from
• USPS
Magento Connect
• FedEx
• DHL
magentocommerce.com/magento-
connect
CMS Expo 2009 - Chicago
84. Payment Methods
13 Default methods and over 130 3DP
methods on Magento Connect
magentoecommerce.com/magento-connect
CMS Expo 2009 - Chicago
85. Saved Credit Card
•
Zero Subtotal Checkout
•
Check/Money Order
•
Authorize.net
•
Payflow
•
Amazon Simple Pay
•
Checkout by Amazon
•
Google Checkout (Under Google API tab)
•
CMS Expo 2009 - Chicago
87. Theme Terminologies
Layouts - Basic XML files that define
•
the block structure for dierent pages
Templates - PHTML files that contain
•
XHTML markup and PHP for visual
presentation
Local - Simple text documents
•
organized on a per language basis that
contain translations for store copy
Skins - Block specific JavaScript, CSS
•
CMS Expo 2009 - Chicago
and images that compliment template
88. Structural Blocks - Blocks created for the
purpose
of assigning structure to a page
Header
Left
Content
Column
Footer
CMS Expo 2009 - Chicago
89. Content Blocks - Blocks that create content
inside each structural block. i.e. mini cart, tags,
category list
Links
Header
Global Navigation
Category
List
Product Listing
Left
Content
Compare
Column
Products
Related Products
Promotions
Footer
Newsletter Links Callout
CMS Expo 2009 - Chicago
90. How Are Magento Themes
Different from Other?
CMS Expo 2009 - Chicago
91. Maximum customization power
•
Multiple themes active at the same time
•
Uninterrupted workflow. All modules
•
are immediately accessible via template
tags from any template file
CMS Expo 2009 - Chicago
92. Creating a Theme
Directory 1: app/design/frontend/
default/default
This directory contains the layout,
translation (local) and template files
Directory 2: skin/frontend/default/
default
This directory contains the images, CSS
and block-specific JavaScript
CMS Expo 2009 - Chicago
93. Why 2 Directories?
Separating the files that have to be web
accessible (images js) from those that
can be hidden makes for maximum
security
CMS Expo 2009 - Chicago
94. New Default Theme
Make a duplicate of an existing default
theme
Rename the new
directory.
The new name is the
name in which Magento
will recognize your
theme
CMS Expo 2009 - Chicago
95. Assigning Interface
themes to the store
You need to assign your new theme to
your website/store in order for it to take
eect
System Configuration Design tab
CMS Expo 2009 - Chicago
97. Hierarchy of Themes
If the category listing page calls for a
template called “view.phtml” but
Magento cannot find the file in the theme
highest in the hierarchy it will look to the
next theme highest in the hierarchy.
This is method of building design is call
“fallbacks” because Magento falls back to
the next possible source of the required
files
CMS Expo 2009 - Chicago
98. How you see the files in each of the theme
directories
default my_theme_1 my_theme_2
all required files
templates/3-col-layout.phtml templates/3-col-layout.phtml
templates/header.phtml
images/logo.gif
css/base.css css/base.css
css/boxes.css
CMS Expo 2009 - Chicago
99. How Magento sees the files
default my_theme_1 my_theme_2
all required files
templates/3-col-layout.phtml templates/3-col-layout.phtml
templates/header.phtml
images/logo.gif
css/base.css css/base.css
css/boxes.css
CMS Expo 2009 - Chicago
102. Magento Core
Magento User Guide
http://magentocommerce.com/support/
magento_user_guide
Magento Designer’s Guide
http://magentocommerce.com/design_guide
Magento Technical Docs
http://docs.magentocommerce.com
Magento API
http://magentocommerce.com/support/magento_core_api
Magento System Requirements
http://magentocommerce.com/system-requirements
Magento Connect
http://magentocommerce.com/magento-connect Chicago
CMS Expo 2009 -
103. Other Places
LinkedIn Magento Users Group
http://linkedin.com/groups?gid=146360
Magento on Twitter @magento
http://twitter.com/magento
Magento Facebook Group
http://www.facebook.com/group.php?
gid=19137087720
CMS Expo 2009 - Chicago
one of the most powerful features of Magento is the ability to manage multiple websites and stores from one back-end
Websites are ‘parents’ of stores.  A website consists of one or more stores. Websites can be set up to share customer data, or not to share any data
Stores are ‘children’ of websites.  Products and Categories are managed on the store level.  A root category is configured for each store view group, allowing multiple stores under the same website to have totally different catalog structures.
A store needs one or more store views to be browse-able in the front-end.  The catalog structure per store view will always be the same, it simply allows for multiple presentations of the data in the front.  90% of implementations will likely use store views to allow customers to switch between 2 or more languages.
customer accounts/profiles
This determines how your products will be shown in the front-end’s catalog pages.
Products per Page - Choose whether the category pages will display 9, 15, or 30 products by default. Your customers will be able to change this, or to display All products.
List Mode
Grid Only - The products will display in a grid structure and your customers will not have the option to change this.
List Only - The products will display in a list structure and your customers will not have the option to change this.
Grid (Default)/List - The products will display in a grid structure by default but your customers will be able to switch to list.
List (Default)/Grid - The products will display in a list structure by default but your customers will be able to switch to grid.
▪Default Tax Class - Select whether the default tax class for with new products added to your catalog will be Taxable Goods or not.
Warning: The “Default Tax Class” feature no longer seems to be available as of 1.1.6. If you know how to re-enable this feature or where the feature has moved, please edit this page and post your solution to the forum (It might be the same feature as System→Configuration→Sales→Tax→Tax Classes).
There are two types of product alerts to which you can allow your customers to subscribe via email. Each have their own enable drop-down, and Email Template, but they share the same Email Sender. For more information on how to configure email templates and email sender addresses, refer to Chapter 6: Customers. The Price Alert will create a link in every product page called Sign up for price alert. Clicking this link will subscribe your customer to this alert, and they will receive an email when the product price is changed. This includes adding or changing Special Prices in addition to the regular Price field. The Stock Alert will create a link in every Out of Stock product called Sign up to get notified when this product is back in stock. Clicking this link will subscribe your customer to this alert, and they will receive an email when the product status changes to In Stock. For each product, there is a tab listing all customers subscribed to either of these alerts. There is more information about this in the Products section later in this chapter.
This determines the frequency with which Magento checks both product prices and stock status for changes, so that your subscribed customers can be alerted.
Frequency - Designate whether you want Magento to check for updates Daily, Weekly, or Monthly.
Start Time - Select the time of day (in 24 hour mode) at which you wish Magento to check for updates.
Error Email Recipient - Enter the email address to which emails will be sent in case an error occurs during the check for updates.
Error Email Sender - Select the address from which the error notification email will be sent.
Error Email Template - Select the template which the error notification email will use.
This is discussed in more detail later in this chapter, under Products.
This is discussed in more detail in Chapter 5: Promotions, Marketing and Content Pages, under Customer Personalization.
You can determine the level at which prices are shared in the Catalog Price Scope drop-down. If you select Global, prices will be shared across all websites. If you select Website, prices can differ between websites, although they will still be shared between store views contained in the same website. The price here affects several different areas in Magento. For example, this includes product prices, base currency, price filters in the admin, and catalog/shopping cart price rules.
Configure these options to make your site more Search Engine Friendly.
Autogenerated site map - If you Enable this feature, a Site Map link will display in the footer on the front-end, directing to an automatically generated site map including a list of all of your existing categories. In addition to the Autogenerated site map, Magento allows for integration with Google Sitemap. There is more information about this below.
Popular search terms - If you Enable this feature, a Search Terms link will display in the footer on the front-end, directing to list of all search terms, displayed as a cloud. This is an SEO feature because each of these search terms counts as a link to your site, and is registered by search engines.
Page Title Separator - Enter a character in this field, and it will be placed between the various Meta Information in the Page Title, that displays at the top of the browser.
Use categories path for product URLs - This determines how the URL Rewrites autogenerate. If you choose Yes, the URL rewrite for products will include the associated category, and a separate rewrite will generate for each associated category. If you choose No, the URL Rewrites will include only the product name, and there will be only one rewrite, regardless of how many categories the product is associated to.
Product URL Suffix (cache refresh needed) - This also affects how the URL rewrites autogenerate. The value entered into this field, for example .html, will automatically be added to the end of your URL rewrite generated for products. There is more about this topic in the section about URL Rewrites.
If you want to configure Magento integration of Google Sitemap, navigate to System > Configuration and select Google Sitemap from the left column.
The sitemap settings for each of these three types of pages can be configured individually.
Frequency - Designate how often you would like Google Sitemap to check each type of page for updates.
Priority - Designate the priority that each page type receives in relation to the other page types when Google Sitemap updates.
▪Enabled - Select Yes to Enable Google Sitemap autogeneration and automatic updates.
Start Time - Select the time of day (in 24 hour mode) at which you wish Google Sitemap to update.
Frequency - Designate whether you want Google Sitemap to update Daily, Weekly, or Monthly. This can differ from the frequency that Google Sitemap actually checks for updates (as defined above).
Error Email Recipient - Enter the email address to which emails will be sent in case an error occurs during the automatic update.
Error Email Sender - Select the address from which the error notification email will be sent. For more information on how to configure these email addresses, refer to Chapter 6: Customers.
Error Email Template - Select the template which the error notification email will use. For more information on how to configure these templates, refer to Chapter 6: Customers.
Attribute Identifier - This is the name of the attribute used by the system. It will appear in the Attributes list in the Attribute Code column, and it will be used when managing Attribute Sets, however it will not appear on the Front-end. Each attribute you create must have a unique Attribute Identifier, and this value cannot contain spaces.
Scope - This drop-down determines the level at which the values of this attribute are shared. When creating a product, you will be able to see the Scope to the right of each attribute. You can choose to make any attribute shared Globally, at the Website Level, or at the Store View Level. Global means that the value of this attribute for a given product must be the same throughout your site. Website means that the value of this attribute for a given product can differ in different Websites, however it cannot differ between Store Views contained under the same Website. Store View means the value of this attribute for a given product can differ in all Websites and all Store Views. For example, if you were creating an attribute called Color, with a Store View Scope, you would be able to set the color of a product to green in one Store View, and blue in another Store View.
Catalog Input Type for Store Owner - This describes what kind of data the attribute will store. What’s set here determines how data entry for this attribute will take place. For example, a Description attribute would use a text field, so that you can manually enter a description for each product, whereas a Color attribute would use a drop-down, so that you choose the color of each product from a drop-down list (the values of which you will enter in the Manage Label / Options tab). Note that it appears that Attributes whose input type requires multiple predefined optionss, such as the Dropdown or Multiple Select types, cannot later be changed to direct input types like text boxes (and the reverse may also be true), so think hard before making an input type selection.
Default Value - If you choose to enter a Default Value, each new product created with this attribute will automatically have this attribute prepopulated with the value you enter here. However, you will always be able to edit the prepopulated value. This field will not display if you have selected Multiple Select, Dropdown, or Media Image as your Input Type. If you have a Dropdown or Multiple Select Input Type, you will be able select the Default Value in the Manage Label / Options tab.
Unique Value - If you designate an attribute to be a Unique Value, that means the value selected or entered for this attribute for each product must be different. If Color was a unique value, only one product could be green, one be blue, etc.
Values Required - If you require values, you must select a value for this attribute for each product you create. You will not be able to save a product if this attribute is left blank.
Input Validation for Store Owner - This controls the type of check Magento places on the values entered for this attribute for each product. If you select None, you can enter any type of information as the value for this attribute. If you select Email, for example, Magento will make sure that the value entered for each product resembles an email address. If it does not, you will receive a warning message.
Apply To - Decide which Product Types will include this attribute. The three Product Types in Magento are Simple, Grouped, and Configurable Products (there is more information on the differences between these Product Types in the Products section later in this chapter). If you select Selected Product Types, a multiple select menu will appear where you can choose to which of the Products Types this attribute will be associated.
Use To Create Configurable Product - This drop-down will only appear if the Scope is Global and the Input Type is Dropdown. If you select Yes, this attribute will be a Configurable Attribute. When creating a Configurable Product, the next step after selecting the Attribute Set and Product Type is to select the Configurable Attributes for this product. You will see a list of all the existing Configurable Attributes associated to the Attribute Set. If you select the checkbox, this attribute will be a Configurable Attribute for this product. If you leave the checkbox empty, this attribute (while still a Configurable Attribute in your attribute settings) will not be a Configurable Attribute for this product. If an attribute is a Configurable Attribute, this means that the customer will be able to select the value of the attribute from a drop-down in the front-end. It is customer configurable. For more information about Configurable Products, please refer to the Products section later in this chapter. Note: This drop-down is not related to the Apply To menu above. An attribute can be a Configurable Attribute even if it is not applied to Configurable Products. If this is the case, you will be able to select the attribute as a Configurable Product when creating a product, but you will not be able to see this attribute among the product’s other attributes in the New Product page.
Use in quick search - If you select Yes, Magento will search all the product values for this attribute when your customer uses the search bar in the header. If you select to use Color in the quick search, your customers will be able to type in green or blue and find products that match that color. For more details, see Chapter 5: Promotions, Marketing and Content Pages.
Use in advanced search - This is very similar to the quick search. However, in the Advanced Search, each attribute will have its own field, rather than there being one search field. If you select Yes, a field will be created for this attribute in the Advanced Search page. For more details, see Chapter 5.
Comparable on Front-end - If you select Yes, a row will be created for this attribute in the Compare Products pop-up window. For more details, see Chapter 5.
Use in Layered Navigation - Magento’s Layered Navigation allows your customers to filter down into a category’s products using any attribute that is “filterable” for Layered Navigation. The Layered Navigation menu will display in the left column of your category pages, and will contain all of the attributes which are filterable. Under each attribute will display the various values of that attribute. Clicking one of these values will filter the list of products in that category page so that only products matching that attribute value will display. There are two types of filterable attributes, which you can select from this drop-down: Filterable (with results) and Filterable (no results). This determines which values will display in the Layered Navigation menu. If you select Filterable (with results), only values that correspond to products in that category page will display in the menu (that is, only values that produce “results” when used as a filter). If you select Filterable (no results), all values that you’ve created in the Manage Label / Options tab will list, whether or not they correspond to any particular products in that category page (it includes values that do not produce “results” when used as a filter). If there are no filterable attributes in a particular category page, the Layered Navigation menu will not display. In order to make an attribute filterable, the Input Type must be either Dropdown, Multiple Select, or Price.
Position - This determines the position of the attribute in the Layered Navigation menu with respect to the other filterable attributes.
Visible on Catalog Pages on Front-end - This field only appears for Simple Attributes. On the product page in the front-end, there is a section called Additional Information, that displays below the Product Description section. The attribute name and value for all “visible” Simple Attributes will display in this section. If a product does not have any visible Simple Attributes (or if the product does not have any values selected for its Simple Attributes) there will be no Additional Information section on the front-end.
Manage Titles - In the Admin field, you must enter the name of the attribute as it will appear in the admin. For each Store View, you can specify a different name for this attribute. This is useful if you manage multiple Store Views with different languages. For example, in the Admin field, type Color; in the UK Store View field, type Colour; in the French Store View field, type Couleur. If you leave the field blank for any of the Store Views, the Admin Label will be used.
Manage Options - This section will only appear if the Input Type is Dropdown or Multiple Select. In order to have a drop-down or multiple select menu in the product page, you must have predetermined values to populate these menus. This is where the values for these menus are predetermined. This works very similar to the Manage Titles section above. For each value you wish to create, click Add Option. You can enter an unlimited number of values. For each value, you must enter a name in the Admin field, and you have the option to enter a different name for each Store view. For example, create two options. For the first option, enter Green in the Admin field; leave the UK Store View field blank, because it uses the same name; enter Vert in the French Store View field. For the second option, enter Blue in the Admin field; leave the UK Store View field blank; enter Bleu in the French Store View field. You will also have the option to select the position and which value(s) is the default. Enter a numerical value in the Position field, and this will determine the sort order of the values in the drop-down/multiple select menu relative to each other. For the Dropdown Input Type, you will have an Is Default radio button with which you can select one value. For the Multiple Select Input Type, you will have an Is Default checkbox with which you can select multiple values.
Note: Once the Attribute Set has been selected, it cannot be changed. You can change the attributes in a product by creating a new product and assigning a different Attribute Set. You can also edit the Attribute Set, and add or remove attributes, however this will affect all products associated to this Attribute Set.
You’ll notice how Magento ignores the version of the redundant file lower in hierarchy and recognizes only the version higher in hierarchy. This is because it’s already found the required file and need not search for it any longer, ergo terminating the search for that specific file while continuing the search for other required files yet to be found.