Okay
  Public Ticket #2848751
Incorrect recurring dates
Closed

Comments

  •  1
    Willard started the conversation

    when the month starts midweek (such as September 2021), if the client sets recurring dates from Wed, SEP 01 for MWF appointments, it includes AUG 30 as the 2nd appointment.

    This is a pretty fundamental error in the scheduling system. It counts backwards from the starting date to include a date *before* the first appointment.

    Please tell me how to correct this. Its completely ruining the billing structure for the appointments.

  • [deleted] replied

    Hi Willard,

    thank you for reaching out to us!

    That is very strange as dates should only go forward from the start date customer chooses.

    Can you please provide me a link to the booking page?

  •   Willard replied privately
  • [deleted] replied

    Hi Willard,

    thank you; please tell me, am I selecting the wrong date?

    I choose the 18th as a start date and receive 18th:

    4394445051.png


  •  1
    Willard replied

    If your start date is on Thurs the 19th, but your weekly recurring patterns are MTWTh, you will see appointments: 19th, 16th, 17th, 18th, 23rd.

    it is set to “recommend the closest dates after”—I don’t understand why it would be recommending dates before my starting date.

  • [deleted] replied

    Hi, Willard,

    Could you please provide us with a temporary WP Admin login, so we will be able to investigate the issue from the inside. You can post the credentials as a private reply to this ticket. 

    Looking forward to hearing from you. 

  •   Willard replied privately
  •  1
    Willard replied

    After trying all of the different recurringSub settings (and confirming that  change in the db), it looks like it is being ignored. On Disabled, it is still recommending different time slots.

    Please help.

  •   [deleted] replied privately
  •   Willard replied privately
  •   [deleted] replied privately
  • [deleted] replied

    Willard,

    I just received a response from our developers: it turned out there's a bug. It will be fixed in the next update.

    Sorry for this inconvenience.

    Please let us know if you have any further questions.

    Best Regards.