<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
    
    <title>Knowledge Base</title>
    <link>http://www.magentocommerce.com/knowledge-base/</link>
    <description></description>
    <dc:language>en-us</dc:language>
    <dc:creator>michael@varien.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />


<item>
    <title>Tutorial: Creating Attributes (custom fields)</title>
    <link>http://www.magentocommerce.com/knowledge-base/entry/tutorial-creating-attributes-custom-fields</link>
    <description><![CDATA[<p>So you&#8217;re ready to add some custom data to your products?&nbsp; Luckily, this isn&#8217;t complicated.&nbsp; Today we&#8217;re going to create an attribute called &#8220;Hard Drive Size&#8221; for the external hard drives we&#8217;re about to sell in our store, and also an attribute called &#8220;Manufacturer&#8221; to use in our layered navigation.&nbsp; Let&#8217;s start with the simpler one - Hard Drive Size.&nbsp; In the front-end, this will appear on products like &#8220;Hard Drive Size:&nbsp; {whatever options you create and select}&#8221; - For example: &#8220;Hard Drive Size: 100GB&#8221;.
</p>
<h3>Creating a simple attribute - Hard Drive Size</h3><p>
<ol>
<li>Log into the Magento admin panel</li>
<li>Navigate to &#8220;Manage Attributes&#8221; under Catalog -> Attributes -> Manage Attributes</li>
<li>In the top right, click on &#8220;Add New Attribute&#8221;</li>
<li>You&#8217;re now on the Attribute edit page and <b>Properties</b> tab.&nbsp; It looks like this:</li>
</ol>
<br />
</p><h4>Properties Tab</h4><p>
<img src="http://www.magentocommerce.com/images/uploads/attributes_hd_attprops.jpg" style="border: 0;" alt="image" />
<br />
<ul>
<li><b>Attribute Identifier:</b>  This is the name of the attribute used by the system.&nbsp; Spaces can not be used in this field. We&#8217;ll type <i>hard_drive_size</i>.</li>
<li><b>Scope:</b> This determines the store level at which this attribute will save for all products. If you choose Global, and edit “Hard Drive Size” for product 123 in store A to “50 GB”, product 123’s hard drive size in store B (and any other stores) will also update to “50 GB”.&nbsp; For hard drive size, we’ll make it globally editable - we won’t sell the exact same hard drive in different stores with different sizes… that’s not possible.&nbsp; An example where we might want globally editable: no is “Price.” We might want to sell the Hard drive for $20 more in Store A.
<li><b>Catalog Input Type:</b>  This describes what kind of data the attribute will store. What&#8217;s set here determines how data entry for this attribute will take place.&nbsp; We&#8217;ll use <i>Text Field</i> since we want to enter the value for each product manually into a text field.</li>
<li><b>Default Value:</b> You can enter a value that will automatically populate for new products. We have many different hard drive sizes, so we will leave this blank.</li>
<li><b>Unique Value:</b> If &#8220;yes&#8221;, the data saved in this attribute has to be unique for each product. In this case, we&#8217;ll say &#8220;no&#8221;, because multiple hard drives can have the same hard drive size.</li>
<li><b>Values Required:</b> If &#8220;yes&#8221;, you will be required to enter data in this attribute field when saving a product that uses it.</li>
<li><b>Input Validation:</b>  This decides whether the data entered by the store owner is validated when the product is saved.&nbsp; If validation is set to &#8220;Digits&#8221;, we&#8217;ll only be able to enter 0-9 in this field.&nbsp; An error will be thrown if we try to put letters in the field.&nbsp; In the case of Hard Drive Size, we don&#8217;t need validation on this field.
<li><b>Apply To:</b> This determines for which Product Types this attribute will display.&nbsp; For example, <b>price</b> wouldn&#8217;t make sense in a grouped product, as each Simple Product associated to the Grouped Product will have its own price.&nbsp; Therefore, you can set <b>price</b> to not apply to grouped product, and you won&#8217;t be scratching your head over what numbers to write in there.</li>
</ul>
<li><b>Use in quick/advanced search:</b>  If &#8220;yes&#8221;, the data saved in this attribute will be searchable in the front-end in the quick search and advanced search, respectively (ie, if i type &#8220;100GB&#8221; it should return all products with this value saved in the <i>Hard Drive Size</i> field).</li>
<li><b>Comparable on Front-end:</b>  If &#8220;yes&#8221;, this attribute will be displayed in a product comparison, so long as at least one product in the Compare List contains a value for this attribute.</li>
<li><b>Use in Layered Navigation:</b>  If &#8220;filterable&#8221;, this data will be available as a filter in Magento&#8217;s layered navigation. Filterable (with results) means that only values that are associated to specific products in a given category page will list in the Layered Navigation menu. Filterable (no results) means that all existing values for an attribute will display in the menu, even if using this as a filter will produce no results. There&#8217;s one condition to use attributes in layered navigation - the <b>Input Type</b> has to be Dropdown, Multiple Select, or Price.</li>
<li><b>Position:</b> This determines the position of this attribute in the Layered Nav menu.</li>
<li><b>Visible on Catalog Pages on Front-end:</b>  If &#8220;no&#8221;, this attribute will not be displayed in the product info page. The &#8220;visibility&#8221; only controls whether or not the attribute displays in the front-end. Keep in mind - if you set an attribute to &#8220;Visible: No&#8221;, and leave it as &#8220;Comparable: Yes&#8221;, this attribute will still show up in comparison charts.</li>
</ul>
<br />
</p><h4>Manage Label / Options</h4><p>
<img src="http://www.magentocommerce.com/images/uploads/attributes_hd_labels.jpg" style="border: 0;" alt="image" />
<br />
Under this tab, you can enter the label for the attribute in the front-end.&nbsp; If you control stores in multiple languages, you can enter the label in each language under this tab.&nbsp; If a store&#8217;s label is blank, this store will look to the <b>default</b> label and use this one.&nbsp; Here we&#8217;ll enter &#8220;Hard Drive Size&#8221; under &#8220;Default&#8221;.
</p>
<h4>Frontend Properties</h4><p>
<a href="http://www.magentocommerce.com/images/uploads/attributes_front-end.gif" onclick="window.open('http://www.magentocommerce.com/images/uploads/attributes_front-end.gif','popup','width=700,height=600,scrollbars=no,resizable=yes,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false">Click here to see how the attribute appears in the front-end.</a>
</p>
<h3>Creating an attribute with controlled options - Manufacturer</h3><p>
The next attribute we&#8217;ll create is going to be &#8220;Manufacturer.&#8221;  Let&#8217;s say you carry televisions by 4 manufacturers.&nbsp; Rather than having to type the name of each manufacturer, why not just make it an attribute and assign four possible options to it:&nbsp; Varien, Panasonic, JVC, and Sony.
</p>
<h4>Attribute Properties</h4><p>
For our &#8220;Manufacturer&#8221; attribute, we&#8217;ll use <b>Catalog Input Type</b> &#8220;Dropdown&#8221; since we want this attribute to have limited data.&nbsp; Using &#8220;Dropdown&#8221; also enables us to show the attribute as a layered navigation filter.&nbsp; Below is what the Properties tab looks like for &#8220;Manufacturer&#8221;:
<br />
<img src="http://www.magentocommerce.com/images/uploads/attributes_manu_attprops.jpg" style="border: 0;" alt="image" />
</p>
<h4>Manage Label/Options</h4><p>
Since we select <b>Dropdown</b> as the input type, we have the ability to create the possible options for this attribute from this tab.&nbsp; Under &#8220;Manage Labels&#8221; tab is &#8220;Manage Options&#8221;.&nbsp; Press &#8220;Add Option&#8221; to add an option.&nbsp; It functions similarly to labels - any blank fields will look to the &#8220;default&#8221;.&nbsp; You can also set the positions of each value and select one of the values as the default. See below for how it looks after adding four manufacturers as options.
<br />
<img src="http://www.magentocommerce.com/images/uploads/attributes_manu_labels.jpg" style="border: 0;" alt="image"  />
</p>
<h3>Applying to a product</h3><p>
Now, to apply this selectable attribute to a product, just add it to an attribute set and create a new product using this set.&nbsp; Below is a simplified example of the General tab of creating a new product in the admin:
<br />
<img src="http://www.magentocommerce.com/images/uploads/attributes_manu_product.gif" style="border: 0;" alt="image" width="541" height="281" />
<br />
</p><h4>Front-end</h4>
<p>
<a href="http://www.magentocommerce.com/images/uploads/attributes_front-end.gif" onclick="window.open('http://www.magentocommerce.com/images/uploads/attributes_front-end.gif','popup','width=668,height=544,scrollbars=no,resizable=yes,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false">Click here to see how the attribute appears in the front-end.</a>
<br />
<a href="http://www.magentocommerce.com/images/uploads/attributes_front-end.gif" onclick="window.open('http://www.magentocommerce.com/images/uploads/attributes_front-end.gif','popup','width=668,height=544,scrollbars=no,resizable=yes,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.magentocommerce.com/images/uploads/attributes_front-end_s.gif" style="border: 0;" alt="image" width="359" height="46" /></a>
</p>
<p>
Mmm, nice.&nbsp; Now you&#8217;ll never have to type these manufacturers again.&nbsp; Also, data entry will be more consistent, since it is impossible to have a typo or spelling error if a drop-down is used.
</p>]]></description>
    <dc:language>en-us</dc:language>
    <dc:creator>johannes@varien.com</dc:creator>
    <dc:rights>Copyright 2007</dc:rights>
    <dc:date>2007-08-09 T;04:06:01-08:00</dc:date>
