This commit enhances the bib management system by updating the CSS layout for quantity and end inputs, ensuring proper alignment and display. It also modifies PHP functions to introduce a new column for the "or" separator between quantity and end values, improving the user interface. Additionally, new SQL entries are added to support the updated functionality, including localized labels and hints for user guidance. These changes aim to improve usability and clarity in the bib input process.
This commit introduces new JavaScript functions and PHP methods to enhance the handling of range inputs for quantity and end values in the bib management system. It includes the addition of input fields for quantity and end values, along with logic to manage their states based on user interaction. The CSS is updated to support the new layout and visual states for these fields. Additionally, data attributes are added to improve the handling of range validation and preview functionality. These changes aim to improve user experience and data integrity in the bib input process.
Update participant statistics queries in fxInfosBibRange and fxInfosBibEpreuve functions
This commit modifies the SQL queries in the `fxInfosBibRange` and `fxInfosBibEpreuve` functions to improve the accuracy of participant statistics. The `nb_utilises` count now reflects distinct bib numbers, ensuring correct tallying for teams sharing bibs. Additionally, the logic for fetching event statistics is refined to handle team configurations more effectively, enhancing the overall data retrieval process. These changes aim to improve data integrity and clarity in participant reporting.
This commit updates the loading mechanism for event statistics in the promoteur hub by introducing a new inline loader with an image and message. It also improves the AJAX loading process by adding a wait message and ensuring the loader is displayed during data fetching. Additionally, the error handling for AJAX requests is refined to hide the loader upon completion, enhancing user experience and clarity in the loading process.
This commit removes the `fxTraceCompte` functionality from various locations in `compte.php`, `inc_fx_compte.php`, and other related files to streamline the account management flow. The tracing logic is eliminated to enhance performance and reduce complexity. Additionally, the session handling for login redirection is improved by simplifying the logic and removing unnecessary function calls. These changes aim to improve maintainability and clarity in the account management system.
This commit introduces a new function, `fxSuperadmRedirectToLoginIfNeeded`, to streamline the login redirection process for superadmin users. It enhances session management by checking for user authentication and allowing legacy account access under specific conditions. Additionally, the login flow is updated to ensure users are redirected appropriately after login, improving the overall security and user experience in the superadmin interface. These changes aim to enhance maintainability and clarity in session handling across various superadmin pages.
This commit introduces new functions for logging and host validation in the account tracing system, improving the ability to track user actions in development and pre-production environments. Additionally, it adds a bootstrap function call in inc_start_time.php to initialize tracing early in the request lifecycle. These changes aim to enhance debugging capabilities and ensure reliable logging across different environments.
This commit updates the account tracing logic by adding a check for both development and pre-production environments to determine if tracing is enabled. Additionally, it introduces a fallback error logging mechanism to capture log entries when the log file is not writable, improving the robustness of the tracing functionality. These changes aim to enhance debugging capabilities and ensure reliable logging in various environments.
This commit introduces comprehensive tracing functionality to the account management flow by adding calls to `fxTraceCompte` and `fxTraceCompteRedirect` at key points in the login and routing processes. The changes improve the tracking of user actions and session states, facilitating better debugging and monitoring of account-related activities. Additionally, the promoteur hub event retrieval function is updated to include tracing, enhancing visibility into hub interactions. These updates aim to improve maintainability and user experience in the account management system.
This commit enhances the session management and redirect behavior in the login process. It introduces a new function, `fxCompteRedirectAfterLoginConsume`, to streamline the handling of post-login redirects while preventing loops for login-related pages. Additionally, comments are updated for clarity regarding the session's role in protecting access to certain pages. These changes aim to improve user experience and maintainability of the authentication flow.
This commit simplifies the `fxPromoteurHubShouldUse` function by directly returning the result of `fxPromoteurHubIsAvailable`, enhancing code readability. Additionally, comments in `compte.php` are updated to clarify the landing behavior for the promoteur hub and participant home, improving understanding of the session handling logic. These changes aim to streamline the promoteur hub functionality and improve maintainability.
This commit updates the promoteur hub functionality by introducing a new function, `fxPromoteurHubIsAvailable`, to streamline the logic for determining hub access. The existing `fxPromoteurHubShouldUse` function is modified to incorporate this new check, improving clarity and maintainability. Additionally, comments are added to clarify session handling in the `fxLoginCompte` function, ensuring better understanding of public login behavior. These changes aim to enhance the robustness of the promoteur hub interface and improve code readability.
This commit updates the connection timeout for MySQL operations and introduces new functions for managing connection errors and flash messages. The `fxStaticSyncConnectError` and `fxStaticSyncFormatConnectionError` functions provide clearer error reporting during synchronization. Additionally, the user interface is improved to display relevant flash messages, enhancing the overall user experience and robustness of the synchronization workflow.
This commit modifies key column references in the `fxStaticSyncTableDefinitions` function to align with updated database schema identifiers. Additionally, it introduces a new utility function, `fxStaticSyncKeyColumnsValid`, to validate key columns before executing queries, improving error handling in the `fxStaticSyncFetchRowsByKey` and `fxStaticSyncLoadKeyedRows` functions. The changes aim to enhance the robustness of the synchronization process and provide clearer error feedback during data operations.
This commit introduces several new functions to enhance the static synchronization process, including `fxStaticSyncNormalizeCellValue`, `fxStaticSyncSqlOrderByKeys`, and `fxStaticSyncGetTableRowCount`. These additions improve data handling and error reporting during synchronization. The `fxStaticSyncLoadKeyedRows` function is updated to provide more detailed feedback on physical and duplicate row counts, while the user interface is enhanced to display duplicate key counts in the source data. Overall, these changes aim to improve the robustness and clarity of the database synchronization workflow.
This commit eliminates the need for database name confirmation when syncing to client environments, simplifying the user experience. The `fxStaticSyncRequiresDbConfirm` function is removed, and related logic is adjusted in the synchronization workflow. Additionally, the user interface is updated to reflect these changes, providing clearer messaging about the synchronization process and reinforcing the read-only nature of the client production environment.
This commit renames and refines several functions related to data synchronization, enhancing the clarity of status reporting. The `fxStaticSyncResolveDataStatus` function is replaced with `fxStaticSyncFinalizeCompareResult`, which consolidates status determination logic. Additionally, user feedback is improved in the synchronization process, with clearer messages regarding data discrepancies and alignment. These changes aim to streamline the synchronization workflow and enhance overall user experience.
This commit introduces new functions for confirming database names during synchronization, enhancing safety when syncing to production environments. The `fxStaticSyncResolveDataStatus` and `fxStaticSyncFormatDataDiffSummary` functions are added to provide clearer status reporting and summaries of data discrepancies. Additionally, the synchronization process is refined to improve user feedback, including clearer messages regarding data alignment and discrepancies. These changes aim to enhance the robustness and clarity of the database synchronization workflow.
This commit introduces new functions for resolving and comparing database schema columns, allowing for better handling of structural discrepancies during synchronization. The `fxStaticSyncCopyTable` function is updated to check for schema alignment before proceeding with data copying, providing clearer error messages when structures do not match. Additionally, the synchronization process is refined to allow for read-only operations towards production environments, enhancing safety and user feedback. Overall, these changes aim to improve the robustness and clarity of the database synchronization workflow.
This commit introduces several utility functions for database synchronization, including error handling for MySQL operations and retrieval of table metadata. The `fxStaticSyncDbLastError`, `fxStaticSyncExecQuery`, `fxStaticSyncGetTableColumnNames`, and `fxStaticSyncGetTableEngine` functions are added to improve the robustness of the synchronization process. Additionally, the `fxStaticSyncCopyTable` function is updated to handle column mismatches more gracefully and to provide clearer feedback on the synchronization results, enhancing overall user experience and error reporting in the database synchronization workflow.
This commit updates the ChronoTrack API configuration by introducing a variable for the base URL, allowing for easier management of test and production environments. It also improves the admin interface to display the API endpoint status, indicating whether the test or production API is in use. Additionally, error handling in the OAuth token fetching process is enhanced to provide clearer messages when access tokens are absent or when errors occur, improving overall user feedback and robustness of the API.
This commit refines the configuration of the ChronoTrack API by introducing a variable for the base URL, allowing for easier adjustments. It also adds a conditional definition for the token key based on the environment, ensuring appropriate settings for both test and production environments. Additionally, the admin interface is updated to display the API endpoint when configured, enhancing user feedback and clarity. These changes aim to improve the overall configuration management and user experience within the API.
This commit introduces new features for handling orphan entries within the ChronoTrack API. It adds a new endpoint for syncing orphan entries, enhancing the ability to identify and manage entries that are present in the system but not eligible for transfer. The user interface is updated to include a dedicated section for displaying orphan entries, improving clarity and user interaction. Additionally, the synchronization logic is refined to compute and report orphan entries effectively, aiming to enhance overall data management and user experience in the API.
This commit introduces new functions for handling PUT requests within the ChronoTrack API, improving the management of entry updates. It includes the implementation of payload processing functions for both POST and PUT requests, ensuring that entry IDs are appropriately excluded from the payloads. Additionally, the synchronization logic is refined to differentiate between creating and updating entries, enhancing the overall clarity and efficiency of the API. These changes aim to streamline entry management and improve user experience in the API.
This commit updates the ChronoTrack API push process by refining the user interface messaging for manual pushes, clarifying the status of participants, and improving the confirmation prompts. Key changes include the introduction of new variables for tracking eligible participants and orphans, as well as enhanced HTML output for better clarity on the current state of entries. These improvements aim to streamline the push process and enhance the overall user experience in managing participant data.
This commit introduces a new UI structure for the superadmin interface by implementing the fxSuperadmV2Panel functions, which improve the organization and presentation of event access and ChronoTrack API sections. The changes include the addition of collapsible panels for better user interaction and visual clarity. Additionally, the versioning in the settings file is updated to reflect the latest changes. These enhancements aim to streamline the user experience and improve the overall functionality of the superadmin interface.
This commit improves session management within the superadmin interface by introducing a new session validation function that ensures active sessions are maintained and provides JSON responses for session expiration. Additionally, the session timeout duration is standardized, and user feedback is enhanced with alerts for expired sessions. The codebase is streamlined by removing deprecated session handling logic, improving overall clarity and maintainability. These changes aim to enhance user experience and ensure robust session handling across the application.
This commit streamlines the entry management process within the ChronoTrack API by removing deprecated functions related to entry withdrawal and deletion. The admin interface is updated to eliminate unused actions, enhancing clarity and usability. Additionally, comments are refined to improve code readability. These changes aim to simplify the codebase and improve the overall user experience in managing entries.
This commit introduces new functions for managing entry withdrawal within the ChronoTrack API, including the ability to probe and withdraw entries based on their status. The admin interface is updated to include buttons for testing withdrawal actions, providing clearer user feedback. Additionally, the synchronization logic is enhanced to summarize entry statuses and handle batch withdrawals more effectively. These changes aim to improve the overall management of entries and enhance user experience in the API.
This commit improves the entry deletion process within the ChronoTrack API by introducing a new function to handle deletion attempts with context requirements. It also enhances session management by implementing a session validation function that provides JSON responses for session expiration, improving user feedback during AJAX calls. Additionally, the synchronization logic is updated to utilize the new deletion function, ensuring better error handling and reporting. These changes aim to streamline entry management and enhance the overall user experience within the API.
This commit modifies the entry wipe functionality in the ChronoTrack API admin interface. The wipe button is now disabled when there are no entries to delete, and the confirmation prompt has been updated to clarify the action's scope. Additionally, the API response for the wipe action now returns a warning state when no entries are found, providing clearer messaging about the visibility of entries. These changes aim to improve user experience and ensure accurate communication regarding entry management.
This commit introduces improvements to the entry synchronization process within the ChronoTrack API. Key changes include the renaming of functions for clarity, the implementation of pagination for fetching entries, and enhanced reporting of entry counts before and after synchronization actions. Additionally, the admin interface is updated to provide clearer feedback regarding the state of entries, including details on entries found before a wipe and remaining entries after synchronization. These enhancements aim to improve the overall user experience and data management capabilities of the API.
This commit introduces a new feature to wipe all entries from ChronoTrack Live for a specific event, including user confirmation prompts and error handling. Additionally, it enhances the participant synchronization process by refining the handling of entry data and improving the reporting of synchronization results. The admin interface is updated to include a new button for the wipe action, providing clearer user feedback and control over event data management. These changes aim to streamline the management of ChronoTrack entries and improve the overall user experience within the API.
This commit introduces new functions to better manage team-related data during participant synchronization. Key updates include the addition of team identification and role labeling, as well as improved handling of blocked team registrations. The participant summary now includes team-specific fields, enhancing the clarity of participant data. Additionally, the admin interface is updated to provide clearer messaging regarding blocked team registrations, improving user feedback during synchronization processes. These changes aim to streamline participant management and enhance the overall user experience within the ChronoTrack API.
This commit introduces a new function to classify blocked participants by type, improving the handling of synchronization errors related to missing or invalid data. The changes include updates to the participant classification logic, allowing for better reporting of issues such as duplicate bibs, missing external IDs, and unmapped races. Additionally, the push preview functionality is enhanced to display blocked participants clearly, improving user feedback during the synchronization process. These updates aim to streamline participant management and enhance the overall user experience within the ChronoTrack API.
This commit updates the MS1 loader to include a message parameter for inline HTML usage, ensuring consistent messaging during AJAX operations. Additionally, new functions are introduced to render loading indicators and assets, improving user feedback during data synchronization processes. The integration of these features aims to enhance the overall user experience and clarity within the ChronoTrack API admin interface.
This commit introduces a new 'sync_probe_push' action to the ChronoTrack API, allowing for the probing of participant data synchronization. It includes a new button in the admin interface for initiating probe pushes, along with improved error handling in the API response messages. Additionally, the batch size for synchronization is adjusted, and the entry payload building process is refined to include event IDs and registration choices, enhancing the overall synchronization capabilities and user experience.
This commit updates the ChronoTrack API to improve event handling and synchronization features. Changes include enhanced messaging for closed events, adjustments to the push panel functionality, and refined status handling for event synchronization. The logic for managing event states is streamlined, allowing for clearer user interactions and better management of synchronization processes. These improvements aim to enhance the overall usability and effectiveness of the ChronoTrack API in event management.
This commit introduces new synchronization features to the ChronoTrack API, including the ability to preview and push participant data to ChronoTrack. A new push panel is added to the admin interface, allowing users to view eligible participants and initiate synchronization. Additionally, backend functions are implemented to handle synchronization requests, enhancing the overall data management capabilities of the API. These changes aim to streamline the process of updating participant information within the ChronoTrack system.
This commit introduces several enhancements to the ChronoTrack API, focusing on entry handling and diagnostic capabilities. New functions are added to normalize and summarize entry data, improving the management of entry-related information. Additionally, the diagnostic functionality is updated to include entry endpoints, providing more comprehensive insights during API diagnostics. These changes aim to enhance the overall usability and effectiveness of the ChronoTrack API for event management.
This commit introduces new entries for the 'inscriptions_pays' and 'inscriptions_provinces' tables in the fxStaticSyncTableDefinitions function. Each entry includes a label, keys, and columns to ignore, enhancing the static synchronization configuration for better data management.
This commit enhances the ChronoTrack API by refining functions related to race and registration choice entities. Key updates include the introduction of new functions for collecting race and registration choice entities, improved normalization logic, and adjustments to existing functions for better clarity and functionality. Additionally, terminology is updated to ensure consistency across the API, enhancing overall usability and integration with the ChronoTrack system.
This commit introduces a new diagnostic feature in the ChronoTrack API, allowing users to run diagnostics on events and retrieve detailed reports. The functionality includes a new diagnostic panel in the admin interface, which displays API diagnostic results, including OAuth status and endpoint responses. Additionally, the backend is updated to handle diagnostic requests, ensuring comprehensive error handling and reporting. This enhancement aims to improve troubleshooting and support for event management within the ChronoTrack system.
This commit updates the ChronoTrack API admin interface to incorporate support for registration choices, enhancing the functionality of race mapping. Terminology is refined throughout the interface, replacing "race" with "course" where appropriate to improve clarity. New functions are added to handle registration choices, ensuring a more comprehensive integration with the ChronoTrack API. Additionally, existing functions are modified to accommodate these changes, improving overall user experience and interaction.
This commit introduces a new function to render an event link picker in the ChronoTrack API admin interface, allowing users to search and select events more efficiently. The event page rendering logic is updated to conditionally display the link picker based on event status. Additionally, the race mapping display is enhanced to show saved mappings more clearly, improving user interaction and overall experience when managing events.
This commit enhances the ChronoTrack API admin interface by adding a status display for race loading and a button to reload races. The status updates provide user feedback during the loading process, indicating success or failure. Additionally, the race loading logic is improved to handle network errors gracefully, ensuring a better user experience when interacting with the API.
This commit adds comments in the `inc_settings.php` file to clarify the default values for ChronoTrack API credentials and their intended usage. It also notes that the credentials can be overridden by other switch blocks, improving the understanding of the configuration process for developers.
This commit corrects a syntax error in the `inc_settings.php` file by adding a missing quotation mark to the `service_pass` entry. This change ensures proper parsing of the credentials, maintaining the integrity of the ChronoTrack API configuration.
This commit updates the ChronoTrack API configuration in the `inc_settings.php` file by adding the client ID, client secret, service user, and service password. These changes are essential for establishing a connection with the ChronoTrack API, ensuring proper functionality and access to its features.
