I have not drilled down to the details of collection, untill today when I really need it! Do you think its very late? because I have been into Magento for more than a year now!. Better late than never! So, I got the way of working out my situation. Here is how I created a collection from Magento’s “Magical Class” Varien_Data_Collection. I call this “Magical Class”, because it worked like a Magic to me

$collection=new Varien_Data_Colllection();
$collection->addItem($objProduct);

There are various other functions in this class you might need to “work around” a problem. So, have a look and certainly do comment if you also think this class to be a Magical Class!

$order = Mage::getModel('sales/order')->load($order_id);
$items = $order->getAllItems();
$itemcount=count($items);
$name=array();
$unitPrice=array();
$sku=array();
$ids=array();
$qty=array();
foreach ($items as $itemId => $item)
{
	$name[] = $item->getName();
	$unitPrice[]=$item->getPrice();
	$sku[]=$item->getSku();
	$ids[]=$item->getProductId();
	$qty[]=$item->getQtyToInvoice();
}

Hope this might “just” help somebody in need.

I came this condition recently, and found out that Magento has functions to chanage your Grid (in Admin) to XLS files and if you dig more than you can change your data Array to XLS file using Magento’s function.

First let me say you about exporing data from the Admin Grid you have already populated. You need do the following in your grid Block’s _prepareColumn function.

$this->addExportType('router/controller/action', Mage::helper('reports')->__('Excel'));

And in your controller you will have to do this.

/**
     * Export grid to Excel XML format in Controller
	 * @class Mynamespace_Mymodule_Adminhtml_controllerController
     */
    public function actionAction()
    {
        $fileName   = 'grid.xls';

		/**
		* This is the part where Grid Columns and Data are created as Excel XML and returned as stream.
		* The implementation of this code is done in the parent class of Grid Mynamespace_Mymodule_Block_Adminhtml_Grid
		* And that class should be Mage_Adminhtml_Block_Widget_Grid
		*/

        $content    = $this->getLayout()->createBlock('mymodule_adminhtml/mygrid_grid')
            ->getExcel($fileName);

    /**
	* This is for Force Download implemented below
	*/
	$this->_prepareDownloadResponse($fileName, $content);
    }

	/**
	 * Force Download Code block in your controller
     * Declare headers and content file in responce for file download
     *
     * @param string $fileName
     * @param string $content set to null to avoid starting output, $contentLength should be set explicitly in that case
     * @param string $contentType
     * @param int $contentLength explicit content length, if strlen($content) isn't applicable
     * @return Mage_Adminhtml_Controller_Action
     */
    protected function _prepareDownloadResponse($fileName, $content, $contentType = 'application/octet-stream', $contentLength = null)
    {
        $session = Mage::getSingleton('admin/session');
        if ($session->isFirstPageAfterLogin()) {
            $this->_redirect($session->getUser()->getStartupPageUrl());
            return $this;
        }
        $this->getResponse()
            ->setHttpResponseCode(200)
            ->setHeader('Pragma', 'public', true)
            ->setHeader('Cache-Control', 'must-revalidate, post-check=0, pre-check=0', true)
            ->setHeader('Content-type', $contentType, true)
            ->setHeader('Content-Length', is_null($contentLength) ? strlen($content) : $contentLength)
            ->setHeader('Content-Disposition', 'attachment; filename=' . $fileName)
            ->setHeader('Last-Modified', date('r'));
        if (!is_null($content)) {
            $this->getResponse()->setBody($content);
        }
        return $this;
    }

Now you can export your Grid data to XLS sheet. But what about your array you are not displaying in the grid? This should be fun too.. for you now.. because it was not fun for me to find out in the first hand .

Lets take the same controller now.

 /**
     * Export Array to Excel XML format in Controller
	 * @class Mynamespace_Mymodule_Adminhtml_controllerController
     */
    public function actionAction()
    {
		$filename   = 'array.xls';
		$exportData=Mage::getSingleton("adminhtml/session")->getMyData();

		/**
		* Example Data Format
		* $data[0]['product_id']=10
		* $data[0]['product_name']=HTC Diamond
		* $data[0]['vendor_name']=HTC JMKYZY
		* $data[1]['product_id']=11
		* $data[1]['product_name']=HTC Ruby
		* $data[1]['vendor_name']=HTC JMKYZY
		*
		*/

		// Setting headers columns
			$data[0]=array($this->__("Product ID"),$this->__("Product Name"),$this->__("Vendors"));

		// Setting Column Data
			$i=1;
			foreach($exportData as $key=>$value){
				$data[$i]=array($value['product_id'],$value['product_name'],$value['vendor_name']);
				$i++;
			}

		// Unparsing in Excel Format
			$xmlObj = new Varien_Convert_Parser_Xml_Excel();
			$xmlObj->setVar('single_sheet', $filename);
			$xmlObj->setData($data);
			$xmlObj->unparse();
			$content=$xmlObj->getData();

			// Force Download
			$this->_prepareDownloadResponse($filename,$content);
	}

