Support

December 22, 2015 at 8:55 am

It sounds like something is resetting the query. Do you have the same version of WordPress on both sites?

One other thing you can do that may help is remove those double quotes for each parameter value, with the exception of the title= parameter, and you’ll want to make sure that those are not curly quotes in your code.

December 22, 2015 at 9:01 am

I asked about the WordPress version because I was wondering what other things might be different from the dev site to the live site. If it’s only https and WP version, then that may be an indication that is a WP version issue. But if this worked before on WP 4.3.1, then it may be something else unique to the live site.

December 29, 2015 at 2:20 pm

You’ll have a better time with the custom template if you do not use the [ESPRESSO_EVENTS] shortcode within the template using do_shortcode calls. It was never intended to be used this way. If you’re already using a template, you can do multiple loops within the template.

FWIW, The issue with using $wp_query as a variable was earlier brought up with the lead developer of Event Espresso and his reply was:

Because of the fact that we are properly resetting the $wp_query global after our usage, which means that it should not have any adverse affect on other uses of it. It kinda works like this:

// set by theme (or WP or whoever)
$var = "banana";

// later on in our code...
$original_var = $var;
$var = "monkeys";
// do some stuff

// reset $var
$var = $original_var;

// meanwhile back in the theme (or WP or wherever)
echo $var;
// **should** output:  banana

so as you can see, even though we redefine $var, it has no effect on any other code because of the fact that we reset it after we are done with it. Of course, a theme could do something funky and unorthodox which complicates this and blows things up, but we shouldn’t have to jump through hoops to accommodate bad code, when ours is following proper WP convention. Redefining the $wp_query global IS proper WP convention and is perfectly acceptable, which is why they have functions available for resetting it. They wouldn’t do that if you weren’t supposed to touch it !
all of the places where we are redefining the $wp_query global are places that for all intents and purposes, should behave as if they were the main query. We currently have LOTS of code that performs checks for the main query and then applies changes and/or runs some logic if the main query is encountered. If we were to change our shortcodes that redefine the $wp_query global, then some of those checks would return false and those changes/logic would no longer be applied. We will have to find some other more complicated way of identifying whether or not the current query should be processed.

December 29, 2015 at 2:45 pm

To be clear, the judgement/remarks regarding $wp_query belong to the lead developer of Event Espresso, they are not mine.

December 30, 2015 at 8:38 am

That’s likely coming from the options table.