</item>
<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.magentocommerce.com/knowledge-base/tutorial-creating-attributes-custom-fields/"
    trackback:ping="http://www.magentocommerce.com/trackback/113/"
    dc:title="Tutorial: Creating Attributes (custom fields)"
    dc:identifier="http://www.magentocommerce.com/knowledge-base/113/"
    dc:subject="Catalog"
    dc:description=""
    dc:creator="johannes"
    dc:date="2007-08-09 04:06:01 AM GMT" />
</rdf:RDF>
--> 


    <item>
      <title>Comment by Ross</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>@tierralogic - the posts that have the blue gradient are the Magento team (eg. johannes).
</p>
<p>
If you want to try it yourself, go ahead!&nbsp; Although if they are working on it, it might be worth waiting a couple of weeks for the next release (release candidate I think) - and see what changes have been made.
</p>
<p>
At the moment there is no place to submit code.&nbsp; It has been said that a development community (and ways to contribute code - and sell add-ons and services) will be launched after the production release (when the APIs etc are more stable and documented).
</p>]]></description>
      <content:encoded><![CDATA[<p>@tierralogic - the posts that have the blue gradient are the Magento team (eg. johannes).
</p>
<p>
If you want to try it yourself, go ahead!&nbsp; Although if they are working on it, it might be worth waiting a couple of weeks for the next release (release candidate I think) - and see what changes have been made.
</p>
<p>
At the moment there is no place to submit code.&nbsp; It has been said that a development community (and ways to contribute code - and sell add-ons and services) will be launched after the production release (when the APIs etc are more stable and documented).
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by tierralogic</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>so how does this work? are any of the responding parties part of the magento team? 
</p>
<p>
basicly, if i wanted to try and do this myself, which i think i can do with some effort, should i just go ahead and give it a shot and then what? submit the code to the group or smth? 
</p>
<p>
sorry just a little new to this! <img src="http://www.magentocommerce.com/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;padding:0;" />
</p>]]></description>
      <content:encoded><![CDATA[<p>so how does this work? are any of the responding parties part of the magento team? 
</p>
<p>
basicly, if i wanted to try and do this myself, which i think i can do with some effort, should i just go ahead and give it a shot and then what? submit the code to the group or smth? 
</p>
<p>
sorry just a little new to this! <img src="http://www.magentocommerce.com/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;padding:0;" />
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by DragonZoul</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>The concept is fine. We&#8217;ll see how far &#8220;attrbiutes&#8221; may be used, especially on the programmatric way in &#8220;my own&#8221; new classes ...
<br />
what other types of attributes are planed?
</p>]]></description>
      <content:encoded><![CDATA[<p>The concept is fine. We&#8217;ll see how far &#8220;attrbiutes&#8221; may be used, especially on the programmatric way in &#8220;my own&#8221; new classes ...
<br />
what other types of attributes are planed?
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by Ross</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>Great to hear!&nbsp; It sounds like not much is being overlooked!
</p>
<p>
Thanks for the reply.
</p>]]></description>
      <content:encoded><![CDATA[<p>Great to hear!&nbsp; It sounds like not much is being overlooked!
</p>
<p>
Thanks for the reply.
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by johannes</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>Yes, it would be great to upload files!&nbsp; In fact, we are working on supporting this type of attribute <img src="http://www.magentocommerce.com/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;padding:0;" />
</p>]]></description>
      <content:encoded><![CDATA[<p>Yes, it would be great to upload files!&nbsp; In fact, we are working on supporting this type of attribute <img src="http://www.magentocommerce.com/images/smileys/smile.gif" width="19" height="19" alt="smile" style="border:0;padding:0;" />
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by Ross</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>This is great, but I do agree with the previous comment - it would be nice to be able to have an attribute of type &#8216;file&#8217; (or similar).&nbsp; There is the &#8216;image&#8217; type of attribute (which is close), but a more general purpose one would be good.
</p>
<p>
For example, a shop selling CDs may wish to have a track listing with the track titles linked to preview audio samples.&nbsp; If attributes could do that it would be really great!
</p>]]></description>
      <content:encoded><![CDATA[<p>This is great, but I do agree with the previous comment - it would be nice to be able to have an attribute of type &#8216;file&#8217; (or similar).&nbsp; There is the &#8216;image&#8217; type of attribute (which is close), but a more general purpose one would be good.
</p>
<p>
For example, a shop selling CDs may wish to have a track listing with the track titles linked to preview audio samples.&nbsp; If attributes could do that it would be really great!
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>

    <item>
      <title>Comment by tierralogic</title>
      <link>{url_as_link}</link>
      <description><![CDATA[<p>how can i add an upload field for a file, and have the system show a link to it on the front end? this would be for a user manual, etc, like a pdf file. 
</p>
<p>
thanks!
</p>]]></description>
      <content:encoded><![CDATA[<p>how can i add an upload field for a file, and have the system show a link to it on the front end? this would be for a user manual, etc, like a pdf file. 
</p>
<p>
thanks!
</p>]]></content:encoded>
    <dc:date>2008-08-15 T;00:11:01-08:00</dc:date>
    </item>


</channel>
</rss>