覆盖 Magento 社区模块控制器的问题
首先,这里的答案非常有帮助:在社区扩展中覆盖 Magento 控制器
First of all, the Answer here is very helpful: Overriding a Magento Controller in community extention
然而,尽管通过了答案中提到的两个测试",我仍然有一个模块控制器覆盖,它只是拒绝工作.这是我所拥有的:
However, despite passing both of the "tests" mentioned in the answer there, I still have a module controller override that just refuses to work. Here is what I have:
appcodelocalCompanyOnepageCheckoutetcconfig.xml
<?xml version="1.0"?>
<config>
<modules>
<Company_OnepageCheckout>
<version>0.0.1</version>
</Company_OnepageCheckout>
</modules>
<frontend>
<routers>
<onepagecheckout>
<args>
<modules>
<company_onepagecheckout before="IWD_OnepageCheckout">Company_OnepageCheckout</company_onepagecheckout>
</modules>
</args>
</onepagecheckout>
</routers>
</frontend>
</config>
appcodelocalCompanyOnepageCheckoutcontrollersIndexController.php
<?php
require_once(Mage::getModuleDir('controllers','IWD_OnepageCheckout').DS.'IndexController.php');
class Company_OnepageCheckout_IndexController extends IWD_OnepageCheckout_IndexController
{
function indexAction() {
die('Hello world!');
}
}
appetcmodulesCompany_OnepageCheckout.xml
<?xml version="1.0"?>
<config>
<modules>
<Company_OnepageCheckout>
<active>true</active>
<codePool>local</codePool>
<depends>
<IWD_OnepageCheckout />
</depends>
</Company_OnepageCheckout>
</modules>
</config>
此模块旨在覆盖位于 appcodecommunityIWDOnepageCheckout[...]
正如本文开头所提到的,我已经按照其他问题中的建议使用了 Reflection 类,并且可以在社区模块之前的数组中首先看到我的模块.但是,当我访问 mysite.com/onepagecheckout 时,我仍然看到社区模块,并且无法让它使用我的文件.
As mentioned at the top of this post, I've used the Reflection class as suggested in that other Question and can see my module first in the array ahead of the community module. However, when I visit mysite.com/onepagecheckout I still see the community module, and can't get it to use my file.
我的直觉是,这可能与我遗漏的模块名称的大写有关.
推荐答案
只需更改
<company_onepagecheckout before="IWD_OnepageCheckout">Company_OnepageCheckout</company_onepagecheckout>
到
<Company_OnepageCheckout before="IWD_OnepageCheckout">Company_OnepageCheckout</Company_OnepageCheckout>
如果它不起作用则使用
<global>
<!-- This rewrite rule could be added to the database instead -->
<rewrite>
<!-- This is an identifier for your rewrite that should be unique -->
<!-- THIS IS THE CLASSNAME IN YOUR OWN CONTROLLER -->
<mynamespace_mymodule_onepage_iwd>
<from><![CDATA[#^/onepagecheckout/index/#]]></from>
<!--
- mymodule matches the router frontname below
- checkout_cart matches the path to your controller
Considering the router below, "/mymodule/checkout_car/" will be
"translated" to "/MyNameSpace/MyModule/controllers/Checkout/CartController.php" (?)
-->
<to>/comonepagecheckout/index/</to>
</mynamespace_mymodule_onepage_iwd>
</rewrite>
</global>
<frontend>
<routers>
<comonepagecheckout>
<!-- should be set to "admin" when overloading admin stuff (?) -->
<use>standard</use>
<args>
<module>Company_OnepageCheckout</module>
<!-- This is used when "catching" the rewrite above -->
<frontName>comonepagecheckout</frontName>
</args>
</comonepagecheckout>
</routers>
</frontend>
在
See more at
相关文章