View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006955 | module PayPal | module PayPal - sub | public | 2019-02-22 15:47 | 2019-04-18 17:56 |
| Reporter | Stefan_Werner | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 5.2.3 | ||||
| Fixed in Version | 5.2.4 | ||||
| Summary | 0006955: Empty payment methods are created if used in auto module activation enviroment | ||||
| Description | Empty Payment methods are created if you use config export and import on OXID SDK | ||||
| Steps To Reproduce | Export config with disabled paypal module import config Empty Payment method created Best to reproduce on OXID eShop SDK | ||||
| Additional Information | to fix oxideshop/source/modules/oe/oepaypal/Core/Events.php::disablePaymentMethod() add an if /** * Disables PayPal payment method */ public static function disablePaymentMethod() { $payment = oxNew(\OxidEsales\Eshop\Application\Model\Payment::class); if ($payment->load('oxidpaypal')) { $payment->oxpayments__oxactive = new \OxidEsales\Eshop\Core\Field(0); $payment->save(); } } | ||||
| Tags | No tags attached. | ||||
|
|
As far as I understand there are three steps, which have to be done: 1) Export the config. 2) Import the config. 3) Auto-activate the modules (with a module). All three steps are linked to third-party modules, like the ones from the OXID SDK. The functionalities - im-/export as well as auto-activation - are not part of the standard tool kit of an OXID eShop. The so called OXID SDK modules are also not maintained by OXID itself. Furthermore I identify the problem in the task chain of the im-/export behavior. The module exports only the config values for the PayPal module but not the refered payments. Then you import these config values into another shop. After that the auto activation is used and triggers the onActivate-Event from the PayPal module which can't find the relevant payment methods which are refered by the config values. To sum it up, I'm unable to identify a wrong behavior in the PayPal module. I would say that it's more of a difficulty in the im-/export module. Since it is a very special use case, there might be some misunderstanding on my side. If this is the case, I would appreciate some more feedback from you. [sp] |
|
|
Hello, the PR with a fix is merged: https://github.com/OXID-eSales/paypal/pull/50 |
