[George]

If you modify core code of a plugin or theme, every time you update it it any changes to core code will be overwritten. There is not anything we can do to alter this truth, but the code fix I shared is a temporary way to fix a problem you described as very negative.

If you don’t want that fix, then the best option is to wait for an official plugin update that does this.

---

In regards to dequeueing scripts, I do not know where on your site you want things dequeued, and where you will then selectively be re-enqueueing them (if at all).

But you’re right that simply dequeueing a script is easy, so you should have no problem dequeuing any script or stylehseet you would like.

To find scripts and styles you want to dequeue, simply open the plugin code for The Events Calendar or Events Calendar Pro in your code editor of choice, and use its “Find in Folder” feature to look for all instances of wp_enqueue_script() and wp_enqueue_style().

If you find an instance and it is a script or stylesheet you want to dequeue, then make a simple little one-liner like you described above and you’re good to go! 😀

Cheers and best of luck with your modifications,
George

[George]

I’m sorry to hear this, @Benjamin!

I cannot recreate any of this behavior and so, to be honest, I’m a bit stumped with what might be causing all of this.

I will raise this issue with some of our developers and see if that inspires any further steps I could recommend.

Thank you,
George

[George]

Hey Teresa,

Thanks for reaching out!

There is unfortunately no out-of-the-box custom integration with Google Analytics, but there is a litany of Analytics-specific plugins out there that will add Analytics to your site just fine, and which should let you track specific pieces of content (like events). The Events Calendar should work fine with any well-coded plugin like this.

I hope this information helps!
George

[George]

Hey Geoff,

Thanks for your follow-up. Adding more complicated information like the course name and all of that is unfortunately a bit too far outside the scope of support that we can provide. Please read more about this here.

As a word of advice to hopefully help point you in the right direction, at least, notice how $order_id is available to that tribe_notify_admin_about_rsvp() function I wrote for you? In that function, where the wp_mail() function is called which sends the email, you can get clever and use that $order_id to back-engineer the data to get basically any information you want.

It’s complicated, unfortunately, and will take much tinkering. But if you play around with Post Meta and use debugging tools like var_dump() along the way, you should hopefully be able to put something together. I would recommend reading these Codex articles as well:

• https://developer.wordpress.org/reference/functions/wp_mail/
• https://developer.wordpress.org/reference/functions/get_post_meta/

If you need more assistance customizing the emails, then the best course of action is to hire a developer to assist you. We have a list of great developers here, in case it’s helpful → http://m.tri.be/18k1 (and we have no affiliation with any of these folks–they’re simply some well-respected names in the community that we’ve compiled).

As noted, I will make a ticket for this feature to eventually arrive in the plugins officially, too. So hopefully at some point the plugin will provide all of these details automatically. I’m sorry that it doesn’t currently!

Sincerely,
George

[George]

Hi @stratejusinc,

I am sorry to see that this script is loading in the header. It’s unique in that way—all other scripts of ours load in the footer. I am not sure why this is happening, but will make a development ticket so that this can be patched in a future release.

In the meantime, a temporary fix would be to just make that line of code that says wp_enqueue_script() look like this instead of what it currently looks like:


wp_enqueue_script( 'tribe-this-week', tribe_events_pro_resource_url( 'widget-this-week.min.js' ), array( 'jquery' ), apply_filters( 'tribe_events_pro_js_version', Tribe__Events__Pro__Main::VERSION ), true );


---

We do indeed limit asset loading to events pages. As an actively-updated plugin with many moving parts and a development team of many folks contributing code, things slip through and there are occasionally assets loading in places where they’re not needed.

We are constantly working on this and agree that an option or flag to have a bit more control over asset loading is a great feature to have. It is not “easy” or simple though, unfortunately, and so I cannot specify an ETA for the arrival of any such feature unfortunately.

In the meantime, I cannot provide you the extensive custom coding you demand. We are a support team for a general product of which you are one of many customers; not a consultant you have singularly hired to build something specific to your spec and project needs, available for demands for work on your time-table and whim.

⚠️ Please review what license support includes here: https://theeventscalendar.com/knowledgebase/what-support-is-provided-for-license-holders/

I am sorry to disappoint you about the nature of things. To review, however, we agree with you on many points and are actively working on refining the asset loading of our plugins. Here is a recap of the key details from this thread:

• I have shared a temporary fix for the script that is causing jQuery to load in the header.
• I have confirmed that this loading-in-the-header behavior is not correct behavior, and that I will make a bug ticket for us to fix this in our plugins in an upcoming release.
• I have confirmed that we are continuously working on loading assets only where appropriate, and that assets for events should only be loaded on events pages.
• I have confirmed that as future plugin releases are published, this behavior will be improved and refined over time.

Thank you,
George

[George]

Hey Benjamin,

