🚀 Optimize facilitator feedback counts retrieval and add caching

This commit improves the performance of the facilitator feedback counts feature by introducing a caching mechanism. It replaces the direct database query with a pre-computed and cached result, reducing database load and improving response times for the facilitators view.

🔒️ Exclude sensitive form data from environment YAML output

📝 Add Stripe user ID to organisation views for better identification

This commit adds the Stripe user ID to the organisation views, improving the ability to identify and manage Stripe connections. The ID is now displayed alongside the account name in both the _buttons partial and the build view.

✨ Add ticket price to the displayed information in event orders

This commit enhances the user experience by including the ticket price alongside the ticket type name in the event orders view. The price is displayed using the discounted price and currency of the ticket, providing more comprehensive information at a glance.

♻️ Simplify resale logic in payment_completed! method

Remove unnecessary order check and refactor condition for ticket refund and destruction during resale process to improve code clarity and efficiency.

✨ Introduce payment completion logic for individual tickets

This commit introduces a new method payment_completed! in the Ticket model to handle post-payment actions for each ticket. The method is called for each ticket when an order's payment is completed, ensuring that all necessary actions are performed on a per-ticket basis.

✨ Add ticket resale functionality for events

This commit introduces a new feature allowing event organizers to enable ticket resales. The changes include:

1. New 'enable_resales' field for events
2. Toggle resale endpoint for individual tickets
3. UI updates to display resale status and actions
4. Logic to handle resale purchases and refunds

These changes improve the flexibility of ticket management for both organizers and attendees, allowing for better event participation.

🍱 Add advisor images and update contact page with advisor section

♻️ Refactor local group assignment in Organisationship after_create hook

This commit improves the robustness of the local group assignment process in the Organisationship model. It replaces the create method with find_or_create_by to prevent duplicate entries, and adds error handling to catch and report any database operation failures.

⚙️ Add process_timeout option to Cuprite driver configuration

🚀 Add OpenAI integration and optimize video creation process

This commit introduces OpenAI integration and improves the video creation process. Here's a breakdown of the changes:

1. Add 'ruby-openai' gem to Gemfile
2. Configure OpenAI in boot.rb
3. Optimize Pace.js usage in app.js and _head.erb
4. Refine narration in gathering creation test
5. Streamline video generation process in test_config.rb

🚨 Add error logging for MaxMind download failures

💰 Increase contribution requested per event from £20 to £25

This change updates the standard contribution amount requested for each event from £20 to £25. This adjustment likely reflects a need to cover increasing costs or to better support the organization's activities.

🐛 Fix waitlist addition check in events controller

This commit improves the reliability of the waitlist addition process by changing the condition that checks if a user was successfully added to the waitlist. Instead of checking if the newly created waitship is persisted, we now verify if the waitship exists in the database by querying for it directly. This change ensures a more accurate confirmation of the waitlist addition.

🐛 Increase sleep duration in Squarespace account creation task

This commit increases the sleep duration from 10 to 30 seconds in the Squarespace account creation task. This change is made to allow more time for the account creation process to complete, reducing the likelihood of false negatives when checking for the newly created account.

🐛 Fix access to deleted events and related data

This commit addresses an issue where deleted events and their associated data (orders, tickets, donations) were not accessible in certain views. The changes ensure that administrators can view and manage this data even for deleted events, improving data accessibility and management.

♻️ Refactor StripeCharge balance and fee calculation methods

Rename methods for clarity and consistency: - calculate_balance to balance_from_transactions - calculate_fees to fees_from_transactions

Update task to use new method names when setting balance and fees.

This change improves code readability and better reflects the methods' functionality, deriving values from transactions rather than calculation.

⚡️ Optimize event accounting methods with memoization

This commit improves performance by implementing memoization for several methods in the EventAccounting module. The changes include:

1. Refactoring instance variable creation in profit_share_roles method
2. Adding memoization to credit_applied, credit_on_behalf_of_organisation, credit_on_behalf_of_revenue_sharer, fixed_discounts methods
3. Implementing memoization for discounted_ticket_revenue
4. Optimizing donation_revenue, organisation_discounted_ticket_revenue, and revenue_sharer_discounted_ticket_revenue with conditional memoization

These optimizations will reduce unnecessary recalculations and improve overall performance of the event accounting system.

⚡️ Implement memoization for expensive calculations in EventAccounting and StripeCharge

This commit improves performance by implementing memoization for expensive calculations in the EventAccounting module and StripeCharge model. The changes reduce redundant computations by caching results of method calls, which can significantly speed up subsequent accesses to the same data.

✨ Add partials for event stats row components

This commit introduces a series of partials for each component of the event stats row. This refactoring improves code organization, readability, and maintainability by breaking down the large _event_stats_row.erb file into smaller, more manageable pieces.

The changes include:

1. Creating separate partial files for each component of the event stats row.
2. Updating the main _event_stats_row.erb file to use these new partials.
3. Passing necessary local variables to each partial.

This modular approach allows for easier updates and modifications to individual components of the event stats row in the future.