• Hey Folks,

    I ran into a problem regarding WP-Eventmanager, RSVP Dates and SQL:

    The problem i’m tring to fix: sometimes we copy events and forget to manually change the RSVP date, which then leads to future events not beeing bookable since the RSVP date is – accidentally – set in the past.

    The solution I came up with: run a Cronjob with an SQL command, that automatically sets all RSVP Dates = Event Start dates in the database.

    So far, so good. The Cronjob works and sets the date in the database accordingly.

    HOWEVER, here’s the problem:

    even though in the database i set “event_rsvp_date=event_start_date”, the event is still not bookable. If I open the event in the wordpress backend, the input form still shows the “old” rsvp date.

    Example:

    Today is 15th of november. I have an event, start date is 30th of november. The rsvp date is set to 1st of november, therefore I cant book the event.

    I run the Cronjob, in the database the rspv set is set to 30th of november (rsvp date = event start date, I confirm via MySQL). The event though is still not bookable. If I open the event in the WP Backend, the input field for rsvp date still shows “november 1st”.

    What’s going on here? Is there something I’m missing? Or am I on the wrong track and there is a more elegant approach?

    Any help would be appreciated ?? Thanks!

  • The topic ‘Problem with SQL and RSVP Dates’ is closed to new replies.