Display events on homepage
Hey guys, I’ve posted this (basic) question on the wordpress forum, but no answer. Can someone please explain me how to display the events on the homepage (or any other page, then the one assigned under settings?)
Here is my post: http://wordpress.org/support/topic/plugin-the-events-calendar-display-listphp-on-index-page-and-other-pages?replies=1
I don’t want it in a sidebar and no, not via shortcode embed (i thought that wasn’t possible?)
The thing is that I don’t want to use widgets. I like to hard-code 😉
Here the website (developing): http://www.hubbicle.in-town.nl/
It has several loops:
I would like to put an events list in loop-events, so I can also show it on the front page and other pages.
The only thing I got working is http://www.hubbicle.in-town.nl/shows/ thanks to your guide by adding it to a template using the WP CMS.
But how to show the same somewhere else?
$posts = tribe_get_events( ‘numResults=1&eventCat=’);
$template = TribeEventsTemplates::getTemplateHierarchy(‘widget-featured-display’);
I tried copying my list.php template into loop-php.
Tried custom post types:
‘events’, ‘posts_per_page’ => 10, ‘orderby’ => ‘date’, ‘order’ => ‘ASC’, ‘paged’ ) ); ?>
Hi Tineke, your “Upcoming Posts” code is incorrect – you have the orderby=date which will show events by the date you created the posts….I think most people would want to show upcoming events with the event happening the soonest to be the first in the list….and so on…
So, for anyone hoping to find that in this thread, instead of orderby=date in the query , do eventDisplay=upcoming
Hi Rob, not sure if it’s been mentioned somewhere in the forum yet, but may be a bug….
When displaying upcoming events via template code, it shows the upcoming events correctly…..until you create a recurring event…..then it messes up the display order the upcoming events.
Screen shot here: http://yfrog.com/h7zzdmp
Can John chime in and see if he can confirm the bug please? Hopefully get it fixed in the next version update
Hey Brian. This does look like a legitimate bug; I’ve sent it John’s way to confirm and if so we’ll get it patched for 2.0.2. FYI John is out the rest of the week but once he’s back hopefully we’ll be able to provide a suggestion for the shorter term as we work to fix this for 2.0.2. Sorry about the inconvenience.