• Hello,

    I am using Events Manager (version 7.2.3.1) with the Bridge theme (child theme active) on WordPress. I would like to report a bugs I have found in the Calendar view.

    In Calendar view mode, the month name is displayed correctly for the current month (e.g. April 2026), but disappears when navigating to subsequent months. Specifically, the behavior I observed is the following:

    • April 2026: month name visible ✓
    • May 2026: not visible ✗
    • June 2026: not visible ✗
    • July 2026: not visible ✗
    • August 2026: not visible ✗
    • September 2026: not visible ✗
    • October 2026: not visible ✗
    • November 2026: visible ✓
    • December 2026: not visible ✗
    • January 2027: visible ✓
    • February 2027: visible ✓
    • March 2027: visible ✓
    • April 2027: visible ✓

    If I continue navigating forward past April 2027, the calendar gets stuck showing January 2027 regardless of which month is actually displayed.

    The DOM updates correctly — the input’s value and data-month-value attributes change as expected — but the text is not rendered visually for the affected months.

    Through browser DevTools I verified that:

    • The color and webkit-text-fill-color are correctly applied
    • The opacity is 1
    • The computed width of the input is correct (around 140px)
    • The overflow-x and overflow-y of the input are set to ‘clip’
    • No JavaScript errors appear in the console

    I also checked the flatpickr locale file (includes/external/flatpickr/l10n/it.js) and the month names are all correct and complete.

    This issue may be related to a previously reported topic on this forum: https://wordpress.org/support/topic/wrong-data-month-value-in-events_calendar/
    In that topic, a user identified that the month name is being overwritten by a function call in events-manager.js (around line 2638) which initializes flatpickr with the monthSelectPlugin using shorthand: true. This shorthand setting uses abbreviated month names, and in Italian some abbreviations may be longer than expected, potentially causing the rendering issue.

    Thank you for looking into this

    The page I need help with: [log in to see the link]

You must be logged in to reply to this topic.