Closed tcavaletto closed 4 years ago
This happened to us as well. It took past reservations (looks like almost all of them going back to when we installed the plugin) and changed the status on all of them back to Pending Review - that means that everyone received a notification and we have to go back and approve all of them - which means everyone will receive another email.
@marcierempel Could you give me a screenshot of the history on one of these reservations? I'll be digging into this issue this weekend and a reference point would be extremely helpful.
I wondered if it had something to do with the Populate FirstOccurrenceStartDateTime and LastOccurrenceEndDateTime fields on the Reservation table - job that ran. I don't remember seeing that job before the update to 1.5.2.
It changed the statuses on over 750 reservations, but I'm having a hard time determining if it was only reservations that were approved already. It doesn't look like it touched any that had been denied. I'm trying to figure out a way to get all of them back in to the correct status.
This issue is now resolved and will be rolled into the next update.
@marcierempel ++ for nailing where the source of the problem was.
@tcavaletto Do you know if it only changed the status of approved reservations back to pending review or did it change all reservations despite their current status? we're trying to figure out a way to get everyone of them back to what their status was before the job ran.
Prerequisites
Description
A clear and concise description of what the bug is, include screenshots if applicable.
Steps to Reproduce
Expected behavior:
A clear and concise description of what you expected to happen.
Actual behavior:
A description of what actually happened.
Versions