>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3616969. --> Reported by: [mably](https://www.drupal.org/user/3375160) Related to !244 >>> <h3>Problem/Motivation</h3> <p>An offer is drawn on two surfaces. On the slot booking page it is a card, and yoyaku_booking_fee preprocesses that card to say beside the price that a charge is added, in the front's own wording and with no figure. On the seat map, the same tariff appears as a row in the panel beside the plan, and that row carried a label and a price and nothing else.</p> <p>So a booker who took a place off the plan read a price that was not the whole of what they would be charged, and met the fee for the first time at checkout. The same tariff on the booking page told them before they took anything.</p> <h3>Where it came from</h3> <p>VenueMapBuilder builds an area's bookable tariffs as a tariff, a label and a price, with the price left NULL because placement carries no reference to the payment module. yoyaku_payment fills the price in through hook_yoyaku_placement_map_alter, and a price was the only thing anything filled in. There was no key for a mention beside it, so a module with something to add to an offer on the plan had nowhere to put it.</p> <p>This is not the offer card's doing, and moving the card did not settle it: the panel builds its rows in the browser and cannot render a template, which is settled in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/yoyaku/-/work_items/3616886" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/yoyaku/-/work_items/3616886</a></span>. What the two surfaces share is the stepper, the queue and the notice, and not the markup.</p> <h3>The other half of this issue is already shipped</h3> <p>As filed, this also asked for the lines that say what is holding an offer back. <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/yoyaku/-/work_items/3616821" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/yoyaku/-/work_items/3616821</a></span> gave the plan those: a per-order allowance and an area with nothing left are both stated beside the stepper they stop, and the plus button is pointed at that region so it reads back the reason rather than going quiet. Nothing is left of that half, so this issue is the fee.</p> <h3>What shipped</h3> <p>Each tariff row of the map payload carries a priceNote beside its price, left NULL by placement, on the tariffs a seat may be booked at and on the tariffs that may book an area offered by quantity. yoyaku_booking_fee fills it through the map alter that already exists, in the class that preprocesses the card, so one class holds one rule: beside a charge, never on an offer costing nothing, never with a figure. It is ordered after yoyaku_payment, which fills the prices it reads; ordered by name it would run first and find every row free.</p> <p>The panel prints it where the card prints it, beside the area's price, and once under the running total. A seat is priced from a select whose options exist to be compared, and a mention repeated on every option is read out option by option for nothing, so for seats the total carries it: that is the number a booker checks against what they will be charged.</p> <h3>The keying it needed</h3> <p>The settled half of the payload is held until an operator changes something, and it was keyed by slot and content language only. What a booker is told about an offer is the front's to decide, so the entry is now keyed by the booking channel as well, and names that channel among its own dependencies together with the channel list, since a front keeps what it charges in settings on the channel itself. STATE_VERSION is bumped.</p> <p>The map alter's documentation said it ran per request, which stopped being true when <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/yoyaku/-/work_items/3616821" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/yoyaku/-/work_items/3616821</a></span> moved it onto the cached half. It now says what it is, and what an implementation may vary by: the slot, the content language and the front, and nothing else.</p> <h3>Remaining tasks</h3> <ul> <li>Review MR !244.</li> </ul> <p>AI-Generated: Yes (Claude Code wrote the code and the tests on the merge request, and drafted this issue summary. I reviewed both before posting.)</p>