IT 技术领域学海无涯。其实任何领域都学海无涯，无非 IT 发展太快了，让我有更多嘘唏。希望我掌握的技术有如小小草，虽然渺小，却有旺盛的生命力。
Google 很强大，虽然我不止一次地说，但用了 Google Apps Script 以后，我还是想再说一次。
Many of Google Products are helping people use the web. Google Apps Script help me visually programme route jobs.
在工作流中，有很多变化着的因素，导致很多程序是一次性的。快速变化的环境不要求程序很智能，但要能快速响应业务的变化。很多时候我很郁闷——因为编程速度跟不上业务速度，导致人工重复劳动。
Google Apps Script 是目前跟我理想中的 crm, accounting 最接近的解决方案。
据说 Zend 正在跟 Plesk 探讨怎么让他们的产品相互兼容。
我没那么高深，无法让 Zend Server 完全兼容 Plesk，但可以做到——
前台用上 Zend Server 版的 php （Plesk 前后台使用两个安装的 php），尽管 Plesk 后台误认为 php module not installed。我强行修改了 psa 数据库里的数据，改了什么我不记得了。说实话，把 Zend Server 和 Plesk 跑在一起意义也不大。
In Gmail, type “-in:inbox” or “!in:inbox” in search box and click “Search Mail”,what emails will show up? All emails not in inbox? Not exactly.
You know Gmail delivers conversions instead of emails as search result, so let’s use terminology conversion. Does “-in:inbox” come up with all conversions not in inbox? No, again.
The collection of “-in:inbox” is all conversions not in inbox plus those conversions originated by me or to which I responded.
在 CentOS 上，怎么把 linux user ftp 登录后限制在它的 home directory？很久以前我设置过一次，知道是很简单的一个设置，今天需要同样的事情再做一次，竟然怎么也想不起来。要命的是，google 了好几个小时都不得要领。
可以说半天时间是浪费掉的。最后当然是重新找到了办法，赶紧记下来：
Edit /etc/proftpd.conf, add
DefaultRoot ~
当然前提预装有 proftpd。如果还预装 plesk，则更简单，/etc/proftpd.conf 已含有
DefaultRoot ~ psacln
只要把新建的用户归入 secondary group psacln 即可。
Magento 自带的管理产品图片的机制简单有效，但每次只能对单个产品进行管理，每次要 http upload 很费时。如果换个角度看，如果要成批更新产品图片，就不那么方便；如果要调用某个产品图片，必须先找到产品才能找到图片，因为 Magento 对上传后的文件进行了 dispretion 处理了文件路径，没有直观的办法可以直接浏览图片。
所以我的做法是，产品图片按产品属性归类，把整个文件夹 ftp 到 Magento 某个位置（或从 Magento 中独立出来，用一个静态文件服务器来管理图片，这样可以提供更方便的文件操作）。
然后在 magento/media/catalog/product 下建一个软连接（假设这个软连接名 static_image_linkedin）到产品图片目录的根。不要在 magento/media/catalog 这一级把 product 建为软连接，因为 Magento 会在 product 下建 cache 目录，从静态文件服务器角度看，这个 cache 是垃圾（我追求完美）。
然后，如果要指定产品使用某图片，必须把image, small_image, thumbnail, media_gallery 对应的值保存为人工指定位置的图片路径，该值的形式如 “/static_image_linkedin/nwf/recycled/green_bag.jpg”。Magento 原值形式如 “/g/r/green_bag.jpg”，我还没做出一个 GUI 帮助完成此项修改，依赖数据库直接操作。
我本有一个想法是修改 magento/app/code/core/Mage/Catalog/Model/Product/Media/Config.php 来改变产品图片目录的根，这样就不需要建软连接。但这样做的缺点是在移交 Magento 给别的 developers 时，我还得多一点额外交代。
When to use:
Magento has a native “buy x get y” sales rule in promotions. Magento’s x and y refer to a same product. For example, if a product offer is “buy 3 get 2”, you have to buy 5 of this product then only pay for 3 of them.
Quite often the store owners want to give an offer which let customers choose from a wide range of products, (the programme add them up, get a total quantity of subselect), and offer another selection of products for free. It is useful if the store have two ranges of products, among which prices are almost the same. Let’s make it clear to you: in this module, “buy x get y” means “Buy X selection of products, Get another Y selection for free”.
I wrote some quick and dirty codes to do “Buy X selection of products, Get another Y selection for free” quite a while ago, but this release refactors the codes into a standard standalone Magento extension.
How to install:
Copy the whole “app” folder, merge to magento/app. That’s it.
If you are logged in Magento backend when doing installation, that’s fine. But you have to log out and log in again to access Buy X Get Y configuration section in System Configuration.
How to use:
Log in Magento backend, go to Promotions -> Shopping Cart Price Rules, create a new rule whose name must start with “[bxgy]”;
In “Rule Information” tab, apart from the Rule Name, set up everything else as if it is normal Magento sales rule;
In “Conditions” tab, create a product total quantity subselect. The product subselect should match the selection of X product in the offer, and condition is “equals or greater than”, and quantity should match the quantity of X product used as qualifier;
* Do not create more than one subselect. Result is unpredictable otherwise.
* The condition must be “equals or greater than” and the quantity must be the threshold quantity of the offer. Although the calculation of the free quota of Y product is not dependent on the quantity (it is dependent on the settings in “Actions” tab), the offer validation is still Magento original logic. This module changes the discount amount after the offer validation. In other words, you must think about when to trigger Magento native “buy x get y”, and do the same conditions for this module.
In “Actions” tab, set Apply to “Buy X get Y (discount amount is Y)” (although this is not normal buy_x_get_y action, the program still check this simple_action), set Discount amount to offer free quota, set Maximum Qty Discount is Applied to to 0, set Discount Qty Step (Buy X) to offer quantity qualifier. For example, if the offer is “buy any 3 of X products, and get any 2 of Y products free”, then set Discount amount to 3, set Maximum Qty Discount is Applied to to 0, set Discount Qty Step (Buy X) to 2. Then, in “Apply the rule only to cart items matching the following conditions (leave blank for all items)”, create a combination of conditions which match the selection of Y product in the offer. Multi combination is OK;
In “Label” tab, enter the offer labels as normal. It is not required, but if you leave it blank, the “ugly” Rule Name “[bxgy]***” will be used is discount description;
Now save the rule, and go to System -> Configuration -> Buy X Get Y -> Buy X selection of products, Get another Y selection for free, set up the offer reminder message in cart. It is not required. And if it is not set up, the offer is still taking effect as long as the sales rule is enabled.
How is it created:
This module is created by koukou1985’s module creator (http://www.magentocommerce.com/wiki/custom_module_with_custom_database_table). Thanks to koukou1985.
How good is it:
This module does not override any Mage classes. It is safe to use with other extensions as long as namespace and module name do not conflict.
FAQ:
Q: Why this module does not work?
A: I won’t cover all reasons that make my module not working. I only point out caveats of my module, and expect you to have common knowledge of Magento, such as “refresh the cache to see the newly installed features”. All caveats are in above sections. So, if you are stuck, go back to the top and read again.
Download BuyXGetY.tar.gz
Update: a new version of bxgy module is available at http://blog.goods-pro.com/1764/magento-extension-bxgy-0-1-1-is-released/
2011/02/21 Update again: please checkout a newer release. Always leave comments on the newest release post. The comment on this post is closed.
漫天都是“云服务”，但真让我有云的感觉的服务目前只有 Google 一家。最近买了 1&1 cloud server，如果要评满意程度的话，只能是 5 out of 10 （购前期望过高）。
我原以为基于云的服务器可以一劳永逸、无限扩张，哪知 1&1 cloud server cpu core, memory, hard disk 都有上限，cpu core 最多买 4 个，其实就相当于单个 quad core cpu。
1&1 cloud server 性能也一般，或许还不如 vps，唯一优势就是比同等性能的 dedicated server 便宜一些。
Magento store owners are having a challenge when using rcah 0.1.0, especially for homepage. The nature of homepage is CMS, most content of it static.
Store owners want their visitors (especially first time visitors) to read static content on the homepage, but static content become obstacles filling in the central area of the page when visitors start to click on filters for refined results.
Root category as homepage 0.1.1 is released to address the problem. It conditionally hides the CMS Block on category pages. It only hides CMS Block in Display Settings of a category (category landing_page attribute). Static CMS Blocks used for others purposes (in sidebar, footer, etc) are not affected.
I must say the conditions when hiding the CMS Block are subtle. Please refer to readme file with the release for details.
Download RootCategoryAsHomepage.tar.gz
I did this experiment with php apc:
In php.ini I set include_path = /first/include/path:/second/include/path, but do not put a file in /first/include/path or /second/include/path, create test.php as simple as this
<?php require 'tobeincluded.php';
It will run into a fatal error. This error is obvious.
Then I create the file tobeincluded.php in /second/include/path, test.php now runs all right.
Then I create another file with same file name as tobeincluded.php but different content and put it in /first/include/path, test.php keeps running as if /first/include/path/tobeincluded.php does not exist. This is because php apc has cached /second/include/path/tobeincluded.php and ignored /first/include/path/tobeincluded.php. Apc will refresh its cache when it is restarted or original cached file is updated in the file system. I assume apc is checking file timestamp.
Then I copy test.php to test2.php and put test2.php in the same folder as test.php, run test2.php. It renders the same result as test.php – include /second/include/path/tobeincluded.php but ignore the existence of /first/include/path/tobeincluded.php.
Then I copy test.php to test3.php and put test3.php in a different folder (no matter parent folder or child folder or irrelevant folder), run test3.php. Now it is aware of the existence of /first/include/path/tobeincluded.php so /first/include/path/tobeincluded.php is included in test3.php.
Even I trigger to run test2.php in a different virtual host (but same document root), it still renders the same result. I assume php file on the file system is identical to apc. In other words, apc loads cache data by realpath regardless virtual host.
今天我做了个有趣的实验：
摸清 Magento 的规律后就容易理解 Manage Products GUI 在 scope 改变或 store view 切换时的行为。另文有提及 change product default value and store view view by programming.
