Magento 2 – Rewrite AccountManagement Model of Customer (ver. 0.42.0-beta2)

magento2magento2-dev-betamodel

I want to rewrite activate function of AccountManagement.I don’t know how to proceed.

A public interface is a set of code that third-party developers can call, implement, or pluginize. Magento guarantees that this code will not change in subsequent releases without a major version change.

Public interfaces for a module reside in the Api folder for a module. For example, the public interfaces for the Customer module reside in the app/code/Magento/Customer/Api folder. Third-party developers should use only these interfaces. You can use other interfaces but Magento does not guarantee that other interface will not be modified or removed in subsequent releases.

1.I need to rewrite AccountManagementInterface or AccountManagement?

2.It is necessary to use di.xml?

3.following is correct?

<preference for="Magento\Customer\Api\AccountManagementInterface"
                type="Mynamespace\Mymodule\Model\AccountManagement" />

Thanks in Advance.

Best Answer

The <preference> element in a di.xml file is the right approach. What you are doing is saying "use my type whenever you see a reference to the interface name in the merged di.xml file". So can supply any class that implements that interface. You could write this class from scratch (implementing the interface), or you could inherit the class we provide and override the one method with a new implementation (the class we provide implements the interface already).

Another approach is using plugins - you can intercept calls to an existing method without replacing the whole class, if that is appropriate. The advantage of plugins is you can add a bit of functionality to existing code easily, and if 3 different modules want to add functionality that will work as well. In comparison, only the last element will win - there can be only one class at the end of the day.

So you need to decide which approach best fits what you are trying to achieve. Since you are trying to rewrite a single function, you might want to look into plugins instead of using the <preference> element.

Related Solutions

Magento 1.8 – Rewrite Function from Core Model Class

To Future Readers:

The OP mentioned in their answer that they had a rewrite conflict with another third-party module. If you want your override to take precedence without refactoring third-party code you can add a module dependency.

In the app/etc/modules/MODULE_NAME.xml file add the following XML below the codePool tag

<depends>
    <DEPENDENT_MODULE_NAME/>
    ...
</depends>

List all the modules yours needs to take precedence over. Now your overrides will take effect rather than the other modules.

Note: If you do this you'll probably want to have your classes inherit from that module's classes so that you can preserve that module's functionality.

Model Rewrite Conflict in Two Magento Modules

Take a look at How to prevent module rewrite class conflict in Magento you seem to have a conflict

Try

Comment's config.xml where models rewrite is defined:

<global>
 <models>
  <!--sales> <-- remove
   <rewrite>
    <order>Beph_Comment_Model_Sales_Order</order>
   </rewrite>
  </sales-->
(...)

Date's config.xml where models rewrite is defined:

<global>
 <models>
  <sales>
   <rewrite>
    <order>Beph_Date_Model_Sales_Order</order>
   </rewrite>
  </sales>
(...)

Comment's Beph/Comment/Model/Sales/Order.php:

<?php
class Beph_Comment_Model_Sales_Order extends Beph_Date_Model_Sales_Order{
 public function hasCommentField(){
    $var = $this->getComment();
    if($var && !empty($var)){
        return true;
    }else{
        return false;
    }
 }
 public function getCommentFieldHtml(){
    $var = $this->getComment();
    return $var;
 }
}

Date's Beph/Date/Model/Sales/Order.php:

<?php
class Beph_Date_Model_Sales_Order extends Mage_Sales_Model_Order{
 public function hasDateField(){
    $var = $this->getDate();
    if($var && !empty($var)){
        return true;
    }else{
        return false;
    }
 }
 public function getDateFieldHtml(){
    $var = $this->getDate();
    return $var;
 }
}

Also since both module seem to do similar things, you may consider merging them

Best Answer

Related Solutions

Magento 1.8 – Rewrite Function from Core Model Class

Model Rewrite Conflict in Two Magento Modules

Related Topic