Category: 小小草

IT 技术领域学海无涯。其实任何领域都学海无涯，无非 IT 发展太快了，让我有更多嘘唏。希望我掌握的技术有如小小草，虽然渺小，却有旺盛的生命力。

What happens when an order is cancelled in Magento?

Order Status

When you click Cancel button in an order view, order status changes to Cancelled if payment is not received (i.e. invoice is not raised).

If payment is received before you click Cancel button, order status changes to Complete. You must raise a credit note to offset the payment, then the status changes to Closed. However, this order still counts in dashboard. This statistical result is not what I am expecting, but I think there is a reason inside.

See table as summary

Is payment received? No Yes

Order status changes to >>>Cancelled >>>Complete (before credit note is raised)

>>>Closed (after credit note is raised)

What is order status when payment or credit is partially done?

If an order is cancelled when payment is partially received, the status changes to Complete immediately as if full payment is received.

If a Complete order is partially refunded, the status remains Complete. The status changes to Closed when customer is credited in full.

See table as summary

Payment is partially received >>>Complete (before credit note is raised)

>>>Complete (credit noted is raised but partially)

>>>Closed (after full refund)

Will inventory level reverse itself when an order is cancelled? It depends.

Reversal only happens if this order is not shipped AND payment is not received.

See table as summary

Order is not shipped

AND

payment is not received
Order is shipped

OR

payment is received

Inventory level Reversal No reversal on cancelling

Will inventory level reverse itself when an order is cancelled after it is partially fulfilled? And how much is the reversed inventory?

If an order is partially fulfilled (payment is partially received or shipment is partial), there are 3 types of quantity, Qty Ordered, Qty Invoiced, Qty Shipped, showing at order view. Then you click Cancel button, you get –

Qty Cancelled = Qty Ordered – max (Qty Invoiced, Qty Shipped)

Qty Cancelled is the quantity automatically reserved to inventory.

May 19, 2010
No formatting inside html tag
我目前用的 WordPress 版本为 2.8.4。发现一个 bug，就是在 post html 源码编辑状态（非 Visual 编辑），输入时为
```
<div>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。

不知 WordPress 能听明白吗？
</div>
```
保存后查看一下数据库，post_content 忠于原文，前台输出时却经过 WordPress 的格式转换，变成了
```
<div>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。</p>
<p>不知 WordPress 能听明白吗？
</p></div>
```
html p tag 都不配对了。

这个 bug 不严重，因为 WordPress 自带的 TinyMCE editor 不会插入 div tag。TinyMCE 倒可以插入 b-quote，输入时
```
<blockquote>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。

不知 WordPress 能听明白吗？
</blockquote>
```
前台输出
```
<blockquote><p>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。</p>
<p>不知 WordPress 能听明白吗？
</p></blockquote>
```
完全正确，没有触发 bug。这个小 bug 让我联想到很多 wysiwyg editor 和 output formatting 时不尽如人意的地方。

我在 magento 和 phplist 里都是禁用 wysiwyg editor 的，在 WordPress 里虽没有禁用它，但我有意识地仅仅使用它的 htmlentity。象我习惯于手写 html 代码以求更多输出控制的人，觉得 WordPress output formatting logic 也不好，更好的逻辑是：
- 如果post_content是有效的DOM，仅对最外层的 text nodes 作 html p wrapping，对任何 html tag 内部的不做任何处理。其他诸如 htmlentity filter 都不需要，因为 wysiwyg editor 已经作了这项工作。
- 如果post_content是无效的DOM，WordPress 默认的 formatting 会作一些修复。我没考察过修复的智能程度，我的要求是一开始就不要写出无效的 DOM，所以不想多讨论这种情况下的处理。
举个例子说，我的 formatting logic 就是把
```
anything outside html tag is wrapped by p tag.

do not touch anything inside html. user should be responsible for it.
<div>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。

不知 WordPress 能听明白吗？
</div>
```
输出为
```
<p>anything outside html tag is wrapped by p tag
</p><p>
do not touch anything inside html. user should be responsible for it.</p>
<div>
我希望 WordPress 自动格式化post时不要自说自话把html code加进html tag里。

不知 WordPress 能听明白吗？
</div>
```
April 29, 2010
Understanding layout.xml syntax in Magento
I write this article about my understanding of layout.xml up to now. I use it to show you
- How to add buttons in order/invoice/shipment/creditmemo without override Block class?
- How to define an array as a parameter in layout.xml using <action method=”addButton”><param>array</param></action>?
- How to assign any type of variables in layout.xml?
- How to avoid overriding controller class but still get the result you want on a specific url?
as well.

