Reply to: tickets(364226)

Hi Artem,

Thanks, saving that did work for me.

For some reasons the icons are not loading for me, but either way, I cannot edit the designer. I can’t remove any rows for example. No console errors are occuring when I click remove.

Thanks,

Reply to: tickets(363891)

Hello, I found an other solution that I will try: This is what the note in the PHP file says:

You can preview this email by visiting …/wp-admin/post.php?post={X}&action=edit&debug=true&type=notification_email — replace X with rsvp post ID

Jeroen

Reply to: tickets(364205)

It turns out the two who RSVP’d but didn’t get reminders had been scheduled before the date changed. We had called them on the phone to notify them of the date change, but I would have expected the reminders to have gone out yesterday when the host got the reminder (even though it was incorrect and we didn’t want them to go out yesterday).

FWIW, here’s a loom I made for my internal team explaining the situation with the cron. You can see that the reminders showed as already sent prior to my saving the event a second time, and that updated the cron.

https://www.loom.com/share/8d0cd7c7647e4f59b3779c0b5583a72d?sid=d4cc9a8f-472b-49db-83ac-101b97d7e47b

So now, my question is, will those reminders be sent to the two current RSVPs as well as the people who have yet to sign up on 10/1 and 10/7?

I’m also attaching a screenshot from our SMPT history showing that only 1 reminder was sent (to the host) and not to anyone else.

Reply to: tickets(364200)

Here are the credentials

 

https://scrt.link/l#TcsqlyhE75JeBQfnwkXG0/hbtiQpfKZFJ5p2yJc0i2EC86F-TgA7u8Io0U8Lr4WLk

 

I had to remove the button short code from each of the pages because it was popping up blank so I created a test page so you could see what is happening. Everything worked fine before updating the ticket plugin last night. I have cleared the cache, dumped the server cache, tried an incognito window and multiple browsers.

Reply to: tickets(364205)

That’s great. Thanks for that clarification.

This came up because a reminder went out to the host of a particular event, but not to the couple of people who had RSVP’d.

In this case, the reminder to the host shouldn’t have gone out at all because the event had been rescheduled from one date, to another date next month but the person who changed it didn’t know they had to save the change twice to update the cron job for the reminders.

I’m GUESSING what happened is that the event was rescheduled (without the double save) and then the two people RSVP’d after the event was rescheduled, but I’m trying to understand what happened, and most importantly, I want to make sure they will get the correct reminders a month from now and that the other 20 or so people who have yet to RSVP will get the correct reminders going forward.

I have now updated the cron by resaving and refreshing the event.