I will try to describe this issue by taking a case of changing the Magento’s login functionality to a Ajax powered login functionality. So after this you will be able to implement a login function in a pop-up div in any page, unlike the default Magento’s seperate login page. I will leave the pop-up div part to you and get started with the real business (AJAX and JSON).

Presuming that you will use Mini-Login form. Here is how you proceed.

1. Change Submit type button to Button type button.
2. Register OnClick Javascript event of that button and its Handler
3. In the Handler function call Ajax Request for login
4. Show Error Message or redirect to customer Dashboard

Your mini.login.phtml should be like this

<form action="<?php //echo $this->getPostActionUrl() ?>" id="mini-login-form" method="post">
    <fieldset>
        <p><label><?php echo $this->__('Email') ?>:</label> <input name="login[username]" class="input-text" /></p>
        <p><label><?php echo $this->__('Password') ?>:</label> <input name="login[password]" class="input-text" /></p>
        <p><input type="button" onClick="handlerFunction()" value="<?php echo $this->__('Login') ?>" /></p>
    </fieldset>
</form>

<script type="text/javascript">
<!--
function handlerFunction(){

// Write These codes only after form Validation

// Making Ajax Request
		var request = new Ajax.Request(
			//Defining Ajax Request URL, We are calling custom Controller Ns_Mylogin_AccountController Class (Defined Below)
        	'<?php echo $this->getUrl("mylogin/account/loginPost") ?>',
           	{
            	method: 'post',
                onComplete: function(transport){ // Defining Complete Callback Function

                	// Getting Ajax Response Text Which is JSON Object
                	var jsonResponse=transport.responseText;
                	//Checking JSON Objects property and performing related action
                	// You will understand the response Text format after going through the controller description (Below)
                	if(jsonResponse.error){
                		alert("Error Occured");
						return false;
                	}
                	else{
                		window.location.href=jsonResponse.url;
                	}
                },
                parameters: Form.serialize($("mini-login-form"))	// Seriallizing the form input values
        	}
        );
}
//-->
</script>

Please see inline comments for better understanding. Now our next set should be setting up our custom controller. I’ll not get into details of setting up modules and all but directly to our controller class Ns_Mylogin_AccountController. What I’ve done is just taken the core’s loginPostAction function of Mage_Customer_AccountController and added some codes there. Please see there is a comment on each line added apart from the default Magento’s core code.