So by comparing the two export controller methods, you can see that the Admin Grid’s Parent already has the functionality to get data from Grid and set that data to Varien_Convert_Parser_Xml_Excel Object and unparse its. As I said we need to dig further to know what going on inside Magento.

Happy Coding.

But today I was looking at fontis’s blog http://www.fontis.com.au/blog/magento/debugging-with-xdebug and they had indeed used XDebugger and are debugging Magento through command line. So, I thought why not give it a try once again! And as you have already expected i was successfull today!! Wasn’t easy though

Here’s what I’ve done to get it working on WAMP. Before getting this done I assume you have created a new PHP Project and imported all files, beforehand in Eclipse.

Step 1. A very good explanation of downloading Eclipse PDT with Zend Debugger can be found here Installing_the_Zend_Debugger

Step 2. Configuring the Zend Debugger can also be found on same location but I would like to emphasize on its setting here, coz I missed myself on first run

Use these settings for For Zend debugger in php.ini

[Zend]
zend_extension_ts=D:/wamp/bin/php/php5.2.5/ext/ZendDebugger.dll
zend_debugger.allow_hosts=127.0.0.1
zend_debugger.expose_remotely=always

You should not forget to enable Zend Debugger extension on WAMP. Now restart Wamp. You are now well set with Eclipse PDT and Zend Debugger. Next thing you need to do is make debugging settings in your Eclipse.

Step 3. In you Eclipse Go to Windows–>Preference–>Debug and set as follows

Step 4. Then Windows–>Preference–>Server and set as follows

While setting Server configuration you will be prompt to add server path in path mapping, place that relative to your www root Example: /mysite (which will open as localhost/mysite) and select the files in your workspace.

Step 5. Now all your settings are done. Now let me tell you about debugging a Block Class of Magento, say Mage_Catalog_Block_Product_List. Go to the class file and add a breakpoint anywhere inside _getProductCollection function.

Step 6. Go to Run–>Open Run Dialog and configure as following

Step 7. All set to go now, Run profile as web page Run–>Debug As–>PHP Webpage.

You can now see PHP Debug perspective, and use Step Over or Step Into to debug your values. Here is what I got.

Hope this might be a life changer.. at least it is for me!

$collection = Mage::getResourceModel('customer/customer_collection')
				->addNameToSelect()
				->addAttributeToSelect('email')
				->addAttributeToSelect('created_at')
				->addAttributeToSelect('group_id')
				->joinAttribute('billing_street', 'customer_address/street', 'default_billing', null, 'left')
				->joinAttribute('billing_postcode', 'customer_address/postcode', 'default_billing', null, 'left')
				->joinAttribute('billing_city', 'customer_address/city', 'default_billing', null, 'left')
				->joinAttribute('billing_telephone', 'customer_address/telephone', 'default_billing', null, 'left')
				->joinAttribute('billing_fax', 'customer_address/fax', 'default_billing', null, 'left')
				->joinAttribute('billing_region', 'customer_address/region', 'default_billing', null, 'left')
				->joinAttribute('billing_country_code', 'customer_address/country_id', 'default_billing', null, 'left')

				->joinAttribute('shipping_street', 'customer_address/street', 'default_shipping', null, 'left')
				->joinAttribute('shipping_postcode', 'customer_address/postcode', 'default_shipping', null, 'left')
				->joinAttribute('shipping_city', 'customer_address/city', 'default_shipping', null, 'left')
				->joinAttribute('shipping_telephone', 'customer_address/telephone', 'default_shipping', null, 'left')
				->joinAttribute('shipping_fax', 'customer_address/fax', 'default_shipping', null, 'left')
				->joinAttribute('shipping_region', 'customer_address/region', 'default_shipping', null, 'left')
				->joinAttribute('shipping_country_code', 'customer_address/country_id', 'default_shipping', null, 'left')
				->joinAttribute('taxvat', 'customer/taxvat', 'entity_id', null, 'left');

