- last update
8 months ago 12 pass - 🇺🇸United States msupko
I'm not really sure we need to set these values at all. If we don't call these methods, Commerce will automatically set these timestamps for us. Here's a patch that just removes this logic.
- 🇮🇱Israel jsacksick
Yes, we shouldn't be setting those values:
Payment::presave()
has the following code:if ($state == 'authorization' && $original_state != 'authorization') { if (empty($this->getAuthorizedTime())) { $this->setAuthorizedTime(\Drupal::time()->getRequestTime()); } } if ($state == 'completed' && $original_state != 'completed') { if (empty($this->getCompletedTime())) { $this->setCompletedTime(\Drupal::time()->getRequestTime()); } }
-
jsacksick →
committed f67445ae on 8.x-1.x
Issue #3302231 by sah62, msupko, jsacksick: Invalid Payment Authorized...
-
jsacksick →
committed f67445ae on 8.x-1.x
- Status changed to Fixed
4 months ago 9:30am 5 September 2024 Automatically closed - issue fixed for 2 weeks with no activity.