• Resolved mr2808

    (@mr2808)


    In EventPrime settings, the documentation for Frontend Time Format says: “Admin area time format is based on your WordPress settings.

    My WordPress is set to time format “H:i” (17:01).

    In the Edit Event screen, the input format is “g:i A” (05:01 PM).

    I guess, this is a bug because the WordPress setting is being ignored.

    Regards,
    Michael

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support epsupport1

    (@epsupport1)

    Hi Michael,

    Thank you for bringing this to our attention

    Could you please share the exact documentation link or reference where this statement is mentioned? This will help us review it in context.

    To clarify, EventPrime currently provides a 12-hour format option for the backend (admin area). For the frontend display, you can adjust the time format by navigating to EventPrime → Settings → General tab → Setup subtab → Frontend Time Format.

    Looking forward to your reply.

    • This reply was modified 5 months, 1 week ago by epsupport1.
    Thread Starter mr2808

    (@mr2808)

    Go to wp-admin/edit.php?post_type=em_event&page=ep-settings

    There you find “Frontend Time Format” with this documentation:

    Time format for frontend event lists and single event pages. Admin area time format is based on your WordPress settings.

    And WordPress is set to time format “H:i” (17:01) but not “g:i A” (05:01 PM).

    Plugin Support epsupport1

    (@epsupport1)

    Thanks for sharing the details.

    We’ve reviewed this at our end and confirmed that the backend (admin area) currently uses the 12-hour time format by default. The “Frontend Time Format” option under EventPrime → Settings applies only to event listings and single event pages on the frontend.

    We’ve forwarded this to our planning and development team for further review to ensure consistency between the backend and WordPress time format settings. Any required correction in functionality or plugin settings will be addressed in an upcoming update.

    Thank you for bringing this to our attention.

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

You must be logged in to reply to this topic.