Unhook woo commerce and only use RSVP

[desical]

Hi,
How do we unhook woo commerce in Event calendar PRO and only use RSVP feature, we do not want to implement woo commerce at this time. We want hide the choice on community/add. Instead add a add a custom field URL and allow sub site administrators add their own Paypal or any other Payment url when creating events.

In future we may use woo commerce

Thanks

[Geoff B.]

Good evening Avinash and welcome back!

Thank you for reaching out to us.

I would love to help you with this topic.

The good news is that it’s possible to do these 2 things.
However, bypassing WooCommerce also means that there will be nothing truly transactional going on directly on the site.

For actual purchases to be made (with payment info, etc..) you will have to handle that completely outside of our plugins.

The best way to achieve this is through a template customization. You might want to read our Themer’s guide to get a sense of how that works.
Also, I recommend reading my colleague Brook’s take on removing….. the RSVP option: https://theeventscalendar.com/support/forums/topic/possible-to-remove-rsvp-as-a-ticket-option/#post-1102859

This should get you started on the right track.

You might also give the following snippet a try: https://theeventscalendar.com/support/forums/topic/hiderestrict-access-to-a-ticket-type/#post-63122

As for adding an additional field, you can simply read the following: https://theeventscalendar.com/knowledgebase/pro-additional-fields/

Let me know if that helps.

Have a great day!

Geoff B.

[desical]

Hi Geoff,
First off I appreciate your quick reply, you all truly provide quick support, which is huge for us. Solutions you have provided will certainly help us get started.
The link:

Possible to remove RSVP as a ticket option?

We want to only use RSVP feature and hide woo commerce as choice. So assuming we make necessary changes to the code in the link which would only show RSVP, is my understanding correct?

Creating Additional Fields

it looks like we should be able to add URL for payment within the event as desired. We will test it out.

I forgot add one more question yesterday, I am curious to know, is it possible to hide page to avoid creating event on master domain but only allow event creation on subsites? We are syncing events (using ical) from subsites to master domain and want avoid creating events on master domain?

Thank you once again.
Avinash

[Geoff B.]

Good evening Avinash,

Thank you for writing back and for your great words.

The link:
https://theeventscalendar.com/support/forums/topic/possible-to-remove-rsvp-as-a-ticket-option/#post-1102859
We want to only use RSVP feature and hide woo commerce as choice. So assuming we make necessary changes to the code in the link which would only show RSVP, is my understanding correct?

Your understanding is spot on. Adapting this snippet will work.

https://theeventscalendar.com/knowledgebase/pro-additional-fields/
it looks like we should be able to add URL for payment within the event as desired. We will test it out.

Awesome, let me know how that goes.

I forgot add one more question yesterday, I am curious to know, is it possible to hide page to avoid creating event on master domain but only allow event creation on subsites? We are syncing events (using ical) from subsites to master domain and want avoid creating events on master domain?

That is a great question. The short answer is yes.

I am not clear if you want to hide the front-end page only or if you want to hide the ability to add events in the backend as well. Could you clarify that part for me ?

In any case, there are several solutions available:

1. For front-end, the link to the page is only visible if you actually input that link somewhere. If you want to be extra sure, you could change the “add” slug to something really different (e.g.: 133442455)
2. For the backend, you can remove any menu in the dashboard with a few line of codes in the functions.php of your WordPress theme (https://codex.wordpress.org/Function_Reference/remove_menu_page)
3. If you want to push things further you could literally block certain options (even with direct URL entry). Most users do that in combination with a WordPress role

Let me know if that helps.

Have a great day!

Geoff B.

[desical]

This reply is private.

[desical]

So I got your point to add a wired slug to the community submission form. I am just curious if that would affect the sync from ical, as I mentioned we are syncing events from subsites to the main site. Is it fine if the URL structure is different on subsite and main site?

On a larger take, I don’t think we need to disable the event submission from the backend. Since the backend/dashboard can be restricted according to the user role. I just want to make sure if some user goes nuts and try’s some URLs combinations to find the community event submission page on the main domain he should not be able to do so.

[Geoff B.]

Good evening Avinash,

Thank you for writing back.

I would like to run this by some team members tomorrow so that I can provide you with the best answer possible.

Thank you for your patience..

Best regards,

Geoff B.

[desical]

This reply is private.

[Geoff B.]

This reply is private.

[Geoff B.]

Good evening Avinash,

I asked the person responsible for the first snippet on advice on how to convert his snippet for your purpose.

Here is his answer:

My snippet would likely we do that by changing ‘WooCommerce’ to ‘RSVP’ per the last line of my comment in there.

So:
if ( $module !== 'RSVP' ) continue;

But you are right, the structure of the snippet needs to be changed since the structure of that file has (with the addition of foreach). I have tested it out and it needs some further tweaking. I’ll ask for an update on this one.

I am just curious if that would affect the sync from ical, as I mentioned we are syncing events from subsites to the main site. Is it fine if the URL structure is different on subsite and main site?

There should be no impact with iCal on the main site.

If you want to add an extra layer of security, you could always add a redirection for that wired community add URL in your .htaccess file.

Best regards,

Geoff B.

 

[desical]

This reply is private.

[Geoff B.]

Good afternoon Avinash,

Thank you for your patience.

I am still working on getting this updated with the author of the snippet, but in all likelihood this will probably go to the beginning of next week.

I will make sure I paste the complete file when it becomes available.

Have a good week-end,

Geoff B.

 

[desical]

Hi Geoff,
Do you have any ETA on this? I appreciate your help and support.

Thank you

[Geoff B.]

Good evening Avinash,

The long wait is finally over.
Here is a snippet that works: https://gist.github.com/GeoffEW/adfeedbc908640ba7bbf584e6622b406

As per my colleague Brook’s instructions, this still needs to go in: [your-theme]/tribe-events/community-tickets/modules/tickets.php

Let me know how that goes and thank you for sticking with us.

Best regards,
Geoff B.

[desical]

Hey Geoff,

I have created the file according to te path you suggested, with the files name you suggested. i.e., [my-child-theme]/tribe-events/community-tickets/modules/tickets.php

But it does not seem to work. Is it because I am using this theme https://themeforest.net/item/ivent-multipurpose-event-wordpress-theme/13859489 wich does not seem to have the tickets.php files in the parent theme at [theme-name]/tribe-events/community-tickets/modules/tickets.php

After I added this, I am now not getting the tickets option in the dashboard.

[Author]

Posts