<?php
require_once("Mage/Customer/controllers/AccountController.php");
class Ns_Mylogin_AccountController extends Mage_Customer_AccountController{
	/**
	 * Login post action
	 * @return JSON Object
	 */
	public function loginPostAction()
	{
		// Added Line #1
		$result["error"]=0;

		$session = $this->_getSession();

		if ($this->getRequest()->isPost()) {
			$login = $this->getRequest()->getPost('login');
			if (!empty($login['username']) && !empty($login['password'])) {
				try {
					$session->login($login['username'], $login['password']);
					if ($session->getCustomer()->getIsJustConfirmed()) {
						$this->_welcomeCustomer($session->getCustomer(), true);
					}
				} catch (Mage_Core_Exception $e) {
					switch ($e->getCode()) {
						case Mage_Customer_Model_Customer::EXCEPTION_EMAIL_NOT_CONFIRMED:
							//Added Line #2
							$result["error"]=1;
							$message = Mage::helper('customer')->__('This account is not confirmed. <a href="%s">Click here</a> to resend confirmation email.', 						Mage::helper('customer')->getEmailConfirmationUrl($login['username']));
							break;
						case Mage_Customer_Model_Customer::EXCEPTION_INVALID_EMAIL_OR_PASSWORD:
							//Added Line #3
							$result["error"]=1;
							$message = $e->getMessage();
							break;
						default:
							//Added Line #4
							$result["error"]=1;
							$message = $e->getMessage();
					}
					$session->addError($message);
					$session->setUsername($login['username']);
				} catch (Exception $e) {
					// Mage::logException($e); // PA DSS violation: this exception log can disclose customer password
				}
			} else {
				//Added Line #5
				$result["error"]=1;
				$session->addError($this->__('Login and password are required'));
				//Added Line #6
				$this->getResponse()->setBody(Mage::helper('core')->jsonEncode($result));
			}
		}
		//Added Line #7
		$result["url"]=$this->_loginPostRedirect();
		//Added Line #8
		$this->getResponse()->setBody(Mage::helper('core')->jsonEncode($result));
	}

What I’ve done is added an array $result that will hold value if there is error or not while processing the user’s request. If there is error that array will hold $result['error']=1 else it will be as initiallized in Added Line #1. From Added Line #2 through Added Line #5, we have various condition to check for error and set our $result variable.

On Added Line #7 we have called another function (which we we rewrite as well) that will give us the url location identifying which location should be redirect after successful login. The implementation of function is given below. Finally in Added Line #8 and Line #6 we have encoded our $result array into JSON format and send as the response.

For visuallization our $result array will be one of the following.

1. Case (No Error) : $result["error"]=0; $result["url"]=”SOME Redirect URL”
2. Case (Error) : $result["error"]=1;

This JSON encoded response will be then used by the ajax call back function defined and perform related action.

Here’s the _loginPostRedirect() function which I mentioned (Added Line #7).

/**
	 * Define target URL and redirect customer after logging in
	 */
	protected function _loginPostRedirect()
	{
		$session = $this->_getSession();

		if (!$session->getBeforeAuthUrl() || $session->getBeforeAuthUrl() == Mage::getBaseUrl() ) {

			// Set default URL to redirect customer to
			$session->setBeforeAuthUrl(Mage::helper('customer')->getAccountUrl());

			// Redirect customer to the last page visited after logging in
			if ($session->isLoggedIn())
			{
				if (!Mage::getStoreConfigFlag('customer/startup/redirect_dashboard')) {
					if ($referer = $this->getRequest()->getParam(Mage_Customer_Helper_Data::REFERER_QUERY_PARAM_NAME)) {
						$referer = Mage::helper('core')->urlDecode($referer);
						if ($this->_isUrlInternal($referer)) {
							$session->setBeforeAuthUrl($referer);
						}
					}
				}
				else if ($session->getAfterAuthUrl()) {
					$session->setBeforeAuthUrl($session->getAfterAuthUrl(true));
				}
			} else {
				$session->setBeforeAuthUrl(Mage::helper('customer')->getLoginUrl());
			}
		} else if ($session->getBeforeAuthUrl() == Mage::helper('customer')->getLogoutUrl()) {
			$session->setBeforeAuthUrl(Mage::helper('customer')->getDashboardUrl());
		}
		else {
			if (!$session->getAfterAuthUrl()) {
				$session->setAfterAuthUrl($session->getBeforeAuthUrl());
			}
			if ($session->isLoggedIn()) {
				$session->setBeforeAuthUrl($session->getAfterAuthUrl(true));
			}
		}
		// Changed Here
		return $session->getBeforeAuthUrl(true);
	}

You can download the code From Here.

Hope it helps! Happy Coding.

<core>
	<rewrite>
		<locale>Namespace_Module_Model_Locale</locale>
	</rewrite>
</core>

Then in Namespace_Module_Model_Locale class you can add the following code.

class Namespace_Module_Model_Locale extends Mage_Core_Model_Locale{
	/*
	* Code: subesh.com.np
	*/

    public function currency($currency)
    {
    	Varien_Profiler::start('locale/currency');
        if (!isset(self::$_currencyCache[$this->getLocaleCode()][$currency])) {
            try {
                $currencyObject = new Zend_Currency($currency, $this->getLocale());

				// Additionally Added Code
				// The options array's position key has other values as well.

				// 	Zend_Currency::STANDARD
				// 	Zend_Currency::RIGHT
				//	Zend_Currency::LEFT     

				$options = array(
                       'position'	=> Zend_Currency::RIGHT
                );

				$currencyObject->setFormat($options);

				// END Additionally Added Code

            } catch (Exception $e) {
                $currencyObject = new Zend_Currency($this->getCurrency(), $this->getLocale());
                $options = array(
                        'name'      => $currency,
                        'currency'  => $currency,
                        'symbol'    => $currency
                );
                $currencyObject->setFormat($options);
            }

            self::$_currencyCache[$this->getLocaleCode()][$currency] = $currencyObject;
        }
        Varien_Profiler::stop('locale/currency');
        return self::$_currencyCache[$this->getLocaleCode()][$currency];
	}	

}

You can see the comment of the code above for more detail understanding.

P.S: Be informed that you need to change the Class Name you are about to create on the basis of your Namespace and Module name.

I successfully used the same “behavior” of tabbed navigation in “front-end”, was easy at the end (always with Magento, when you get it), but I was struggling at the start. So, like my other posts, to share here’s how I used the same type of tab in Magento’s Front-end.

First thing is add the Tab’s Java-script file. You can either include by layout or in PHTML file. If you want to do from layout then,

<reference name="head">
        	 <action method="addJs"><script>mage/adminhtml/tabs.js</script></action>
</reference>

Next thing is to create Tab’s Menu inside UL & LI. Here’s the structure. (Self Explanatory)

<!-- TAB MENU STRUCTURE -->

<ul id="page_tabs">
	<!-- NORMAL TAB -->
	<li>
		<a id="normaltab" name="normaltab" class="tab-item-link" href="#"> NORMAL TAB </a>
		<!-- NOTE: class has to be tab-item-link-->

		<div id="normaltab_content"> Normal Tab HTML</div>
		<!-- NOTE: See the id of this div content it has id equal to its anchor's (<a>) id + Underscore + content -->
	</li>
	<!-- NORMAL TAB END-->

	<!-- AJAX LOADED TAB -->
	<li>
		<a id="ajaxtab" name="ajaxtab" class="tab-item-link ajax notloaded" href="http://example.com/magento/module/controller/action"> AJAX TAB </a>
		<!-- NOTE 1: class has to be tab-item-link ajax notloaded -->
		<!-- NOTE 2: Since this is Ajax Loaded Tab its Anchor should have href value = SOME URL -->

		<div id="ajaxtab_content"></div>
		<!-- NOTE 1: See the id of this div content it has id equal to its anchor's (<a>) id + Underscore + content -->
		<!-- NOTE 2: Since its innerHTML will be loaded by by Ajax you can set its innerHTML "blank" -->

	</li>
	<!-- AJAX LOADED TAB END -->
</ul>
<!-- TAB MENU STRUCTURE END -->

<!-- TAB CONTENT CONTAINER DIV-->
<div id="tabcontainer"></div>
<!-- TAB CONTENT CONTAINER DIV-->

Now its the time to use the Tabs JS included, like below.

<script>
	// Form Key Required for POST AJAX Method
	var FORM_KEY="<?php echo Mage::getSingleton('core/session')->getFormKey() ?>"; 

	// Set this to false, Guess used for some other purpose in backend, not really required in frontend.
	var varienGlobalEvents=false;

	// Initiallizing Varien Tabs
	/**
	* @param 1 : UL Menu ID
	* @param 2 : Target Tab Content ID
	* @param 3 : Initially Loading Tab's Id
	* @param 4 : Don't know yet, just use as it is (LOL)
	*/

	frontend_tabsJsTabs = new varienTabs('page_tabs', 'tabcontainer', 'normaltab',[]);

</script>

Done! You must now have a functioning Tab loading by Ajax and Normal, but yes tab would look good if you add CSS to your Tabs. Here is how it works.

1. On load it first copies the tab_content div inside the Target Tab Content ID div.
2. On tabbed menu clicked it checks its class name and if it class name does not have “ajax” it simply shows the its_content div.
3. If the menu clicked has “ajax” then it checks for another class name “notloaded”. So if its ajax and notloaded it then makes an Ajax request and updates the responseText to itsid_content div and then removes the “notloaded” class name for the menu. After that it then displays the itsid_content div, hiding previous ones.
4. If you re-click the “Ajax” typed menu, it will not find “notloaded” class in its menu, then it just shows its_content div.

A good trick, I thought while doing this, using class name to restrict the Ajax call.

Just a Re-Post

Magento eCommerce: How To Reset All Test Order Information and Set Unique Prefix For Orders, Invoices, Shipments, and Credit Memos.

<?php echo $this->getMessagesBlock()->getGroupedHtml() ?>

It did not work. Yes, after adding this block it had worked before. In my case, the probable case might be that I had called the module’s template from CMS page. In other case it should work. So, I looked for work around and the following did the trick.

// Getting Messages from Session
$messages=Mage::getSingleton("customer/session")->getMessages();

// Creating Block Mage_Core_Block_Messages
// Setting Message
// echoing the Message's HTML
echo $this->getLayout()->createBlock("core/messages")->setMessages($messages)->getGroupedHtml();

The Error/Success or Notice messages are set on session. So what I did was take those message/s from the session and create a new block, same as what $this->getMessagesBlock() might have called, and set those message to the created block and echoed its HTML.

Clever? or not?

Rewrite you catalog/product/view controller and add that logic.
Rewrite Block of that page and show error message accordingly.
Any other..?

Yeha, I do have another option as well. The Event-Observer Method. You can observe an event controller_action_predispatch_catalog_product_view and set up an observer where you can write your own logic there and redirect accordingly.

You can observe that event by setting up your config something like this.

<controller_action_predispatch_catalog_product_view>
	<observers>
		<mymodel>
			<type>singleton</type>
			<class>mymodel/controller_observer</class>
			<method>controller_action_predispatch_catalog_product_view</method>
		</mymodel>
	</observers>
</controller_action_predispatch_catalog_product_view>

And on the observer’s controller_action_predispatch_catalog_product_view method, you can check your logic for visibiliy of that product to the logged in user group and redirect if not visible.

Here’s the main point of this post (Did I take a lot of your time ?), in that same method you can directly redirect using the following snippet of code.

Mage::app()->getResponse()->setRedirect(Mage::getUrl("myrouter/mycontroller/noview"));

Adding an error message to the session would be a good idea, for user to understand what is happening. Else you can directly call a template in the redirected controller’s action with appropriate message.

I think this sums up the post for now..and as always hoping it helps somebody and waiting for the response.

Below is the code how I created those links using Custom SQL. But I have to tell you that the former methods looks organized, this is just a work around to a situation. You might know what I am trying to say!

$resource 	= Mage :: getSingleton( 'core/resource' );
$read= $resource -> getConnection( 'core_read' );
$write= $resource->getConnection('core_write');
$linkTable=$resource->getTableName('catalog/product_link');

// Creating Upsell Product link

$write->query("INSERT into $linkTable SET
							product_id='".$productId."',
							linked_product_id='".$linkProduct."',
							link_type_id='".Mage_Catalog_Model_Product_Link::LINK_TYPE_UPSELL."'
			");

// Creating Related Product link

$write->query("INSERT into $linkTable SET
							product_id='".$productId."',
							linked_product_id='".$linkProduct."',
							link_type_id='".Mage_Catalog_Model_Product_Link::LINK_TYPE_RELATED."'
			");		

// Creating Crosssell Product Link
$write->query("INSERT into $linkTable SET
							product_id='".$productId."',
							linked_product_id='".$linkProduct."',
							link_type_id='".Mage_Catalog_Model_Product_Link::LINK_TYPE_CROSSSELL."'
			");

Happy Coding!

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.

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!