Forum Replies Created
-
AuthorPosts
-
papertower
ParticipantI believe we are running into the same issue here. Any updates on this bug?
January 5, 2017 at 3:37 pm in reply to: Please consider making select2 selector more specific #1214078papertower
ParticipantThanks, George! I made a workaround for now. Look forward to the change!
March 17, 2016 at 9:03 pm in reply to: Please fix post_per_page assertion for recurring queries #1090771papertower
ParticipantAwesome! Is it possible to have this ticket updated when a commit made it into a scheduled release?
Right now I’m having to use a workaround via the tribe_event_pre_get_posts filter, and I’d really like to remove it when it’s no longer necessary.
Thanks!
-
This reply was modified 10 years, 1 month ago by
papertower.
papertower
ParticipantThis reply is private.
papertower
ParticipantGreetings!
I just changed to the Twenty-thirteen theme and disabled all the plugins except Events Calendar (and pro). I’m afraid the problem persists. Interestingly enough, when I look in the database, the start date meta is correct. Where does Events Calendar initially add the properties to the queried object?
papertower
ParticipantHi George!
If I var_dump the contents of $event->EventStartDate the value is “{{UNKNOWN}}”
So what I’m doing here is taking the global $event object and using var_dump to view its contents. This is at the beginning of the single template. Within that object is the EventStartDate property, as well as the EventEndDate property. The EventEndDate has the value I’d expect, but for some reason the value of the EventStartDate property is a string value of “{{UNKNOWN}}”. Honestly, I’ve never seen that before.
I’ll try debugging the theme/plugins and let you know what I find.
papertower
ParticipantGot it. I see what that does in tribe-event-query-class.php. Thanks!
I’m having an issue now wherein, in the events, I only want the first event for recurring events.
-
This reply was modified 10 years, 1 month ago by
-
AuthorPosts
