• Resolved johnwebman

    (@johnwebman)


    Don’t know if anyone else is experiencing this, but having updated to Version 3.1.34, I just get a blank page when I go to the Field Editor.

    I also note that when creating a new event, the “event expiry date” is no longer set to same date as “end date” automatically. It’s just left blank.

    • This topic was modified 1 year, 6 months ago by johnwebman.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wpemhelp

    (@wpemhelp)

    Hi,

    There could be some technical issue that is causing this. Please open a support ticket by following this link: https://wp-eventmanager.com/help-center/

    We’ll take up your issue and resolve it as quickly as we can.

    Thank You.

    Best Regards.

    Hi @johnwebman

    This has been resolved in the updated version.
    Please install this: https://github.com/wpeventmanager/wp-event-manager/tree/3_1_35

    Regards,
    Priya

    Thread Starter johnwebman

    (@johnwebman)

    Hi Priya,

    Thanks for this. I see that the field editor is fixed in this version. However, One of the issues in ver 3.1.34 was that the Listing Expiry Date is no longer being auto completed from the End Date, (as it was in ver 3.1.33), whenever you post a new event. This issue is still apparent in ver 3.1.35, and thus is still not a viable option for me. I also note that the plugin still shows as ver 3.1.34 in my list of installed plugins, even though it’s supposed to be ver 3.1.35.

    Regards,
    John

    Not sure why this ticket is marked as resolved? I am still getting a blank field editor. One. Month. Later.

    Thread Starter johnwebman

    (@johnwebman)

    @plymouthdesign
    It’s fixed in ver 3.1.35 referenced above. Unfortunately there are still other issues in that version so it hasn’t been released publicly yet.

    Plugin Author Rita Kikani

    (@kikanirita)

    Hello @plymouthdesign , @johnwebman , we already resolve field editor bug in current version 3.1.36.

    And for event expiry date on frontend, we will resolve and release in next version.

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bug in Version 3.1.34’ is closed to new replies.