Eventixa Team

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [Eventixa – Event Calendar, Event Tickets, Registration & Booking] Changing the payment currency fails.
    Plugin Author Eventixa Team

    (@eventixa)

    1 month ago

    Hi Gasoj,

    Thanks for reporting this. You were right—the currency validation wasn’t handling non-default currencies correctly. We’ve fixed the issue, and it will be included in the next plugin update (10th August).

    If this is urgent for your site, please open a support ticket through our website’s Contact/Support page and mention this forum topic. We’ll do our best to prioritize the release and get the fix out as quickly as possible.

    We’re always here to help, so please don’t hesitate to reach out if you have any questions or run into any other issues.

    Thanks again for helping us improve Eventixa!

    Forum: Plugins
    In reply to: [Eventixa – Event Calendar, Event Tickets, Registration & Booking] single meta key for the start and end date/time?
    Plugin Author Eventixa Team

    (@eventixa)

    1 month ago

    Hi Gasoj,

    Thank you for taking the time to share your suggestion.

    We understand the reasoning behind storing combined datetime values such as _evx_start_datetime and _evx_end_datetime, along with a duration field. These can certainly be useful in some scenarios, particularly for custom WP_Query implementations and third-party integrations.

    That said, we’d like to provide some context on how Eventixa currently works internally.

    Eventixa does not rely on separate postmeta date and time fields for its primary frontend event operations. Instead, the plugin maintains a dedicated occurrences/index "_evx_occurrences" table that stores normalized start and end datetimes for each event occurrence. This table is specifically designed for efficient event queries and is used throughout the frontend.

    This allows Eventixa to efficiently power features such as:

    • Upcoming Events
    • Ongoing Events
    • Past Events
    • Event archive listings
    • Event calendars
    • Date-based filtering
    • Multi-day and recurring event occurrences
    • Event ordering by start date/time
    • Time-based event lookups

    Using a dedicated occurrences table also avoids the multiple postmeta joins that would otherwise be required for querying separate date and time values, while providing much better scalability for recurring events and larger event datasets.

    Because of this architecture, adding additional combined datetime meta fields would not improve Eventixa’s own frontend query performance. Those values would primarily serve as convenience metadata for developers, custom queries, or third-party integrations rather than improving the plugin’s core operation.

    Regarding _evx_duration, the same principle applies. Since Eventixa already calculates and maintains event durations internally where needed, storing a separate duration meta would mainly provide an additional convenience value rather than reducing processing within the plugin itself.

    Thanks again for taking the time to share your feedback and suggestions. We really appreciate users who test the plugin thoroughly and help us improve it. If you have any other ideas or run into any issues, please don’t hesitate to let us know.

Viewing 2 replies - 1 through 2 (of 2 total)