feat: Implement complete ticket purchasing flow with new TicketsController

- Create new TicketsController with actions for name collection, creation, and checkout
- Add dedicated ticket views (new.html.erb, checkout.html.erb, show.html.erb)
- Update ticket_selection_controller.js to handle form submission via AJAX
- Add store_cart endpoint in EventsController for session-based cart management
- Update routes to support new ticket flow: /tickets/new, /create, /checkout
- Fix attribute name consistency across views (title→name, starts_at→start_time)
- Add Stripe checkout integration with proper error handling
- Remove deprecated collect_names flow in favor of streamlined approach

The flow is now: Event selection → AJAX cart storage → Name collection → Checkout → Payment
This commit is contained in:
kbe
2025-08-30 19:03:29 +02:00
parent 476438c5c4
commit 6ea3005a65
38 changed files with 1151 additions and 297 deletions

18
bin/test_stripe_check.rb Executable file
View File

@@ -0,0 +1,18 @@
#!/usr/bin/env ruby
# Test to simulate the exact check that's happening in the EventsController
puts "Testing the exact Stripe configuration check from EventsController..."
# Simulate the exact check
stripe_configured = Rails.application.config.stripe[:secret_key].present?
puts "Direct check result: #{stripe_configured}"
# Check the actual value
puts "Secret key value: #{Rails.application.config.stripe[:secret_key]}"
# Check if it's nil or empty
puts "Secret key is nil?: #{Rails.application.config.stripe[:secret_key].nil?}"
puts "Secret key is empty?: #{Rails.application.config.stripe[:secret_key].empty?}"
# Check the type
puts "Secret key class: #{Rails.application.config.stripe[:secret_key].class}"