Replace With:

<default>
<!-- Mage_GoogleAnalytics -->
<reference name="before_body_end">
<block type="googleanalytics/ga" name="google_analytics" as="google_analytics" />
</reference>
</default>
</layout>

^ This will move the Google Analytics code to before the closing of the HTML </body> tag (for faster page load times)

Locate: /app/code/core/Mage/GoogleAnalytics/Block/ga.php

Replace at around LINE 171:

<!-- BEGIN GOOGLE ANALYTICS CODE -->
<script type="text/javascript">
//<![CDATA[
var _gaq = _gaq || [];
_gaq.push(["_setAccount", "' . $this->getAccount() . '"]);
_gaq.push(["_trackPageview", "'.$this->getPageName().'"]);
(function() {
var ga = document.createElement(\'script\'); ga.type = \'text/javascript\'; ga.async = true;
ga.src = (\'https:\' == document.location.protocol ? \'https://ssl\' : \'http://www\') + \'.google-analytics.com/ga.js\';
(document.getElementsByTagName(\'head\')[0] || document.getElementsByTagName(\'body\')[0]).appendChild(ga);
})();

//]]>
</script>
<!-- END GOOGLE ANALYTICS CODE -->

The app is free for basic use, but it will nag you every 5 minutes to buy the paid version.  The full version is $20 and comes with the nice addition of Intellisense-like code completion and a desktop version of the app.  Future upgrades are free for the full version.

—————————————————————-

Now being more experienced with Magento we definitely feel the need to share our findings with the masses. We only wish we knew these things prior to trying to the hack the crap out of magento to make it do what we want.

Turning on Template Path Hints
If you’re new to Magento you will realize that it is quite a hassle to understand the logic behind the file structure and block structure of a magento layout when trying to customize your storefront. There is a very under-publicized built-in magento feature that we’d like to share with you that should help you on your journey. Magento actually has the ability to display hints showing where the different files of your layout is contained so that you can edit it.

To achieve this, Follow these simple steps…

• Log in to your administration panel. Go to Sytem > Configuration.
• From the left navigation column on top there will be “Current Configuration Scope”. In the drop down menu select “Main Website”
• Then navigate to Developer > Advance, also in the left navigation column.
• Under “Debug” you’ll see Template Path Hints. Select Yes and click the Save Config button.

Now when you navigate to your storefront you’ll see a bunch of red boxes displaying the underlying structure of the pages regarding templates and blocks.

Note: This should only be used in a development environment, considering this will make your storefront look hideous with big red blocks everywhere.

—————————————————————-

Never edit core files
Problem: When developing with Magento you will find it necesary to edit core files to achieve certain functionality. However, By editting a core file you are basically blocking yourself into a corner. DON’T DO IT! If you ever wish to upgrade at any point in the future you will not be able to because any changes that you have made in the core files will be overwritten. Never fear, there is a way around this.

Solution: The “local” folder (\app\code\local\) is your saviour. Say you need to edit the “Shipping.php” file located at “\app\code\core\Mage\Shipping\Model\Shipping.php” you can create the same basic directory structure in the local folder and copy and paste the Shipping.php file into the new directory. So, your new “local” Shipping.php file will be located at \app\code\local\Mage\Shipping\Model\Shipping.php. You will be able to safely edit anything and everything within that local file and never have to worry about it being overwritten during an upgrade. This trick works because Magento will look for files in a local directory before looking for a file in the core directory.

Note: The above solution will only overpower files that exist within the \app\code\core\ or \app\code\community\ directories. Also note that any files within your magento theme (\app\design\frontend\default\YOURTHEME\) or (\skin\frontend\default\YOURTHEME\) are not considered core files and you are free to edit them as you please.

These are just to name a few… Follow our blog to read more!

Some things you must know:

• This will only work on an Apache server
• You must have mod_rewrite installed under Apache

First, Create an .htaccess file if you don’t already have one. Then enter one of the following solutions based on your needs.

Force appending www. to only http secure (https://) requests

# Redirect non-www to www

	Options +FollowSymLinks
	# turn mod_rewrite on
	RewriteEngine On

	# If https send to https://www.
	RewriteCond %{HTTP_HOST} ^YOURDOMAIN.COM$ [NC]
	RewriteCond %{HTTPS} on
	RewriteRule ^(.*)$ https://www.YOURDOMAIN.COM/$1 [R=301,L]

Force appending www. to both http (http://) and http secure (https://) requests

# Redirect non-www to www

	Options +FollowSymLinks
	# turn mod_rewrite on
	RewriteEngine On

	# If https send to https://www.
	RewriteCond %{HTTP_HOST} ^YOURDOMAIN.COM$ [NC]
	RewriteCond %{HTTPS} on
	RewriteRule ^(.*)$ https://www.YOURDOMAIN.COM/$1 [R=301,L]

	# If http send to http://www.
	RewriteCond %{HTTP_HOST} ^YOURDOMAIN.COM$ [NC]
	RewriteCond %{HTTPS} off
	RewriteRule ^(.*)$ http://www.YOURDOMAIN.COM/$1 [R=301,L]

With these examples it is necesary for you to make sure that you replace “YOURDOMAIN.COM” to reflect the actual domain name of the website you will be using this on. Once you have done this, save your .htaccess file and upload it to the base directory of your website.

Believe it or not a few search engines distinguish your website as two different websites http://www.yourdomain.com and http://yourdomain.com. It is often considered good practice to add this htaccess rewrite to any website you create so that you can rest assured that your website is not being indexed as two different websites.

There are a lot of references out there on this, but you have to sort of pull it all together on your own for this particular combination.

Verify that mod_deflate has been installed in Apache:

1. Open /etc/sysconfig/apache2.

2. Find the line that starts:

APACHE_MODULES=…

3. Verify that “deflate” is one of the modules listed (may not be in alphabetical order).

Now, enable compression in the virtual host file for your site:

1. Open /etc/apache2/vhosts.d/.conf.

2. Add the following lines inside the tag:

    <IfModule mod_deflate.c>
	DeflateBufferSize 32768
	DeflateCompressionLevel 5

	<Location />
		SetOutputFilter DEFLATE
		BrowserMatch ^Mozilla/4 gzip-only-text/html
		BrowserMatch ^Mozilla/4\.0[678] no-gzip
		BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
		SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png|tiff)$ no-gzip dont-vary
		# Header append Vary User-Agent env=!dont-vary
	</Location>
    </IfModule>

Now restart Apache using:

sudo /etc/init.d/apache2 restart

and you should be in business!

Validate that compression is working

A great, handy online site that you can use to validate that compression is working is http://www.gidnetwork.com/tools/gzip-test.php.

=============================
“e-commerce done right”
http://www.ifuelinteractive.com

updated 6/30/2010 for Magento 1.4

-- Reset Magento TEST Data

SET FOREIGN_KEY_CHECKS=0;

-- reset dashboard search queries
TRUNCATE `catalogsearch_query`;
ALTER TABLE `catalogsearch_query` AUTO_INCREMENT=1;

-- reset sales order info
TRUNCATE `sales_order`;
TRUNCATE `sales_order_datetime`;
TRUNCATE `sales_order_decimal`;
TRUNCATE `sales_order_entity`;
TRUNCATE `sales_order_entity_datetime`;
TRUNCATE `sales_order_entity_decimal`;
TRUNCATE `sales_order_entity_int`;
TRUNCATE `sales_order_entity_text`;
TRUNCATE `sales_order_entity_varchar`;
TRUNCATE `sales_order_int`;
TRUNCATE `sales_order_text`;
TRUNCATE `sales_order_varchar`;
TRUNCATE `sales_flat_quote`;
TRUNCATE `sales_flat_quote_address`;
TRUNCATE `sales_flat_quote_address_item`;
TRUNCATE `sales_flat_quote_item`;
TRUNCATE `sales_flat_quote_item_option`;
TRUNCATE `sales_flat_order_item`;
TRUNCATE `sendfriend_log`;
TRUNCATE `tag`;
TRUNCATE `tag_relation`;
TRUNCATE `tag_summary`;
TRUNCATE `wishlist`;
TRUNCATE `log_quote`;
TRUNCATE `report_event`;
TRUNCATE `sales_flat_quote_payment`;
TRUNCATE `sales_flat_quote_shipping_rate`;
TRUNCATE `log_url`;
TRUNCATE `log_url_info`;
TRUNCATE `log_visitor`;
TRUNCATE `log_visitor_info`;

ALTER TABLE `sales_order` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_datetime` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_decimal` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity_datetime` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity_decimal` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity_int` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity_text` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_entity_varchar` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_int` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_text` AUTO_INCREMENT=1;
ALTER TABLE `sales_order_varchar` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_quote` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_quote_address` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_quote_address_item` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_quote_item` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_quote_item_option` AUTO_INCREMENT=1;
ALTER TABLE `sales_flat_order_item` AUTO_INCREMENT=1;
ALTER TABLE `sendfriend_log` AUTO_INCREMENT=1;
ALTER TABLE `tag` AUTO_INCREMENT=1;
ALTER TABLE `tag_relation` AUTO_INCREMENT=1;
ALTER TABLE `tag_summary` AUTO_INCREMENT=1;
ALTER TABLE `wishlist` AUTO_INCREMENT=1;
ALTER TABLE `log_quote` AUTO_INCREMENT=1;
ALTER TABLE `report_event` AUTO_INCREMENT=1;

Just run this script against the Magento database (make a backup first!).

=============================
“e-commerce done right”
http://www.ifuelinteractive.com

The Change

1. Open the file <magentoroot>/lib/Varien/Db/Adapter/Pdo/Mysql.php.

2. Add the following lines:

$code = 'SQL: ' . $sql . "\r\n";
if ($bind) {
     $code .= 'BIND: ' . print_r($bind, true) . "\r\n";
}
$this->_debugWriteToFile("[".date('Y-m-d H:i:s')."] ".$code);

Add it to the “query” function as shown below:

public function query($sql, $bind = array())
{
     $this->_debugTimer();

     try {
          $sql = (string)$sql;
          if (strpos($sql, ':') !== false || strpos($sql, '?') !== false) {
               $this->_bindParams = $bind;
               $sql = preg_replace_callback('#(([\'"])((\\2)|((.*?[^\\\\])\\2)))#', array($this, 'proccessBindCallback'), $sql);
               $bind = $this->_bindParams;
          }

          $code = 'SQL: ' . $sql . "\r\n";
          if ($bind) {
               $code .= 'BIND: ' . print_r($bind, true) . "\r\n";
          }
          $this->_debugWriteToFile("[".date('Y-m-d H:i:s')."] ".$code);

          $result = parent::query($sql, $bind);
     }
     catch (Exception $e) {
          $this->_debugStat(self::DEBUG_QUERY, $sql, $bind);
          $this->_debugException($e);
     }
     $this->_debugStat(self::DEBUG_QUERY, $sql, $bind, $result);
     return $result;
 }

The Log

By default your sql will be logged to:

<magentoroot>/var/debug/sql.txt

Limitations

1. As mentioned above, the file will likely be overwritten during a Magento upgrade.

2. There’s nothing that will turn logging off (except a Magento upgrade).  So you need to be careful that this is a temporary setting for debugging only.

=============================
“e-commerce done right”
http://www.ifuelinteractive.com

ajaxAddToCart.zip

Step 1: Create the server side script.
My sample script is called “addToCartTest.php” and I put it in a /scripts folder in the root of my Magento installation.

<?php
include_once '../app/Mage.php';
Mage::app();

try{
     // usage /scripts/addToCartTest.php?product_id=838&amp;amp;amp;amp;amp;qty=1
     $product_id = '';

     // get query string
     if (!isset($_GET['product_id'])) { $product_id = ''; } else { $product_id = $_GET['product_id']; }
     if (!isset($_GET['qty'])) { $qty = '1'; } else { $qty = $_GET['qty']; }

     $product = Mage::getModel('catalog/product')->load($product_id);

     $session = Mage::getSingleton('core/session', array('name'=>'frontend'));
     $cart = Mage::helper('checkout/cart')->getCart();

     $cart->addProduct($product, $qty);

     $session->setLastAddedProductId($product->getId());
     $session->setCartWasUpdated(true);

     $cart->save();

     $result = "{'result':'success'}";
     echo $result;

} catch (Exception $e) {
     $result = "{'result':'error'";
     $result .= ", 'message': '".$e->getMessage()."'}";
     echo $result;
}

Step 2: Create the ‘html’ page
Obviously, you’d be putting this code into your product detail page or wherever you’re trying to add the item to the cart from.

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Ajax add to cart sample</title>
<script src="/scripts/jquery-1.3.2.min-noconflict.js"></script>
<script type="text/javascript">
jQuery(document).ready(function($) {
     $("#buyNowButton").click(function(){
          var qty = $("#qty").val();
          var product_id = $("#buyNowButton").attr("product_id");

          var params = "product_id=" + product_id + "&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;qty=" + qty;        

          var result = $.getJSON("/scripts/addToCartTest.php", params, function(data, textStatus){
               if (textStatus == "error"){
                    alert("There was an error adding this item to your cart.  Please call customer service for assistance.", "Error");
                    return;
               }

               if (data.result == "error"){
                    alert("Sorry, an error occurred while adding the item to your cart.  The error was: '" + data.message + "'");
                    return;
               }

               alert("Thanks!  The item has been added to your cart!")
          });
     });
});
</script>
</head>
<body>
     <input type="text" id="qty" value="1" />
     <a id="buyNowButton" product_id="972" href="#">Buy Now</a>
</body>
</html>

That’s it!

Prerequisites:
1. jQuery (Because Magento uses prototype and scriptaculous, you have to use jQuery in “no conflict” mode);
I’ve included the source code, along with the no-conflict version of jQuery in the zip file attached.

Let me know if you’re using this code (helps my ego)!

=============================
“e-commerce done right”
http://www.ifuelinteractive.com ]]> http://blogs.ifuelinteractive.com/2009/10/15/jquery-magento-and-ajax-add-to-cart-redux/feed/ 12 http://blogs.ifuelinteractive.com/2009/09/29/create-a-new-product-attribute-and-then-using-it-on-a-page-in-magento/ http://blogs.ifuelinteractive.com/2009/09/29/create-a-new-product-attribute-and-then-using-it-on-a-page-in-magento/#comments Tue, 29 Sep 2009 18:53:45 +0000 Andy http://blogs.ifuelinteractive.com/?p=51

Creating a new product attribute and using it when you’re displaying a product turns out to be fairly simple – but I know for us at iFuel – and I think for lots of others based on the posts you see around the net, it ends up not being as simple as it seems.

For this example, we’ll create a new attribute called “ingredients”.  We need this to be a text field (text area to be exact) that Magento admins can enter the product ingredients.  Then we’ll need to be able to access this text when we display the product.

Attributes

Attributes are single pieces of information that can be assigned to any of the entities (models) in the Magento system.  There is an extensive user interface for creating and maintaining attributes and attribute sets for products.  But you can actually create attributes for other entity types, like categories, too.  (Creating an attribute for a category has to be done right in the database – I’ll try to cover that in a future post).

To create an attribute:

1. Select “Attributes” -> “Manage Attributes” from the “Catalog” menu in the Magento admin panel.

2. Click “Add New Attribute”.

Adding an Attribute

3. Enter an attribute code – we’ve used “ingredients” here.

4. Select the scope – we’ve selected “global” but you could select store as well.

5. Select the attribute type – we’ve selected text area because we want the user to be able to enter free-form text (we’re using the wysiwig editor for Magento so they’re actually entering html).

6. Go to the “Manage Label/Options” tab and enter a label to be used for the new attribute.

7. Save the new attribute.

Attribute Sets

Once you’ve added the new attribute, you have to add it to the attribute set that you use for your products.  (If you have more than one attribute set for your products, you’ll have to add it to all of the sets you want it to appear in).

1. Select “Attributes” -> “Manage Attribute Sets”

2. Select your attribute set (if you haven’t created new attribute sets, it’ll be called “Default”)

3. Drag your new attribute from the list of “unassigned attributes” on the right into the list on the left (where you drop it will be where the admin will see it)

Adding and attribute to an attribute set in Magento

4. Save the attribute set.

Using the new attribute in the page

So, that’s the easy part.  Actually, using the attribute in the page is pretty easy, once you’ve got the right syntax!  Assuming the id of the product you are using is in $productid then:

<?php

$productModel = Mage::getModel('catalog/product')->load($productid);

$ingredients = $productModel->getIngredients();

echo $ingredients;

?>

Poof!

I kept trying $_product->getIngredients(), but that wasn’t working.  I think there’s a way to tell Magento to load that attribute when the product is being loaded.  If anyone knows, let me know!

=============================
“e-commerce done right”
http://www.ifuelinteractive.com

I knew there had to be something out there, but I didn’t know there was something right in the IIS 6 resource kit called LogParser.

There are a bunch of options in log parser, but the one I thought was way cool was the ability to basically “query” the log.  For example:

LogParser “Select count(*), sum(sc-bytes) from d:\logs\w3svc1\ex090922.log where cs-uri-stem like ‘%.jpg’ or cs-uri-stem like ‘%.gif’ or cs-uri-stem like ‘%.swf’ or cs-uri-stem like ‘%.css’ or cs-uri-stem like ‘%.js’ or cs-uri-stem like ‘%.pdf’ or cs-uri-stem like ‘%.png’ or cs-uri-stem like ‘%.cur’”
returns:

COUNT(ALL *) SUM(ALL sc-bytes)
———— —————–
23977        53910768

Statistics:
———–
Elements processed: 34195
Elements output:    1
Execution time:     0.22 seconds

This tells me that there were 23K requests for these file types, for a total of about 53Mb.  The log in question only represents 1 hour from one of two servers hosting the site (I think you can process from multiple logs simultaneously – have to spend more time playing around).  And it was really fast – < 1 second!

So kudos to whoever created this tool!