For years now I thought that Support had to work the magic that made the schedule appear on the front page of an event community. Nope, it turns out it is as simple as embedding the Introductory Text on the schedule track page (duh). Of course, then you have to run both a tract level (schedule) and a theme level (year) update to get it to show up.
From the correspondence files:
I think what we’ve got here is another case of the introductory text in the theme configurations instead of the track configurations. If you look at the configurations for the track from 2015, you’ll see that it’s <h3>:
http://digitalcommons.brockport.edu/cgi/user_config.cgi?context=divconf/2015/schedule
The track level for 2016 is still showing the h2:
http://digitalcommons.brockport.edu/cgi/user_config.cgi?context=divconf/2016/schedule
You’ll want to update the track level configurations to match that <h3>, then run a track level update and a theme level update.
I might also suggest removing the theme level (2016) introductory text from this year (and maybe 2015) so you don’t run into this again next year.
Another new discovery - if you want to keep text in the coding, but hide it from view the way to do that is - <!-- text to be hidden -->.
No comments:
Post a Comment