The Kessai payment refit removed the yoyaku_payment content entity and the yoyaku_payment_views submodule that shipped the yoyaku_payments view. On sites that had that submodule enabled, the view config is left orphaned over a base table (yoyaku_payment) that no longer exists, so the payments admin listing crashes.

Fix

Recreate the yoyaku_payment_views submodule over the Kessai payment entity:

  • Base table kessai_payment, exposed to Views by kessai_views.
  • A Views relationship from the payment subject_id to its booking transaction, so each payment is listed next to its order reference (the payments-and-orders integration).
  • A non-exposed filter on subject_type = yoyaku_transaction so only booking payments are listed.
  • Columns: ID, Order (transaction reference), Amount, Currency, State, Created, with an exposed State filter. Page at admin/booking/views/payments.

Upgrade note (pre-1.0, no update hook)

Sites that had the old submodule must delete the orphaned view config and enable the new modules:

drush config:delete views.view.yoyaku_payments
drush en kessai_views yoyaku_payment_views

Issue fork yoyaku-3609249

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mably created an issue. See original summary.

mably’s picture

Status: Active » Needs review

Recreated the payments view over the Kessai payment entity in MR !5. Verified on a live site: the view lists booking payments joined to their order reference at admin/booking/views/payments, with no crash.

  • mably committed f325e62b on 1.x
    fix: #3609249 Restore the yoyaku_payments view after the Kessai payment...
mably’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.