Closed (fixed)
Project:
Yoyaku Booking Engine
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Jul 2026 at 09:44 UTC
Updated:
22 Jul 2026 at 11:50 UTC
Jump to comment: Most recent
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.
Recreate the yoyaku_payment_views submodule over the Kessai payment entity:
kessai_payment, exposed to Views by kessai_views.subject_id to its booking transaction, so each payment is listed next to its order reference (the payments-and-orders integration).subject_type = yoyaku_transaction so only booking payments are listed.admin/booking/views/payments.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
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
Comment #3
mably commentedRecreated 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.
Comment #5
mably commented