Tag: magento

It is exciting to see Magento new versions keep coming out once after a while. Magento notify administrator upon login, and administrator upgrades it, then Magento should stop notifying until another new version is available. The logic should be as simple as that.

However, currently Magento message is always active even after upgrading. It only disappears when administrator marks it read or deletes it. Very annoying, isn’t it?

is_in_stock在magento export products时会是其中一列，但我在attributes里怎么也找不到它，它到底是什么？

Magento内置的产品属性与自定义的产品属性可访问范围不同。默认设置下，自定义的产品属性只能在product view取值，如在product view以外则取不到值；内置的产品属性则没有这种限制。

为了让自定义产品属性能在Magento前端（比如product list, product new, 或者自己写一个product featured）随意取值，至少有三种方法可以更改默认设置。

最简单的办法是创建一个config.xml(文件名任意)，放在app/etc/modules/下：

<?xml version="1.0"?>
<config>
    <frontend>
        <product>
            <collection>
                <attributes>
                    <attributeyouwant/>
                </attributes>
            </collection>
        </product>
    </frontend>
</config>

以后有空再讲其他两种办法。记得一定要刷新Magento cache才能让设置生效！

说来懊恼，为了让Magento product list能够显示自定义属性的值，我查看了magento wiki 和 forum 上几十个帖子，众说纷纭，我也不知道哪个是对的，或者哪个针对当前1.1.8可用。一个个实验下来，排列组合了不下100种可能，比如：

• 有人说layout add this line: my_attribute，另有人说是my_attribute
• 有人说要用$_product->getMyAttribute()，也有人说用$_product->getAttribute(‘my_attribute’)，也有人说用$_product->getData(‘my_attribute’)，也有人说用$_product->getAdditionalData(‘my_attribute’)，还有人说用$_product->getResource()->getAttribute(‘my_attribute’)->getFrontend()->getValue($_product))
• 还有人说Create separate module for your customization, Name it ‘Mycustomization’
  (can be changed).
  Then do this:
  1. Create file app/etc/modules/Mycustomization.xml

  <?xml version="1.0"?>
  <config>
  <modules>
  <Mycustomization>
  <active>
  true
  </active>
  <codePool>
  local
  </codePool>
  </Mycustomization>
  </modules>
  </config>
  

  2. Create folder app/code/local/Mycustomization and inside it app/code/local/Mycustomization/etc/

  3. Create file
  app/code/local/Mycustomization/etc/config.xml

  <?xml version="1.0"?>
  <config>
  <modules>
  <Mycustomization>
  <version>
  0.0.1
  </version>
  </Mycustomization>
  </modules>
  <frontend>
  <product>
  <collection>
  <attributes>
  <designer/>
  </attributes>
  </collection>
  </product>
  </frontend>
  </config>
  

  Once done on the frontend in all product collections you will have designer attribute loaded automatically.

• 还有Create a file app/etc/modules/category_product_attributes.xml with the following:

  <?xml version="1.0"?>
  <config>
  <frontend>
  <product>
  <collection>
  <attributes>
  <attributeyouwant/>//This is your attribute
  </attributes>
  </collection>
  </product>
  </frontend>
  </config>
  

• 等等

最后发现所有组合都不起作用，除非清除magento cache 让 layout xml 生效。

如果直接修改Magento的文件，Magento每次升级后，又要重新修改，所以这肯定不是个办法。以我最近一次修改/app/code/core/Mage/Core/Model/Email/Template.php为例，修改后Magento使用gmail smtp server来发送邮件。以下我使用update proof way重作一遍。(当前Magento版本是1.1.8)

1. 不直接修改/app/code/core/Mage/Core/Model/Email/Template.php，而是新建一个/app/code/local/(MyNameSpace)/Core/Model/Email/Template.php，其中(MyNameSpace)可以随意命名。

/app/code/local/(MyNameSpace)/Core/Model/Email/Template.php 是 /app/code/core/Mage/Core/Model/Email/Template.php的子类，其中我只重载了send方法，所以，/app/code/local/(MyNameSpace)/Core/Model/Email/Template.php不需要拷贝其他部分，它完整的内容是：

class (MyNameSpace)_Core_Model_Email_Template extends Mage_Core_Model_Email_Template {
public function send($email, $name=null, array $variables = array())
{
if(!$this->isValidForSend()) {
return false;
}

if (is_null($name)) {
$name = substr($email, 0, strpos($email, ‘@’));
}

$variables[’email’] = $email;
$variables[‘name’] = $name;

$mail = $this->getMail();
if (is_array($email)) {
foreach ($email as $emailOne) {
$mail->addTo($emailOne, $name);
}
} else {
$mail->addTo($email, ‘=?utf-8?B?’.base64_encode($name).’?=’);
}

$this->setUseAbsoluteLinks(true);
$text = $this->getProcessedTemplate($variables, true);

if($this->isPlain()) {
$mail->setBodyText($text);
} else {
$mail->setBodyHTML($text);
}

$mail->setSubject(‘=?utf-8?B?’.base64_encode($this->getProcessedTemplateSubject($variables)).’?=’);
$mail->setFrom($this->getSenderEmail(), $this->getSenderName());

$config = array(
‘ssl’ => ‘ssl’, //optional
‘port’ => 465, //optional – default 25
‘auth’ => ‘login’,
‘username’ => ‘your_email’,
‘password’ => ‘your_password’);

$transport = new Zend_Mail_Transport_Smtp(‘smtp.gmail.com’, $config);

try {
$mail->send($transport); //add $transport object as parameter
$this->_mail = null;
}
catch (Exception $e) {
return false;
}

return true;
}
}

2. 新建一个/app/code/local/(MyNameSpace)/Core/etc/config.xml，内容是

<?xml version=”1.0″?>
<config>
<modules>
<(MyNameSpace)_Core>
<version>1.0.0</version>
</(MyNameSpace)_Core>
</modules>
<global>
<models>
<core>
<rewrite>
<email_template>(MyNameSpace)_Core_Model_Email_Template</email_template>
</rewrite>
</core>
</models>
</global>
</config>

据说因为Zend Framework的一个bug，tag <email_template>必须在一行内封闭，其间不得有多余的white space。我试过，确实如此。

3. 最后，在Magento注册本次重载：新建一个/app/etc/modules/(MyNameSpace)_Core.xml，内容是：

<?xml version=”1.0″?>
<config>
<modules>
<(MyNameSpace)_Core>
<active>true</active>
<codePool>local</codePool>
</(MyNameSpace)_Core>
</modules>
</config>

我只是以重载一个model class为例，重载block class也是同样步骤。按Magento的说法，重载controller class有点区别，我尚未亲试。