Hope this helps somebody!

Here is the way. The code comments are self explanatory I guess!!

/**
	 * Load Product you want to get Super attributes of
	 */
	$product=Mage::getModel("catalog/product")->load(52520); 

	/**
	 * Get Configurable Type Product Instace and get Configurable attributes collection
	 */
	$configurableAttributeCollection=$product->getTypeInstance()->getConfigurableAttributes();

	/**
	 * Use the collection to get the desired values of attribute
	 */
	foreach($configurableAttributeCollection as $attribute){
		echo "Attr-Code:".$attribute->getProductAttribute()->getAttributeCode()."<br/>";
		echo "Attr-Label:".$attribute->getProductAttribute()->getFrontend()->getLabel()."<br/>";
		echo "Attr-Id:".$attribute->getProductAttribute()->getId()."<br/>";
	}

Happy Codding!

Assumming that first part, i.e. the saving of options are already done, you will now need to create a product attributes through SQL Setup

<?php
$installer = $this;
$setup = new Mage_Eav_Model_Entity_Setup('core_setup');
$installer->startSetup();
$setup->addAttribute('catalog_product', 'my_attribute', array(
    'input'         => 'multiselect',
	'required'		=> false,
    'type'          => 'text',
    'label'         => 'My Attribute Label',
    'source'        => 'mymodule/source_option',
    'backend'       => 'mymodule/backend_option',
    'global'        => Mage_Catalog_Model_Resource_Eav_Attribute::SCOPE_STORE,
    'visible'       => 1,
));
$installer->startSetup();
$installer->endSetup();

The source of the attribute is set to some Model, Ynamespace_Mymodule_Model_Source_Option. This file should look like this.

<?php
class Ynamespace_Module_Model_Source_Option
extends Mage_Eav_Model_Entity_Attribute_Source_Table
{
	public function getAllOptions()
	{
		return $this->getOptionFromTable();
	}

	private function getOptionFromTable(){
		$return=array();
		$col=Mage::getModel("modules/model")->getCollection();
		/**
		* Given that table has column as id,title,image_name
		*
		*/
		foreach($col as $row){
			array_push($return,array('label'=>$row->getTitle(),'value'=>$row->getId()));
		}
		return $return;

	}

	public function getOptionText($value)
	{
		$options = $this->getAllOptions();
		foreach ($options as $option) {
			if(is_array($value)){
				if (in_array($option['value'],$value)) {
					return $option['label'];
				}
			}
			else{
				if ($option['value']==$value) {
					return $option['label'];
				}
			}

		}
		return false;
	}
}

As you can see that the option are retrieved from the custom table in label and value pair. Remember that getAllOptions is called during product export/import as well.

Next important thing you must know is the backend model. Backend model comes into play when you save and load the product. Let me explain. Let us consider a case when you are saving product. The option of this multiselect attribute is sent in post variables as array, but the values cannot be saved as array, either you have to serialize it or implode it into string to save. So to do this change, backend model is there. Similarly, on load you need to explode or unserialize the data from the database to array. So the major functions of backend model are beforeSave() and afterLoad(), which are triggerd as product is saved or loaded. The backend model should look like this:

<?php
class Ynamespace_Modules_Model_Backend_Option
    extends Mage_Eav_Model_Entity_Attribute_Backend_Abstract
{
    /**
     * Before Attribute Save Process
     *
     * @param Varien_Object $object
     * @return Mage_Catalog_Model_Category_Attribute_Backend_Sortby
     */
    public function beforeSave($object) {
        $attributeCode = $this->getAttribute()->getName();
        if ($attributeCode == 'my_attribute') {
            $data = $object->getData($attributeCode);
            if (!is_array($data)) {
                $data = array();
            }
            $object->setData($attributeCode, join(',', $data));
        }
        return $this;
    }

    public function afterLoad($object) {
        $attributeCode = $this->getAttribute()->getName();
        if ($attributeCode == 'my_attribute') {
            $data = $object->getData($attributeCode);
            if ($data) {
                $object->setData($attributeCode, split(',', $data));
            }
        }
        return $this;
    }
}

