[Michael]

Events Calendar Pro: you can choose the version under Account Central > Downloads

The Events Calendar: http://wordpress.org/plugins/the-events-calendar/developers/ “Other Versions”

[Michael]

Additional info:

The list in the admin section (Events > Tags) shows 3 Events tagged ‘test’, but it’s actually 1 event and 2 regular posts.

[Michael]

Excellent, thanks.

Are you planning to list the IDs of the available meta keys in the docs? That would be a big help.

[Michael]

Yes, nrv_featured_item is the meta_key that allows items (Posts, Pages and Events) to be queried and thus featured on the homepage.

Yes, that’s the problem, and if I turn it off, I don’t have a database error.

As I stated a week ago, this worked fine before the upgrade to 3.1, and it does work fine when I exclude tribe_events from the query.

The nrv_featured_item key/value pair shows in the Custom Fields box for the events in question, everything looks normal there, no PHP notices or warnings.

Is there something you’ve changed in 3.1 with regards to how custom field keys/values are stored for the tribe_events post type? Would you like me to post up the code for the metaboxes and/or the WP_Query somewhere?

I am using the WPAlchemy WordPress MetaBox PHP Class:
https://github.com/farinspace/wpalchemy

[Michael]

Take your time…

[Michael]

This reply is private.

[Michael]

phpMyAdmin tells me there is one postmeta table, and the right meta key/value pairs are there. Nothing looks weird in the WordPress admin area, either: custom fields show as expected.

Again: when I exclude tribe_events from the query, it works fine.

[Michael]

That’s great, thank you very much.

All solved – as far as I can see, I don’t need any of the scripts – I’m running a very simple, short list of events on that site. But thanks for going into the dependencies as well, might come in handy at some point.

[Michael]

Hi Kyle,

Great news about extending the docs with examples etc. – sounds like the right idea and the right place to do it. I know how difficult it is to put documentation together – how much is enough, can’t take all use cases into account, etc.

Back to the original question, though:

Using the method above, I managed to unhook:
tribe-events-pro-geoloc
tribe-events-pro
tribe-events-bar

No luck with the following scripts:
bootstrap-datepicker.js
jquery.ba-resize.min.js
jquery.placeholder.min.js
tribe-events-ajax-list.min.js
tribe-events.min.js

I’m sticking to the naming convention of prefix & -handle, and I’ve found references to these scripts in the plugin code, but that doesn’t seem to work in all cases. Can you point me in the right direction?

Thanks,
Michael

[Michael]

Thanks, guys. Good to hear you’re working on consolidating the scripts.

It looks like I used the right hook, also tried different priorities, but didn’t see the right handles: for instance, the handles for the css files have a -css appended somewhere in the process, so the actual handle is not the same as the id that can be seen in the source code.

I successfully removed all the styles, and the script in your example is also gone. Thanks for that – I’ll probably be able to find and/or deduct the rest.

On a general note: I was hoping to see a bit more transparency and easier ways to modify output with version 3.

By transparency, I mean documentation: It’s a bit tedious to track down pastebin snippets in the forum. Your new docs section is a great step, more of that would be very welcome – eg code examples or links to guides and tutorials.

With regards to templating, I’m sure there are good reasons why many things can’t just be modified in a template file – eg changing the order of event details in the single view or adding a class to the View All link on the widget, stuff like that. But I think that makes extensive documentation even more important – I’m happy to dig deeply through a plugin in oder to make it fit my needs, but waiting for an answer to a support question for 5 days is frustrating.

Thanks,
Michael

[Michael]

Alright, thanks.

[Michael]

Geddit. I wasn’t familiar with output buffers, but I eventually got the syntax right.

[Michael]

Thanks, but the code in the snippet only checks for the existence of a previous event, so on the last event, it displays:
PREVIOUS |

As stated above, how do I check if there’s a previous AND a next event?
(I’ve been through the Themer’s Guide. I also searched the forums before posting.)

On a related note, the prev/next navigation seems to choke on recurring events: if there’s another event between the first and second occurence of a recurring event, it jumps back to the first occurence, instead of the second. Is this a known issue?

Thanks

[Michael]

Oh – and I forgot: similarly, is there a way to exclude events that have passed, ie to only display a previous event link if the previous event is an upcoming event?

[Michael]

Okay, I can try that if it comes down to it, thanks.

[Author]

Posts