[masteagall]

Thanks for the response. Please, *yes*, better documentation would be greatly appreciated and immensely useful to all… including to you and your fellow staff it seems (as you just happened to have stumbled upon the answer yourself). To be honest, team members of ours have found the experience of working with your products to be an uphill battle because of this oversight.

Thank you again for the quick reply,

-A

PS: An example of good/useful documentation: http://codex.wordpress.org/Template_Tags/get_posts

[masteagall]

Hi Josh,

Thank you for the response. I must ask though, 1) *where exactly did you find this*? Surely here: http://docs.tri.be/Events-Calendar/index.html – but… where?

And 2) Is it possible to request a complete list of arguments that can be passed to tribe_get_events();? Surely a list must exist someplace. *?*

Frustrated,

Andrew

[masteagall]

.

[masteagall]

Thanks for pointing me in the right direction. I… uh… I guess it didn’t occur to me to look specifically look at line 940, of public static TribeWooTickets’s get_instance( ), under TribeWooTickets entry under classes. :\

I suppose that after working with other documentation ModernTribe has published that’s much better indexed, like what’s found at “http://docs.tri.be/Events-Calendar/”, we were thrown off and/or maybe had false expectations about indexing standards across products. For us, even just getting to see a simple and complete list of what functions are available is a HUGE help, and a monstrously big timesaver as we work through a project with a new plugin, rather than sifting through thousands of lines of code (ie: line 940 in one of many source code files for a seemingly basic function), then figuring out what that code does, and then making a list ourselves. Knowing what’s available up front gives you much better idea of what calls can be made, how swiftly you can accomplish something (if a function already exists for something you’re looking for), and what potential rests beneath the hood. And, going back to your asking, code samples and exemplary snippets would as well be excellent to have too.

Anyway…
Thanks again for your help and super-quick response. I do genuinely appreciate it. If anything else comes up we’ll be sure to give you guys a shout! 🙂

Appreciative,

Andrew

[masteagall]

Hi George,

Hey, thank you for the quick response! This is a huge help, and it works like a champ. I totally appreciate it. However, your response begs one more follow-up question:

In your response I you use the function get_tickets_ids(); to output data. That’s great. However, when I try to search for more information on that function (in your support documentation or even on google) to see what I can find out about other existing functions that may be useful for retrieving ticket data, I don’t find anything. Where can I find more information about that function and any/all other related functions for tickets themselves? Am I just totally missing this list someplace obvious?

I totally understand that you guys have a line that you practically can’t and shouldn’t cross in providing support (ie: no custom solutions), but admittedly I’m finding your documentation a bit tough to follow. And without easy to follow documentation I end up having to ask questions here. :\

Looking forward to hearing back, and thanks again!

Andrew M.

[Author]

Posts