Now you are all set, you should have the values of the multiselect attribute saved in database joined by comma seperated values and while on load those values will be exploded as array. Last thing you can do is export the product data using default profile and check if the error shows up or not regarding this attributes. Must not! I think I’ve checked its integrity with import and export as well. If it shows any, feel free to contact me.

<global>
     <ymodel>
            <class>YNamespace_YModule_Model</class>
	     <resourceModel>quotes_mysql4</resourceModel>
     </ymodel>
<quotes_mysql4>
                <class>YNamespace_Ymodule_Model_Mymodel</class>
                <entities>
			<mymodel>
				<table>ymodel_ytable</table>
			</mymodel>
		</entities>
      </quotes_mysql4>
</global>

Then Create a Model

<?php
class YNamespace_Ymodule_Model_Mymodel extends Mage_Core_Model_Abstract
{
	public function _construct()
	{
		parent::_construct();
		$this->_init('ymodel/mymodel');
	}
}

As you can see in constructor of this class it inits the model (tag) defined in the config file. As model uses Resources, you now need to create a resource the module uses.

<?php

class Ynamespace_Ymodel_Model_Mysql4_Ymodel extends Mage_Core_Model_Mysql4_Abstract
{
    public function _construct()
    {
        $this->_init('ymodel/mymodel', 'id');
    }
}	

So using this resource you now can access Table and add/alter. But you must not explicitly create a object of this class to do that. Creating a model of class above will make this resource usable.

$model=Mage::getModel("ymodel/mymodel")
	->setName("Subesh")
	->setLastname("Pokhrel")
      ->save();

This will create a new row in table now given that name and lastname is the columns of the table. To edit row of a table do the following

$model=Mage::getModel("ymodel/mymodel")->load($id)
	->setName("Subesh")
	->setLastname("Pokharel")
      ->save();

Now to select, there is another procedure. Before that let me tell about collection. Think collections as the array of objects.When you Query in database you get result as collections in Magento and every row resulting from the query is a different Object.To create a collection

<?php

class Ynamespace_Ymodel_Model_Mysql4_Mymodel_Collection extends Mage_Core_Model_Mysql4_Collection_Abstract
{
    public function _construct()
    {
        parent::_construct();
        $this->_init('ymodel/mymodel');
    }
}

To Select All the row of Table

$allCollection=Mage::getModel("ymodel/mymodel")->getCollection();

You can add filters in the above query as required.
To get individual Row you can just loop through the collection

foreach($allCollection as $objRow){
	print_r($objRow);
}

Hope this helps if any one is in need… and @inchoo..please don’t twitt this as any other..link…you find in a weekend… .

/**Using the Previously created DB**/
mysql> use magento

/**Import the Dumpped SQL**/
mysql>source pathToMagentoRoot/mySql.sql

So after the command is executed I had the whole DB on production enviornment. Similarly we can also import dumpped data of Production on Local database running on WAMP server.
To import Dumpped SQL data on WAMP, first create a database, say magento and then use the following commands

/**
	Using the Previously created DB.
	-p password part is optional if you have not configured password for MYSQL locally
	-u Username (root by default)
**/

mysql> C:\wamp\bin\mysql\mysql5.0.51b\bin>mysql.exe -use magento -u root -p password 

/**Import the Dumpped SQL**/
mysql>source pathToSQLSource/mySql.sql

By Now we have the database synced between Local and Production. Next is configuring the database name used by Magento. Browse to app/etc/local.xml and change in the following part.

    <connection>
                    <host><![CDATA[localhost]]></host>
                    <username><![CDATA[username_here]]></username>
                    <password><![CDATA[password_here]]></password>
                    <dbname><![CDATA[databasename_here]]></dbname>
                    <active>1</active>
    </connection>

Finally, browsed through table core_config_data and find value of path: web/unsecure/base_url and path: web/secure/base_url and change their values accordingly.

Now I had my Shop enviorment switched. Most work for you as well. LOL.

// Directly in the PHTML where you want to show the block
<?php
echo $this->getLayout()->createBlock("module/block")->setTemplate("module/page.phtml")->toHtml();
?>

What we have actually done is just load the layout and create an instance of a block class defined inside its paramerter, then assigned a template to the block and finally echoed as html. Simple! The code above will be equivalent to what we do as following in layout and in template file.

// In layout
<block type="module/block" name="module.name" template="module/page.html"/>

<?php
// In parent PHTML
$this->getChildHtml("module.name");
?>

May be helpful!