Support

January 7, 2014 at 6:45 pm

Hi David,

Can you post a link to your home page so we can look into this?

January 7, 2014 at 7:42 pm

Hi David,

If you open up the espresso-custom-template’s index.php file there’s a bit of jQuery at the bottom of the file. There is a line that reads:

var ee_filter_cat_id = jQuery("option:selected").attr('class');

that you can try changing to:

var ee_filter_cat_id = jQuery("#ee_filter_cat option:selected").attr('class');

Which should resolve the conflict.

January 7, 2014 at 9:15 pm

Hi David,

It’s likely not a conflict with the calendar jQuery since your custom fields are only being displayed on single event pages. (eg. There isn’t a calendar on the contact us page)

When you modify the event table template to include a new column you’ll need to make sure the event_meta or other variables you are using are set. They’re set on the registration page, but not on other pages. The way forward is to be sure they’re set within the event table template. It may help to set the global variable for the event_meta within the table template like this:

global $event_meta;

January 8, 2014 at 5:40 am

Hi,

In the events table index.php about line 12 you should see

global $this_event_id, $events, $wpdb;

Change it to read

global $this_event_id, $events, $wpdb, $event_meta;

And that will make the $event_meta variable available to you.

January 8, 2014 at 6:36 am

I see, well it doesn’t work on any page unless there is the events. You may need to add that global $event_meta to the sidebar.php or perhaps to the page.php (both part of your theme).

January 8, 2014 at 11:32 am

Hi David,

I don’t think it’s necessary to add the global to page.php. It’s best to add it to the event table template. Simply adding the global variable may not help depending on the code that you wrote to include the extra column.

You asked us to take another look, but without seeing the PHP code that you’re trying to use we’re kind of in the dark with this. If you’d like to post your modified code in a pastebin or a gist and link to it here we can at least take a look and offer suggestions from there. Please understand that this support thread started out with another issue and the issue you are having now has to do with a customization that you made.

January 8, 2014 at 1:46 pm

Hi David,

It’s not really a conflict, but you are missing a few things here. In order to use the EE_META shortcode for a specific event it needs to be within the foreach loop (so the meta can be pulled for each event) It also needs to be unserialized. If you look in the template you’ll see the loop starts on line 41. You can add the meta variables there after the loop starts like this:

foreach ($events as $event){
global $event_meta;
$event_meta = unserialize($event->event_meta);