Solspace Template Morsals and Calendar

Question

I've been trying to diagnose a problem that I started a thread here:

Solspace calendar 500 error

I have it working somewhat using the following:

{exp:calendar:cal  
         {if segment_3 == ''}
          {exp:template_morsels:fetch 
            name="events_calendar_cm" 
            segment_4="{segment_4}" 
            segment_5="{segment_5}" 
            } 
         {/if}  
         {if segment_3 != ""}   
            {exp:template_morsels:fetch 
            name="events_calendar" 
            segment_4="{segment_4}" 
            segment_5="{segment_5}" 
            } 

        {/if}

}

Event_Calendar Morsal

 date_range_start="{segment_5}-{segment_4}-01"
 date_range_end="{segment_5}-{segment_4}-last"

I've also tried using different variable names like seg_4, seg_5, etc. No difference.

The calendar loads, however, it's only loading the first week on both cases:

http://figlancaster.com/events/cal/

http://figlancaster.com/events/cal/month/06/2014/

Plus, the segments don't seem to be parsing for 06/14.

Any thoughts?

Answer 1

Having {exp:...} tags used for parameters for another {exp:...} tag is a recipe for disaster. That's because {exp:...} tags won't parse before another {exp:...} tag. In your case, {exp:template_morsels:fetch} won't parse before {exp:calendar:cal}. You would know this by turning on Template Debugging and looking for your {exp:calendar:cal} code. Likely you'll see unparsed {exp:template_morsels:fetch} code in there.

Further, the way Template Morsels is used above won't help much with performance. TM allows caching of portions of template code in a manner which performs better than normal EE template or tag caching. However, caching two parameters won't do much to performance. What should be done, if Template Morsels winds up being the only solution (see the other thread about the 500 error first), is put the whole {exp:calendar:cal} code in a morsel.