All my understanding was inspired by the task: adding buttons in order view at backend to offer administrators extra order process facilities.

I love Magento class overriding architecture, but as I have learned the downside of overriding (Basically, there is only one chance of overriding for each class among all extension classes. Therefore, the more classes overridden, the greater chance of conflict between extensions.), I create a principle for my programming in Magento – do not override Magento class unless there is no other way around it.

So, back to the task. It would be very easy to add the button if I had overridden Mage_Adminhtml_Block_Sales_Order_View. It could be
```
public function __construct() {
parent::__construct();
$this->_addButton('new_button', array(
'label'    => Mage::helper('sales')->__('New Button'),
'onclick'  => "window.open('{$this->getUrlForNewButton()}')",
))
;
}
```
However, I do not want to override Mage_Adminhtml_Block_Sales_Order_View. How about firing addButton method in layout.xml? I see an example of addTab at the left side
```
<block type="adminhtml/sales_order_view_tabs" name="sales_order_tabs">
<action method="addTab"><name>order_info</name><block>order_tab_info</block></action>
<action method="addTab"><name>order_invoices</name><block>adminhtml/sales_order_view_tab_invoices</block></action>
<action method="addTab"><name>order_creditmemos</name><block>adminhtml/sales_order_view_tab_creditmemos</block></action>
<action method="addTab"><name>order_shipments</name><block>adminhtml/sales_order_view_tab_shipments</block></action>
<action method="addTab"><name>order_history</name><block>adminhtml/sales_order_view_tab_history</block></action>
</block>
```
In the example, addTab method takes two parameters, one for tab name and the other for block name. Inside addTab method, it creates a block object from the block name, which is passed in as a string. In fact, the tag name <name> or <block> is not significant in layout.xml. It does not represent parameter name in method. But the position is significant – the first tag is passed into method as the first parameter, and ditto the followings.

Back to addButton method in Mage_Adminhtml_Block_Widget_Container. It takes at least two parameters, one as string and the second as associated array. So the layout.xml can be something like this:
```
<reference name="sales_order_edit">
<action method="addButton" translate="label">
<name>new_button</name>
<button_array>
<label>New Button</label>
<onclick>window.open('{$this->getUrlForNewButton()}')</onclick>
</button_array>
</action>
</reference>
```
The difficult part is in <onclick> – it requires a variable of current order id. After some digging, I find another example:
```
<reference name="footer_links">
<action method="addLink" translate="label title" module="catalog" ifconfig="catalog/seo/site_map"><label>Site Map</label><url helper="catalog/map/getCategoryUrl" /><title>Site Map</title></action>
</reference>
```
So, I create a helper method to return url for new button and modify layout.xml to
```
<reference name="sales_order_edit">
<action method="addButton" translate="label">
<name>new_button</name>
<button_array>
<label>New Button</label>
<onclick helper="mymodule/getUrlForNewButton"/>
</button_array>
</action>
</reference>
```
Unfortunately, it did not work. I assume the helper callback does not work if it is in the array. So I change the helper method to return an associated array directly as the second parameter for layout.xml and the final layout.xml is
```
<reference name="sales_order_edit">
<action method="addButton" translate="label">
<name>new_button</name>
<button helper="mymodule/getNewButtonSecondParam"/>
</action>
</reference>
```
It works perfectly. I am very proud of myself.