Just to be clear, in your screenshots the datepickers show 1970—but are you able to set these to proper 2016 dates and then save the event, and have the date properly updated? Or even if you do this, upon save does the date get reset to 1970?

Thank you!
George

[George]

Hey Soula,

In addition to the three pointed questions I posed above, can you clarify what some of the key differences are in the “event setup” between the two events you shared?

Thanks!
George

[George]

Hey @Bouchair,

1. tribe_is_recurring_event()
2. This is not easily possible, but is best done with tribe_get_events(). You can learn more about how to use that function here ? https://theeventscalendar.com/knowledgebase/using-tribe_get_events/
3. tribe_get_start_date() and tribe_get_end_date()

Need to learn more about these functions? The best way to do so is to open up your code editor and look for where the functions are defined. You can use your code editor’s “search” and “find in folder” features to do this.

While I cannot answer further questions about custom coding, how to use functions, etc., if there is anything else I can try to help with here let me know. If not I will close up the thread! 😀

Thanks,
George

[George]

Thanks Martin. If you place the following CSS into the bottom of your theme’s style.css file, you should be able to hide the sidebar and make the calendar view full-width:


body.post-type-archive-tribe_events #content .main {
width: 100% !important;
}
body.post-type-archive-tribe_events #content .kad-sidebar {
display: none !important;
}

For any other refienments/tweaks/design customizations, you will have to take the reins, but I hope this helps!

If you need to write more custom CSS on your site, definitely check out a [free!] tool like Firebug if you use FireFox, or the Developer Tools for either Safari or Chrome. They have “Inspector” tools that let you zoom right over the element whose styles you want to change, which is immensely helpful. I used this tool to come up with the CSS I shared with you above. 😉

Cheers,
George

[George]

Thanks for sharing this!

I see that on http://millvalleymasons.org, you’re using a custom theme called millvalleymasons. If you activate a default theme like Twenty Sixteen or Twenty Twelve, for example, and try to recreate the same exact problems you currently have, do you get any different behavior?

Thank you!
George

[George]

Hey Richard,

Thanks for clarifying things a bit! This is unfortunately not possible out-of-the-box with any of our plugins:

I want to limit it to one ticket per buyer per event rather than just one ticket per event.

In regards to helping with custom code, I’m definitely happy to try and at least point you in the right direction here!

To that end, you go on in your reply to establish this as a goal of yours:

I want to make sure that once they have requested a ticket for a given event, they can’t request another.

It sounds like some sort of limitation could be put in place here in a bit of a roundabout way. What I mean is, instead of a “true” solution where the code looks for membership status and limits the actual “selectability” of quantity of tickets, you could do something like this instead:

• Make it so that only one ticket is ever selectable regardless.
• For any logged-out users, hide the ticket purchase form.
• For any logged-in users, when viewing an event, check to see if they already have a ticket to the event. If so, hide the ticket purchase form; if not, then leave the ticket purchase form open for use to them.

Each thing here is a non-trivial customization to make, so not to belabor a point you already know, but you will have to take the reins on most of the implementation here. As an example/clever workaround for pulling off the first part alone, for example—which is one of the simplest components of this!—you could add the code in the following Gist to your theme’s functions.php file ? https://git.io/vrfJE

Now for the second part, which is again a bit simple (relatively). This bit of code will help hide the carts by default for any user who is not logged-in. To do this, add CSS like the following to the bottom of your theme’s style.css file:


.type-tribe_events form.cart {
display: none !important;
}
body.logged-in .type-tribe_events form.cart {
display: none !important;
}


---

Now the Tricky Stuff

I hope the above code I’ve written for you helps! You will have to take the reins from here, and there are two main complications worth highlighting here:

1. Code in themes gets overwritten every time you update your theme. So you will have to re-implement the code after each theme update, or create a child theme, which you can read about there.

2. Wiring up the third component here is the trickiest part, and you will likely need to work with custom coding from both you membership plugin/system and the Event Tickets Plus ticketing functionality. If you don’t feel comfortable making such edits on your own, hiring a developer to assist you might be a great option. We have a list of great developers here → http://m.tri.be/18k1 (and we have no affiliation with any of these folks–they’re simply some well-respected names in the community that we’ve compiled).

---

Best of luck with your customizing and tinkering!
George

[George]

Sounds good @Virgil! Best of luck with your project and the custom development/tinkering.

Sincerely,
George

[George]

Thanks Richard—I see you’ve marked this thread “resolved”, so I will close up this thread for now, but open a new thread any time if other questions, comments, or concerns ever arise.

Cheers,
George

[George]

Best of luck with your project!

George

[George]

Hey @Oniregoc,

Thanks for reaching out! A bit of customization is required here, but this should be possible by adding the following line of code to your theme’s functions.php file:


add_filter( 'tribe_rsvp_email_recipient', '__return_empty_array' );


Let me know if this helps! 😀
George

[Author]

Posts