Forum Replies Created
-
Posts
-
By the way, this is sorta urgent as my client uses this to get a list of people who have purchased tickets for an event — and to send out emails if necessary beforehand.
Also, I get the same error if I use the “Attendees” link in the Event edit screen — way down at the bottom in the Tickets metabox. (The “Event Sales Report” link right next to it still throws a permissions error, though I’m logged in as admin. I mentioned this one before and you apparently weren’t able to replicate.) But the Attendees is a much bigger issue right now for us.
So I just increased my PHP memory by just adding
define( 'WP_MAX_MEMORY_LIMIT', '512M' );in my wp-config.php file (as I understand it this adds memory just for admin activities. Still getting the error, now showing the increased memory.
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32 bytes) in /home/oasisorc/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence.php on line 124And then again at 1024M
Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 32 bytes) in /home/oasisorc/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence.php on line 124How much memory do we need here? What’s up? I feel like there is some other issue at play here.
I’m seeing this error as well — using a custom theme, not Avada. Dermot, what do you mean when you say you updated your hosting?
Does anyone know exactly what’s causing this? This is what I’m getting when I try to update a recurring event. It looks like some of the events now reflect the change I was trying to make, but not all of them.
This seems a fairly significant issue. Tribe, do you guys have any more info on this?
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /home/oasisorc/public_html/wp-content/plugins/events-calendar-pro/src/Tribe/Recurrence.php on line 91
Yes, appreciate your comment here. I wouldn’t underestimate the time and effort that are required for thorough documentation of a plugin of this complexity (not just initially, but also in keeping it up to date).
I’m happy to hear you’re looking at this.
Another thought on the docs would be better organization of functions and hooks — not just alphabetically, but topically. And not mixing deprecated functions (there are a lot of those!) with those you want people to use.
Good luck, and thanks for a great plugin.
Well, man. I spent a good deal of time with this and just could not figure out how prevent ‘tribe_get_events’ from stomping on any ‘orderby’ parameter I tried to pass in — overriding it with ‘event_start_date’. Hooking into ‘pre_get_posts’ works, but that effects all queries. I just wanted one custom loop that did something a little different.
I also tried to solve this problem just using a straight WP_Query on the ‘tribe_events’ post type. But I couldn’t figure out how not to get all recurrences of an event. (I just wanted the master event.)
So I punted and decided the solution was to just manipulate the array of posts after the ‘tribe_get_events()’ query comes back.
So I use ‘tribe_get_events’ for a custom query, grabbing all items from a specific category — but just the master event, not recurrences — ‘tribeHideRecurrence => 1’ seems to accomplish the latter.
This gives you an array of post objects, on which you can then use the PHP functions ‘usort()’ and ‘strcmp()’ to shuffle them into alpha order by the post_title property. Then we move on to the loop to echo stuff out.
Not as elegant as just getting the right query, but it seems to be working.
<?php $args = array( 'post_type' => 'tribe_events', // this is the default with tribe_get_events so actually not necessary if that's where you are passing these args 'tribe_events_cat' => 'my-special-event-category', //grabbing posts from the events category I want 'posts_per_page' => -1, // gets all such posts 'tribeHideRecurrence' => 1, // prevents showing all copies of recurring events, just gets the master. I don't actually know why this works, but it seems to. ); $custom_events = tribe_get_events( $args ); $custom_events = my_events_sort( $custom_events ); function my_events_sort( $my_array ) { // this function can go in your functions.php file instead of here in the template file function my_title_sort( $a, $b ) { return strcmp( $a->post_title, $b->post_title ); } usort( $my_array, 'my_title_sort' ); return $my_array; } foreach( $custom_events as $event ) { setup_postdata( $event ); ?> // echo out stuff ...Thanks, Josh. This works for normal lists — that is it operates on the main query. I was running a secondary loop for some events, so this doesn’t quite do what I need. I’m going to keep looking into this.
Sounds great. Thanks. Any idea on timing?
Also, I’m going to assume (hope?) the data I had entered for this field prior to 3.12 is still in my db somewhere. Haven’t gone poking around yet to see.
