Home → Velocity Formats →

Events calendar pop-up

• Edit

lauren.fraser

17 Feb, 2014 05:10 PM

We have the Events Calendar from GitHub installed and love it. http://www.citizensmemorial.com/1calendar/index.html

I noticed today that if you click one of our Community Events or Childbirth classes, that in the pop-up that shows - it is showing the path to the block that feeds the address/location field. In our instance, this is a cross-site link, as we store all of our locations blocks in our main site. Can you tell me what format controls these pop-ups?

Also, with our google calendar feed, When you click on the "view event" link from the pop up field. it asks you to sign in to Google calendar. Is that what we should expect? Our calendar is set to public. I'm not sure if there's another setting in Google calendar that we need to change.

Thanks in advance for the help.

1. 1 Posted by Ryan Griffith on 17 Feb, 2014 06:11 PM

   

   Hi Lauren,

   It sounds as though the issue is coming from the Format that generates the XML data the full calendar page ingests, specifically the location element. This particular Format is located at _cascade/formats/outputs/xml/event-xml-builder.

   I'm thinking you'll need to adjust the XSLT that generates the value to work with your shared block, instead of a text field within the page itself. The line you would be looking for is:

   <location><xsl:value-of select="$pageSDS/location"/></location>
   

   Please let me know if you have any questions.

   Thanks!

   • Edit

2. 2 Posted by lauren.fraser on 17 Feb, 2014 10:03 PM

   

   Ryan,
   Thanks. Unfortunately, I'm not well versed in XML.

   It does show the value of the shared block, but then it's also showing the xml path. I've attached a screenshot.

   Would this be what I need to change the XSLT to:
   <location><xsl:value-of select="$pageSDS/location/value"/></location>

   • eventPopup.gif 7.53 KB
   • Edit

3. 3 Posted by Ryan Griffith on 18 Feb, 2014 01:02 PM

   

   Hi Lauren,

   If your location field is a block chooser, your XPath would need to reference the chosen block's content. As it stands now, the Format is probably just dumping the value of the block's content and path.

   For example, let's assume the chooser's identifier is location and you have either an XML or XHTML block chosen. You should be able to output the block's content using the following:

   <location><xsl:copy-of select="$pageSDS/location/content/node()"/></location>
   

   This should copy over the content (including HTML tags) within the chooser's content.

   Please let me know if you have any questions.

   Thanks!

   • Edit

4. 4 Posted by lauren.fraser on 18 Feb, 2014 09:00 PM

   

   Ryan,
   I made this change and I'm still seeing the block information and the unstyled content.

   • Edit

5. 5 Posted by Ryan Griffith on 19 Feb, 2014 02:31 PM

   

   Hm, definitely interesting.

   Are you referring to the pop-ups on your live site or within Cascade Server? if the live site, have you tried re-publishing everything again? Specifically, you would need to re-publish the year and month folders so the XML files used by the calendar are updated.

   Please let me know if you have any questions.

   Thanks!

   • Edit

6. 6 Posted by lauren.fraser on 19 Feb, 2014 02:51 PM

   

   I just republished the index page. I'll republish the folders and let to

   Lauren Fraser

   • Edit

7. 7 Posted by lauren.fraser on 19 Feb, 2014 06:31 PM

   

   Ryan,

   I only published the index. Once I published the year & month folders, they popups on the live site aren’t showing the block info.

   Thanks,

   Lauren

   • Edit

8. 8 Posted by Ryan Griffith on 19 Feb, 2014 06:40 PM

   

   Thank you for following up, Lauren. I am glad to hear re-publishing those pages fixed the issue.

   I did notice the HTML tags are being removed when the calendar pulls in the information. It looks like if you want those tags to be retained, you would need to edit the JavaScript file we use to generate the calendar (_files/js/plugins/jquery.hhcalendar.js). Specifically, you would need to change all references of $("location", element).text() to $("location", element).html() and that should do the trick. There should be 2 of them around lines 186 and 294.

   Please let me know if you have any questions.

   Thanks!

   • Edit

9. 9 Posted by lauren.fraser on 20 Feb, 2014 08:06 PM

   

   That did the trick. Thanks Ryan!

   • Edit

10. lauren.fraser closed this discussion on 20 Feb, 2014 08:06 PM.