Some while ago, I overrode Mage_Catalog_ProductController just to register a variable in viewAction
```
public function viewAction() {
Mage::register('my_var', $value);
parent::viewAction();
}
```
Now I reviewing that approach stupid. I could register a variable using layout.xml without any class overriding!
April 19, 2010
cp -f does not switch off prompt?

我在 Fedora 下执行大量的文件拷贝操作，我使用了

cp -fr [SOURCE] [DEST]

我使用了 -f 开关就是不想被询问文件是否覆盖。但

cp: overwrite `(filename)’? 提示还是出现。

这是什么原因？原来 Fedora 带有几个 alias，可以用 alias 命名查看。

# alias
alias cp=’cp -i’
alias l.=’ls -d .* –color=auto’
alias ll=’ls -l –color=auto’
alias ls=’ls –color=auto’
alias mv=’mv -i’
alias rm=’rm -i’
alias which=’alias | /usr/bin/which –tty-only –read-alias –show-dot –show-tilde’

cp 被 alias 了！-i switch 优先于 -f，所以 cp -fr [SOURCE] [DEST] 其实是执行了

cp -ir [SOURCE] [DEST]

怎么才能让 overwrite 提示不出现呢？办法有二：

办法一是使用 unalias 解开 cp -i。但 cp 默认使用 -i 确实很不错，我不想放弃 Fedora 的体贴。于是——

办法二是使用
/bin/cp -ir [SOURCE] [DEST]

April 19, 2010
Magento 1.3 cannot work with memcached 1.4
今天我注意到一个还未来得及升级的 Magento 1.3.2.3 的安装 down 了，原因是 Magento 1.3.2.3 无法和 memcached 1.4.4.2 协同工作（memcached 1.4.4.2 服务器环境自动升级带来的）。

错误提示如下

Notice: MemcachePool::delete() [memcachepool.delete]: Server 127.0.0.1 (tcp 11211, udp 0) failed with: CLIENT_ERROR bad command line format. Usage: delete [noreply]
(0) in /……/magento/app/code/core/Zend/Cache/Backend/Memcached.php on line 271

我按提示找到 Memcached.php 把第271行改为
```
return $this->_memcache->delete($id, 0);
```
仍旧无效。

尝试着升级安装到 Magento 1.4.0.1，能支持 memcached 1.4.4.2 了。

但网站布局变得乱七八糟，需要调整很多 template, layout 及 css 文件，这不是一时半会能完成的，只好暂用备份文件降级到 Magento 1.3.2.3，改用 apc backend cache。还好网站在单台服务器上运行，没涉及到分布式缓存，memcached 不是必需的。我装了 memcached 也没怎么玩它，缺乏掌控，暂时先搁置。
April 9, 2010
Customise Magento order number
After I put a lot of test orders into Magento, now I want to delete them for a clean start. I also want to shorten the length of order number, and the order number from various stores share the global increment. I want the similar settings on Matgento invoice, shipment, and creditmemo.

I have concluded these steps after some trials and errors.

Firstly, empty orders, invoices, shipments, and creditmemo by executing mysql commands:
```
TRUNCATE `magento_sales_flat_order_item`;
TRUNCATE `magento_sales_flat_quote`;
TRUNCATE `magento_sales_flat_quote_address`;
TRUNCATE `magento_sales_flat_quote_address_item`;
TRUNCATE `magento_sales_flat_quote_item`;
TRUNCATE `magento_sales_flat_quote_item_option`;
TRUNCATE `magento_sales_flat_quote_payment`;
TRUNCATE `magento_sales_flat_quote_shipping_rate`;
TRUNCATE `magento_sales_invoiced_aggregated`;
TRUNCATE `magento_sales_invoiced_aggregated_order`;
TRUNCATE `magento_sales_order`;
TRUNCATE `magento_sales_order_aggregated_created`;
TRUNCATE `magento_sales_order_datetime`;
TRUNCATE `magento_sales_order_decimal`;
TRUNCATE `magento_sales_order_entity`;
TRUNCATE `magento_sales_order_entity_datetime`;
TRUNCATE `magento_sales_order_entity_decimal`;
TRUNCATE `magento_sales_order_entity_int`;
TRUNCATE `magento_sales_order_entity_text`;
TRUNCATE `magento_sales_order_entity_varchar`;
TRUNCATE `magento_sales_order_int`;
TRUNCATE `magento_sales_order_tax`;
TRUNCATE `magento_sales_order_text`;
TRUNCATE `magento_sales_order_varchar`;
TRUNCATE `magento_sales_payment_transaction`;
TRUNCATE `magento_sales_refunded_aggregated`;
TRUNCATE `magento_sales_refunded_aggregated_order`;
TRUNCATE `magento_sales_shipping_aggregated`;
TRUNCATE `magento_sales_shipping_aggregated_order`;
```
Then, go to table magento_eav_entity_type, find entity order, invoice, shipment, creditmemo, change increment_per_store to or not to share global increment (default is 1 which means each store has its own increment), change increment_pad_length to shorten or longer numbers (increment_pad_length does not include prefix: 1 digit by default).

Then, empty table magento_eav_entity_store by executing:
```
TRUNCATE `magento_eav_entity_store`;
```
With an empty table, Magento generate default increment_prefix which is store id (with global increment setting, it is 0), and increment starts from 0.

I want the first order, invoice, shipment, creditmemo number look like 100001, I set magento_eav_entity_type.increment_pad_length at 5, and insert 4 records into magento_eav_entity_store.

Customise order, invoice, shipment, creditmemo number in Magento

And that’s it.

2010年6月22日更新：我想提醒一下，光有几个 store_id = 0 的记录不够保险。因为几天后，我发现每个 storeview 都有了各自的记录，显然 storeview 的记录优先于 default (store_id = 0)。increment_prefix 默认为 store_id，这让每个 storeview 有了不同的前缀，与我初衷（所有 storeview 统一使用 “1” 为前缀）相悖。我不清楚后来这些自动添加的记录是由什么事件引发的。既然 increment_prefix 被改了，我只好接受这个事实，改来改后会让后台订单号看起来没有连续性。

More data added to eav_entity_store
April 7, 2010
Comparison in PHP
除非使用 === 或 !== 进行比较，PHP 尽可能地将值转化为数字进行比较。因此，看到比较 “10” == “1e1” 的结果是 true，千万不要大惊小怪。

“尽可能”如何理解？
1. 如果等式一边是数字，另一边是字符串，那么字符串一定要 cast to int 后再比较。因此，比较 “10” == 1e1 的结果是 true，比较 “10 ” == 1e1 的结果也是 true。
2. 如果等式两边都是字符串，且字符串中均不含数学字符以外的字符（包括white space），那么两边的字符串会在 cast to int 后再比较；否则，直接比较字符串。因此，比较 “10” == “1e1” 的结果是 true，但比较 “10 ” == “1e1” 的结果是 false。
3. 如果等式有一边或两边是数组，则先比较数组结构是否相同，再逐个比较数组元素。在比较数组元素时，索引不会 cast，但值按上述两条规则“尽可能” cast。因此，比较 1 == array(1) 的结果是 false，比较 array(“10”) == array(“1e1”) 的结果是 true，比较 array(10 => 10) == array(“1e1” => 10) 的结果是 false。
April 6, 2010
Paypal vs PaypalUk in Magento

Magento 里有两个有关 Paypal 支付的模块：Paypal and PaypalUk。我尚未查到文档有关它们的区别，只知道 PaypalUK 依赖于 Paypal，在同时启用 Paypal and PaypalUk 时，后台可以看到

Configuration Paypal section when PaypalUk is enabled

Configuration Payment Methods section when PaypalUk is enabled

若不启用 PaypalUk 模块，后台变成：

Configuration Paypal section when PaypalUk is disabled

Configuration Payment Methods section when PaypalUk is disabled

对比可见后台多了 Payflow Edition，估计 PaypalUk 是面向开发者的称呼，Payflow 是面向普通用户的称呼。更多区别还有待摸索。

April 1, 2010
OpenPassword
Inspired by OpenId, I want to start a project – OpenPassword.

What is it for?
People are hesitate to register themselves from site to site. One of the reasons is people are afraid of giving password to the web sites they do not trust much. Most people do not have big memory, so they have to use the same password for all web sites. They may or may not aware that any webmaster / web owner who has access to the password database could try the same password on other sites (or even worse – for online banking). Whether people’s passwords are in safe depends on how honest the webmaster / web owner is. Even the webmaster / web owner is honest, does he have basic skills to keep password in safe? I see a lot of web sites save passwords unencrypted, which could be a disaster.

OpenId comes to solve this problem. But currently not all web sites support OpenId. What if you are in a position you have to use some web sites which do not support OpenId? You have to take care of security yourself. My proposal is:
1. You register different web sites with different passwords.
2. The passwords are generated with one-way encryption.
3. You host encryption algorithm and salt in a safe place, so you do not need remember the passwords. Every time you need them, you generate / retrieve them on the fly.
April 1, 2010
Dispatched events on a simple Magento homepage

每访问一次我一个并不复杂的 Magento 站点主页，将会触发多少个事件？我记了下来：

resource_get_tablename
resource_get_tablename resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after core_collection_abstract_load_before core_collection_abstract_load_after core_collection_abstract_load_before core_collection_abstract_load_after controller_front_init_before controller_front_init_routers resource_get_tablename resource_get_tablename model_load_after core_abstract_load_after resource_get_tablename core_locale_set_locale controller_action_predispatch controller_action_predispatch_cms controller_action_predispatch_cms_index_index resource_get_tablename resource_get_tablename model_load_after cms_page_load_after resource_get_tablename model_load_after core_abstract_load_after cms_page_render controller_action_layout_load_before customer_session_init resource_get_tablename model_load_after core_abstract_load_after resource_get_tablename controller_action_layout_generate_xml_before controller_action_layout_generate_blocks_before core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after resource_get_tablename resource_get_tablename core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after controller_action_layout_generate_blocks_after controller_action_layout_render_before controller_action_layout_render_before_cms_index_index core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_to_html_before model_load_after core_abstract_load_after resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before resource_get_tablename model_load_after catalog_entity_attribute_load_after model_load_after catalog_entity_attribute_load_after model_load_after catalog_entity_attribute_load_after model_load_after catalog_entity_attribute_load_after catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename model_load_after customer_load_after resource_get_tablename model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after model_load_after core_abstract_load_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before resource_get_tablename resource_get_tablename resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after core_block_abstract_to_html_after core_block_abstract_to_html_before resource_get_tablename resource_get_tablename model_load_after core_abstract_load_after core_block_abstract_prepare_layout_before core_block_abstract_prepare_layout_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before model_load_after core_abstract_load_after core_block_abstract_to_html_after core_block_abstract_to_html_before model_load_after core_abstract_load_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before resource_get_tablename model_load_after sales_quote_load_after resource_get_tablename model_load_after customer_group_load_after resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after resource_get_tablename sales_quote_item_collection_products_after_load resource_get_tablename resource_get_tablename resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename resource_get_tablename resource_get_tablename eav_collection_abstract_load_before catalog_product_collection_load_before catalog_product_collection_load_after resource_get_tablename sales_quote_item_set_product sales_quote_item_qty_set_after resource_get_tablename core_collection_abstract_load_before core_collection_abstract_load_after resource_get_tablename core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before model_load_after core_abstract_load_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_after core_block_abstract_to_html_before core_block_abstract_to_html_after controller_action_postdispatch_cms_index_index controller_action_postdispatch_cms controller_action_postdispatch model_save_before core_abstract_save_before resource_get_tablename resource_get_tablename resource_get_tablename model_save_after core_abstract_save_after model_save_commit_after core_abstract_save_commit_after http_response_send_before
controller_front_send_response_after

April 1, 2010