WordPress.org

Support

Support » Plugins and Hacks » [Resolved] v1.5.4 broke the fix added in 1.5.2

[Resolved] v1.5.4 broke the fix added in 1.5.2

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Andy Fragen
    Participant

    @afragen

    Can you do me a favor? Put the following code in your theme’s functions.php file and let me know what is shows at the top of the calendar page. In my Default Events Template the result is string(0) “”

    add_action( 'wp_head', 'template_name' );
    function template_name() {
    	if ( class_exists( 'TribeEvents' ) ) {
    		$template = TribeEvents::getOption('tribeEventsTemplate');
    		var_dump( $template );
    	}
    }
    Plugin Author Andy Fragen
    Participant

    @afragen

    Hold off on that for a second

    Plugin Author Andy Fragen
    Participant

    @afragen

    It’s OK to add that code to functions.php. Please let me know both the results as well as what you have selected for the Template on your calendar view. Thanks

    After adding the snippet to functions.php I get the following at the top of the page when viewing the calendar:

    string(22) “template-fullwidth.php”

    My template is set to “Full Width”, which is a template found in the parent theme (Woothemes Listings).

    the content of template-fullwidth.php can be found at:
    https://gist.github.com/4299248

    Plugin Author Andy Fragen
    Participant

    @afragen

    @espedub, thanks for bearing with me. I think v1.5.5 will now fix this issue. I added a pref to check if the calendar takes on the styling of the first event category of the month.

    Let me know how this works for you.

    1.5.5 fixed the problem I was seeing where the first event in a sequence of events that all share the same category was not picking up the category coloring when using the Calender view.

    Thanks

    Plugin Author Andy Fragen
    Participant

    @afragen

    I’m glad this fix worked for you. Thanks for helping me.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Resolved] v1.5.4 broke the fix added in 1.5.2’ is closed to new replies.