[smallmammothdesign]

This worked perfectly, thanks!

[smallmammothdesign]

Hi Rob,

Thanks for the response. The second plugin I mention is newer:
http://wordpress.org/plugins/wp-ie-enhancer-and-modernizer/

And there’s also http://wordpress.org/plugins/selectivizr/ which to be honest I haven’t tested but as it works the same way I assume it’ll also cause problems.

I’ve ended up ditching the plugins and finding other solutions so this isn’t an immediate concern for me — however these plugins are very handy for fixing a lot of IE7 bugs, and the conflict is a weird one, so someone else might come across this one day as well!

[smallmammothdesign]

Code stripped!

2) Should read:

In single-event.php, I took the three lines after – Event meta – and moved them up above the section – Event content -.

[smallmammothdesign]

Hi,

Saw this by chance and I might be able to help you out here, because I recently did the same thing on my site (I assume you’re using the latest 3.0 versions of everything).

1) I made the override tribe-events folder in my theme folder, and placed single-event.php in it (can be found in The Events Calendar > Views).

2) In single-event.php, I took the three lines after and moved them up above the section).

3) I then changed the middle line from:
echo tribe_events_single_event_meta()
to:
echo tribe_get_meta( ‘tribe_eb_event’ )

This removes the other two meta boxes and replaces them with just the tickets box, so if you want the other boxes as well you’ll have to call them separately — and I don’t know how you’d go about positioning them below the rest of the content (they need to go between tribe_events_single_event_before_the_meta and tribe_events_single_event_after_the_meta, and I don’t know if you can call the meta section twice).

4) What this doesn’t remove is the related events section, which is somehow linked to tribe_events_single_event_after_the_meta, so I chose to get rid of it entirely. In my theme’s functions.php file, I added the line:
remove_action( ‘tribe_events_single_event_after_the_meta’, ‘tribe_single_related_events’ );
(somewhere before the closing ?>)

I’ll be curious to see if the pros have a better way, but since they’ve been a bit slow answering these days I thought I’d share my solution in the meantime. If you want to keep the other meta boxes and the related events, this might not be the way for you… but hopefully it will put you on the right track. Searching here for other tags you want to call could also help: http://docs.tri.be/ — for example, before my revised meta section, I added in custom tags to display some basic info in before the tickets box:
the_title();
echo tribe_get_city();
echo tribe_get_region();
echo tribe_events_event_schedule_details();
etc. (each line between the php open and closing tags)

[smallmammothdesign]

I should also note that not all of my events are in the same time zone, so if the time zone can somehow be set using the general WordPress settings, that won’t do the trick for me. There should either be a set timezone option on each event page, as there is in Eventbrite, or the timezone should be set according to the address.

[smallmammothdesign]

Hi,
I’m using the 3.0 version, and am still experiencing this issue — events created in Eventbrite with an EDT time zone were all updated to Mountain time after I imported them into WordPress.

Any chance for a fix on this?

[smallmammothdesign]

All set! Thanks.

[smallmammothdesign]

That did the trick! Thank you very much!

[smallmammothdesign]

Thanks for following up on this. In my case, overriding single-events is not enough, because I want the change to appear on all pages and templates. And when I tried simply using tribe_events_event_schedule_details, it did not override the existing filter.

For anyone else trying to do this, here’s what I ended up doing in detail:
I copied tribe_events_event_schedule_details, including all the subsequent bits that define the date format into my theme’s functions.php. I then renamed it tribe_events_event_schedule_details-2, and adjusted the variables to my liking.

I then had to change tribe_events_event_schedule_details to tribe_events_event_schedule_details-2 in all the templates I used (first placing the templates in the tribe-events override folder in my theme folder). Tracking them all down is a bit of a nuisance, but it worked.

Options for setting the date format might be a nice feature to include in a future update — not everyone wants things like ‘@’ before the time.

[smallmammothdesign]

Thank you, that seems to be it!
Or at least — it got rid of the events details metadata. However, something is still calling the “Related events”. Is this maybe linked to tribe_events_single_event_after_the_meta ?
Is there a way to call only the tickets?

[smallmammothdesign]

I appreciate that bugs take precedence.
That said, I have a deadline, and hope I won’t have to wait more than a week for an answer!
Thanks.

[smallmammothdesign]

Shoot, apparently leaving spaces doesn’t work either.
One more try:

tribe_get_meta ( ‘what_goes_here’ )

[smallmammothdesign]

Oops sorry forgot it strips my code. I need the “what goes here” bit.
i.e.:

[smallmammothdesign]

Hi Neil,
Thank you for your answer. I’ll start a new thread if it turns out to be necessary, but I think you misunderstood my question, because the solution you have offered Genesis is exactly the solution I am looking for.

I’ve already modified general.php as you are suggesting Genesis do (what exactly I have changed is not pertinent — as I said before, I’ve already worked that out).

However, and Genesis should know this too, if s/he later updates the plugin, the change to general.php you are recommending will be lost, because general.php is not an over-ridable file, right?

So, to avoid losing the changes on update, I would like to use the second approach you are suggesting to Genesis: “play with the format of the filter itself via $tag, ‘tribe_events_event_schedule_details’, and rebuild the output, any way you wish.”

Could you be a bit more specific on how to do this? NOT on how to rebuild the output. Again, I’ve done that aLready. My questions are:
— What goes in place of $tag?
— What code goes before/around $tag, ‘tribe_events_event_schedule_details’?
— before playing with $tag, ‘tribe_events_event_schedule_details’ as you are suggesting, don’t I have to deregister the original function or filter or whatever it is?

Thanks for your help.

[smallmammothdesign]

Hi,
I have the same question, only the modifications I’d like to make are more extensive (e.g., having the date output in this order, without the @ symbol: 8AM – 9:30AM, JULY 17, 2013). I would like this change to appear throughout all the Events Calendar pages.

I have already made these changes to the general.php file found in Public > Template Tags, so I’m fine on that count.

However, rather than making them directly to the general.php file, I’d rather deregister the tribe_events_event_schedule_details function in my theme functions, and reregister the new version I’ve made, so the change isn’t lost upon update.

From what I’ve read, this involves adding this line of code to my theme’s functions.php:
remove_action( $tag, ‘tribe_events_event_schedule_details’, $priority, );

However, I can’t identify the $tag hook and the priority. Could you please tell me what they should be?

And then, to re-register the new function using the same name (tribe_events_event_schedule_details), can I just paste the (modified with my changes) function in as is? I’d rather not rename it, to avoid having to update the call in all the templates that use it.

[Author]

Posts