Support

January 21, 2014 at 8:26 pm

Do you have the latest version of the calendar installed?

January 22, 2014 at 6:37 am

Hi,

Can you go to the Calendar Settings page and check the settings, and importantly save the settings. Please advise if that resolves the issue or not.

January 22, 2014 at 10:34 am

Hi there,

The clue that I think will guide us to a fix is it works if you’re previewing the calendar page from the admin, but you’re getting the eeCAL is not defined error when you’re not in the admin.

The code in the calendar plugin that defines eeCAL is this:

wp_localize_script( 'espresso_calendar', 'eeCAL', $ee_calendar_js_options );

What this does is pass what’s set in the calendar settings into the the calendar scripts, and that’s why Dean suggested saving the settings to make sure the calendar options were set.

Since that didn’t seem to help, and you’re seeing the calendar when you preview the page in the admin, I’m wondering if this might be something a security plugin is causing. Can you let us know if there are any security plugins installed? We’ll continue to look into this issue on our end (can’t reproduce it yet, so not sure what the fix will be).

Another thing that may help is if we can take a look at the PHP error log. If there’s a PHP error that’s being thrown when the calendar page loads, that could pinpoint the cause of the issue.

January 22, 2014 at 1:37 pm

The PHP error log may or not be on your server. Since servers will differ on where the log file is located (and can be configured to not generate a log file), here’s a link to some documentation that shows how to configure error logging:

http://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Logging

I personally use this one in the wp-config.php file:

define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
}

January 23, 2014 at 11:17 am

Hi there,

The test page you linked to leads to a not found page. It may be that it was not published.

The calendar plugin is working as expected on other sites, so this is something that’s unique to your setup. Other active plugins or even the active WP theme may possibly be affecting the calendar. You could try temporarily deactivating all the non-EE plugins temporarily to see if that makes a difference. Also, the theme can be switched by using the theme test drive plugin so the site will look the same to anyone else but you. If you can rule out the theme and other plugins causing a conflict that will help narrow down what’s causing the issue.

January 24, 2014 at 7:55 am

hmmmm so i tried previewing other themes, twenty twelve, twenty thirteen, twenty fourteen…. and the calenders, both original & the test page work.

So… now what?

Definitely a theme issue then. Maybe the theme is de-registering the required Javascript?

January 24, 2014 at 9:04 am

The theme is a folder that contains a bunch of files. This can be zipped up and attached to an email, then sent to support@eventespresso.com.

http://windows.microsoft.com/en-us/windows/compress-uncompress-files-zip-files#1TC=windows-7

http://osxdaily.com/2012/01/10/how-to-zip-files-in-mac-os-x/

January 24, 2014 at 1:01 pm

Hi there,

I’m afraid that the theme that you sent doesn’t allow us to set it up for debugging purposes without an API key. This is the first time I have encountered anything like this.

Since this is an issue that’s being caused by the theme, and the theme is locked down to the point that we can’t set it up for testing, the only option I can think of is to contact the theme developer for support. You can let them know that the calendar displays on all the WP twenty* themes, it appears when you’re viewing the page in the previewer, but it doesn’t display on the WP page when this theme is active.

January 29, 2014 at 2:36 pm

You can also let them know that the issue seems to be related to the wp_localize_script function. The calendar passes its settings through that function. It works on all the other themes out there, and even within this theme’s page preview. But not if you view the page directly.

January 30, 2014 at 7:21 am

It would be best if they can troubleshoot this since it’s the theme that’s causing the issues, and they should know their way around their theme better than anyone else.

February 3, 2014 at 1:36 am

Please let us know how you get on with this.