[Marty]

Speaking of, I’ve noticed tribe_get_listview_link() has a very similar problem. It returns:

/events/category/mycategory/list/

Which is resulting in the “There are no upcoming events in this category” message. It seems like what we’d really want to return here would be:

/events/category/mycategory/?action=tribe_list

As with tribe_get_past_link(), it appears to be including “list/” where it should not be.

[Marty]

Okay, thank you.

[Marty]

Okay, I’ll investigate some more. Thanks for your help!

[Marty]

Thanks

[Marty]

Hi these did the trick, thanks!

I do expect there’ll be more scripts I’ll want to dequeue — I’ve only been looking at the List and Single templates so far, and Grid’s still on my list. I’ll follow your advise and search using “getMinFile.”

That said a comprehensive list in the docs would certainly be helpful.

[Marty]

Cheers

[Marty]

PS. Looking at the List view, there’s a few more I’d like to dequeue:

/the-events-calendar/vendor/jquery-placeholder/jquery.placeholder.min.js
/the-events-calendar/vendor/bootstrap-datepicker/js/bootstrap-datepicker.js
/the-events-calendar/resources/tribe-events-bar.min.js
/events-calendar-pro/resources/tribe-events-ajax-maps.min.js
/the-events-calendar/resources/tribe-events-ajax-list.min.js

Thanks!

[Marty]

Hi, yes, that param did the trick, thanks.

It’d be great if those params were documented somwhere, though — less time wasted by everyone!

[Marty]

Thanks for your response. Can you help me get a bit further?

As-is, the tribe_get_past_link() and tribe_get_upcoming_link() functions aren’t doing the full job of providing back/next links, since they don’t include the “?action=tribe_list&tribe_paged=3” string.

In order to write alternatives to those functions, where would I get the variable to use with “paged=”?

Thanks!

[Marty]

That does help, thanks Barry!

[Marty]

Is there any information you can give me at all — a tentative schedule for when 3.0 will be entering and coming out of beta?

[Marty]

Hi Barry,

I, too, am very much in need of an alternative recurrence scheme.

My ideal solution would be the ability to add multiple “Event Time and Date” fieldsets to an Event. Like the current, single fieldset, each would include a full set of start/end/date/time, plus recurrance options.

Perhaps you can comment on how closely, or not, that matches what is being discussed internally?

I would be very interested in some sort of a 3.0 roadmap, which sketches out the general contours of what functionality is planned and what the schedule might possibly be. This would be incredibly helpful, as it would be information I could bring to my team.

Marty

[Marty]

Improvements to search would be welcome, such as choosing to search Documentation vs. Forum. The layout of the results page could do a better job of directing emphasis (right now I find the big titles distracting).

I also agree that a better system for seeing solutions other users have posted would be a big help. The forum is a bit of a needle in a haystack and encourages posting a new topic rather than extending an existing one.

[Marty]

At first blush that seems to have done the trick. Thanks! I’ll come back if the issue returns.

[Marty]

Hi. I’ve got the page-based solution working and was moving on… and then I came upon this:
http://snipplr.com/view.php?codeview&id=17432

It creates year based archives for categories. Which is awesome. It doesn’t automagically work for Events, but might it point the way to something that could work?

Anyone out there fluent in wp_rewrite who could offer an opinion?

[Author]

Posts