StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11834908
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-08-06T19:48:20.317
FavoriteCount
0
LastActivityDate
2012-08-06T19:48:20.317
LastEditDate
LastEditorUserId
0
OwnerUserId
1232302
ParentId
11832210
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
Okay, so you have two options. The quick and not so flexible SKU pattern way of matching products, or you could add a whole new product link relation to Magento. Obviously the last option costs more time but gives you the possibility to handle the relation from the admin and determine a display order within the batch. Option 1: Matching on SKU (easy, quick, perhaps a bit dirty) You could write a method that, let's say, takes the first 4 characters of your current product and then uses that to match the rest of the product database. Underneath is a mock-up version of how that code might look: <pre><code>$match = substr($product->getSku(), 0, 4); $resource = Mage::getModel('core/resource'); $read = $resource->getConnection('core_read'); $select = $read->select() ->from(array('e'=>$resource->getTableName('catalog/product')), 'entity_id') ->where("e.sku LIKE '" . $match . "%'"); $ids = $read->fetchAll($select); </code></pre> This will retrieve the ID's of the matching products. Then these id's can be loaded in a product collection, like: <pre><code>$_productCollection = Mage::getModel('catalog/product')->getCollection() ->addAttributeToSelect('<your_needed_product_attributes>') ->addAttributeToFilter('entity_id',array('in'=> <your_array_of_productids>)); Mage::getSingleton('catalog/product_status')->addSaleableFilterToCollection($_productCollection); Mage::getSingleton('catalog/product_visibility')->addVisibleInCatalogFilterToCollection($_productCollection); $_productCollection->addStoreFilter()->load(); </code></pre> Now you only have to loop through the collection and build your HTML. Option 2: Adding a new product relation Magento uses the table <code>catalog_product_link</code> to store all types of product relations. In <code>catalog_product_link_type</code> you add a new link type. This is needed to be able to insert new link type data in <code>catalog_product_link</code>. This new link type should be added via an upgrade script in your module. From this point on we need to make adjustments and additions to the Magento admin. Since this is a place for answers and not full blown module solutions I'm going to only mark the places which need our attention to add the new link type. Though, with the following information I don't think you will have too much trouble getting your new relation up and running. 1) Adding a tab for the new type to the menu on the product edit admin page. Like in <code>Mage_Adminhtml_Block_Catalog_Product_Edit_Tabs</code> we need to create a new tab for our link type. <pre><code> $this->addTab('combine', array( 'label' => Mage::helper('catalog')->__('Combine'), 'url' => $this->getUrl('*/*/combine', array('_current' => true)), 'class' => 'ajax', )); </code></pre> <code>*/*/combine</code> will route to the combine action of the <code>Mage_Adminhtml_Catalog_ProductController</code> controller. You probably want to use a different route to your own module, but I will stick to this one for this example. 2) To handle the page request <code>*/*/combine/</code> we need make this action available in a controller. You will find your code references in <code>Mage_Adminhtml_Catalog_ProductController</code> for this. <pre><code>/** * Get combine products grid and serializer block */ public function combineAction() { $this->_initProduct(); $this->loadLayout(); $this->getLayout()->getBlock('catalog.product.edit.tab.combine') ->setProductsUpsell($this->getRequest()->getPost('products_combine', null)); $this->renderLayout(); } </code></pre> We also need a action for handling later grid actions within this tab. <pre><code>/** * Get upsell products grid */ public function combineGridAction() { $this->_initProduct(); $this->loadLayout(); $this->getLayout()->getBlock('catalog.product.edit.tab.combine') ->setProductsRelated($this->getRequest()->getPost('products_combine', null)); $this->renderLayout(); } </code></pre> Furthermore this controller also houses a <code>->_initProductSave()</code> method in which product relations are fetched from the request and added to the 'to-be-saved' product object. You will need to add the underneath snippet by either extending the controller or using an observer for this. Your call. A <code>catalog_product_before_save</code> observer is the best way to do this. <pre><code> if (isset($links['combine']) && !$product->getCombineReadonly()) { $product->setCombineLinkData(Mage::helper('adminhtml/js')->decodeGridSerializedInput($links['combine'])); } </code></pre> In step 5 this data will again be picked up for further saving the new relations into the earlier mentioned <code>catalog_product_link</code> table. 3) The layout we try to build in step 2 won't do a lot without the following XML handles. <pre><code><adminhtml_catalog_product_combine> <block type="core/text_list" name="root"> <block type="<your_own_custom_block_for_product_link_type>" name="catalog.product.edit.tab.combine"/> <block type="adminhtml/widget_grid_serializer" name="upsell_grid_serializer"> <reference name="upsell_grid_serializer"> <action method="initSerializerBlock"> <grid_block_name>catalog.product.edit.tab.combine</grid_block_name> <data_callback>getSelectedCombineProducts</data_callback> <hidden_input_name>links[combine]</hidden_input_name> <reload_param_name>products_combine</reload_param_name> </action> <action method="addColumnInputName"> <input_name>position</input_name> </action> </reference> </block> </block> </adminhtml_catalog_product_combine> <adminhtml_catalog_product_combinegrid> <block type="core/text_list" name="root"> <block type="<your_own_custom_block_for_product_link_type>" name="catalog.product.edit.tab.combine"/> </block> </adminhtml_catalog_product_combinegrid> </code></pre> 4) With all that in place we need to create the block for our 'combine' type. This step is <code>fairly</code> easy. Take <code>Mage_Adminhtml_Block_Catalog_Product_Edit_Tab_Upsell</code> as a reference. We almost need an exact copy of this file. So place it in your module and rename all upsell to 'combine', or whatever name you are using for this relation. You need to place this block type at <code><your_own_custom_block_for_product_link_type></code> in step 3. 5) Extending Mage_Catalog_Model_Product_Link <code>Mage_Catalog_Model_Product_Link</code> is the file that holds all data regarding relation types. For instance which types are available and some logic for saving and loading the relation types. In your extend you need at least the following stuff: <ul> <li>A constant to define your relation type <code>const LINK_TYPE_COMBINE = 6;</code></li> <li>A <code>useCombineLinks</code> method like <code>useUpsellLinks</code></li> <li>A extend of the <code>saveProductRelations</code> method with the underneath addition. Though this is probably also doable via an proper event observer. <pre><code>$data = $product->getCombineLinkData(); if (!is_null($data)) { $this->_getResource()->saveProductLinks($product, $data, self::LINK_TYPE_COMBINE); } </code></pre></li> </ul> This snippet eventually will be triggered after a product is being saved. 6) Adding new relation logic to product model The last step to get the admin up and running is some logic that needs to be added to the product model (<code>Mage_Catalog_Model_Product</code>). You probably want to add these methods via an extend from your module on this model. You will need to add 4 methods, you can take the following as a reference, copy and rename them to your relation name. <ul> <li><code>getUpSellProducts</code></li> <li><code>getUpSellProductIds</code></li> <li><code>getUpSellProductCollection</code></li> <li><code>getUpSellLinkCollection</code></li> </ul> When you followed the above steps you should have a working admin for adding and handling this new product relation. Only thing left is having a block to use in the 'frontend' layout of your page. Again a good reference for this is <code>Mage_Catalog_Block_Product_List_Upsell</code>. I hope this gives you some good information to start with. Your choice which way to go. As said the second option is more work but gives your more flexibility through the admin and is a more robust solution.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreate new links between Magento Products
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim Hofman
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCreate new links between Magento Products
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.