Doesn’t seem to work fully

Are you using Ticket cut-off or Event cut-off? In my test the bookings are indeed closed if the status is set to “Cancelled”.

Hi Jurgen,

I was able to reproduce the issue. I also noticed that the status labels had disappeared. This all should be solved in version 1.3.0.

Please update the plugin when prompted by WordPress.

Hi Patrick,

is there any news on 1.3.0 yet? I would really love to use this plugin ??

Regards,
Jurgen

I use version 1.3. The only effect is that the events have the status “Cancelled”. But they are still visible in the calender and still available for booking. I expected this plugin to make them unavailable for booking, and preferably (optionally) hide them.

Hi Jurgen,

It works like it should in my tests… [redacted]

Cancelled events are not hidden automatically, because some users might want to let users know an event has been cancelled and not just “disappeared from the website”. (As do I myself.)

If you are using the [events_list] shortcode, you can automatically hide cancelled events by excluding the category ID.
[events_list category="-X"]

The thing is, this plugin adds the cancelled category to your existing event categories, so from this side I have no clue which Event ID is assigned in your system. ??

• This reply was modified 4 years, 10 months ago by Steven Stern (sterndata).
• This reply was modified 4 years, 10 months ago by Steven Stern (sterndata).

@duisterdenhaag I’ve deleted your offer to login to your user’s site. While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

@sterndata Actually, this specific user is my customer, because he is also using one of my premium plugins. That’s why he already has my contact info.

@argosmedia, I am sorry, but Forum Rules are limiting my well-intended support, as always.

No worries guys. Sterndata, I value your work as a moderator. Stonehenge, I appreciate your work and support as well, you bring great value to the EM community.

Yes, I am a paying customer for another (premium) Stonehenge plugin, but this one is free, so that’s why I posted here instead of contacting Patrick directly.

Anyway, I realized tonight that my client can just disable events temporarily, by setting their status to Draft or Pending. That way they are hidden from the frontend completely, and that was what I was after. My client doesn’t need to cancel events that already have bookings and sent out emails automatically. So actually this cancellation plugin is not needed for that. Sorry about the needless topic. My problem is solved.