Jump to content


Trumba Community Member
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Troy

  • Rank
    Advanced Member

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
    Seattle, WA
  1. Target _blank

    My brain gets it now ! Let's get even more specific - I'm assuming that you've got a Trumba calendar spud embedded on a page in your portal right? And you want event detail links to display in a new window, a pop-up window, not the window in which the calendar/portal is being displayed. The user would then have to close that external window using the back to calendar link (we'd pass the page enough info to know that it should do a window.close()) or using the native OS window close button. That's what you're digging right? -Troy
  2. Target _blank

    I think we're almost there. When you say you don't like loading content into the parent window that tells me you have a frameset. I know that we don't play well with framesets right now. Is this the issue? If you've got a URL I can look at it would help me understand just what is the bad behavior on our part.
  3. Target _blank

    Evan, This is something we can work on but first I want to understand your situation exactly. You say you don't like to load pages on top of portal pages but instead want to display event details in a new window. Would that new pop-up window not be on top of your portal pages? So you don't care if a new window sits on top of the calendar but you do care if the event details are displayed in the same space as the calendar which is our default behavior. Correct? Set me straight so I can help you out here. Troy
  4. What you encountered was a 10-minute caching window for Spud requests. All Spuds are cached for 10-minutes so new events won't show up until you either clear your cache or wait for the client cache to invalidate the request. Here is a link to our help topic with additional information.
  5. bbern, Thanks for pointing out that the page is wrong. I'll let docs know. -Troy
  6. bbern, I can't repro this so I must not be following your question. I've created an example page below using the KEXP calendar which is set to 3 Columns layout in the Publish Settings. I've overidden the template parameter on both Spuds to be month and sure enough the Choose says Month and the calendar is a Month grid. <html> <body> <script src="http://www.trumba.com/k.aspx?calendar=kexp&widget=chooser&template=month" type="text/javascript"></script> <script src="http://www.trumba.com/k.aspx?calendar=kexp&template=month" type="text/javascript"></script> </body> </html> So where did I not follow your original question? -Troy
  7. help Extra claendars showing up.

    My guess is you have a type in your code. I just pasted your Javascript into an HTML file and it works fine in FireFox. Or is it a browser issue? What browser are you using? Here's a snippet that works for me. I did clean up your example by yanking the language attribute and quoting the type attribute. <html> <body> <script src="http://www.trumba.com/k.aspx?calendar=central_baptist_church_calendar" type="text/javascript"></script> </body> </html> -Troy Edited by Jill to get rid of auto bb code formatting the url.
  8. Yes, of course it's chopped, very typical of IFRAME height. You can paste the following code into your events.htm file to get it to auto-size to the calendar. <script type="text\javascript"> function resizeIFrame() { var name = window.name; var iframe = window.parent.getElementById(name); if (iframe == null) iframe = window.parent.frames[name]; if (iframe != null) { // adjust the iframe's height based on its contents if (iframe.contentDocument && iframe.contentDocument.body.offsetHeight) iframe.height = Math.min(iframe.contentDocument.body.offsetHeight, 10000); // netscape/firefox else if (iframe.Document && iframe.Document.body.scrollHeight) iframe.height = Math.min(iframe.Document.body.scrollHeight, 10000) + 2; // internet explorer } } window.onload = resizeIFrame; window.onresize = resizeIFrame; </script> Mind you I wrote this really fast and wasn't able to test the code. I'll try it out in the morning but you can go ahead and try it right now if you want. The idea is that whenever your iframe loads or resizes you redo the document height. This is a known and tricky issue with IFRAMEs. It's based on code inside our Spuds that does essentially the same thing. There could be an issue if the Spud grows too much but we'll deal with that when we get there. -Troy
  9. Help me please

    Why don't you post the URL to your web page so we can take a look, I'm sure we can help you with it. -Troy
  10. Help me please

    IMTStyles, Our Spuds are all JavaScript so there's no way to embed Spuds without using JavaScript. However you could fake the embed by instead embedding our hosted version of any published calendar. For example, http://www.trumba.com/calendars/kexp hosts the KEXP calendar. It's raw HTML only. You could embed this using an IFRAME or a FRAMESET. Here's an IFRAME that does just that: <html> <body> <iframe src="[url="http://www.trumba.com/calendars/kexp"]http://www.trumba.com/calendars/kexp[/url]" frameborder="0" width="100%" height="100%"></iframe> </body> </html> [size="1"][color="#0000ff"][/color][/size] You're limited to the hosted page and all it's Spuds. To get a lesser set of Spuds you'd have to use JavaScript. I hope this helps. -Troy
  11. Kevin, This is a very interesting situation that I haven't encountered yet. Thanks for bringing it to my attention. What's happening here is that you've nested a Spud inside an IFRAME that you are re-using for navigation. I'm talking about MainiFrame. Normally this Spud would have not interfered with the operation of your IFRAME and your site would work as you would expect. However you added an Upcoming Spud to your home page which is causing the main calendar Spud inside events.html to take over your MainiFrame. This is actually intentional and is used to support our older but now deprecated method of putting Spuds in IFRAMEs. Here's how you can fix it. First you need to create a new file called eventsiframe.htm and place it in the same directory as events.htm. Here's the source for eventsiframe.htm: <html> <head> <meta http-equiv="Content-Language" content="en-us"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> </head> <body> <script type="text/javascript" src="http://www.trumba.com/k.aspx?calendar=saaac_calendar"></script> </body> </html> Now you need to edit your original events.htm and replace the <script>...</script> tag that points to trumba with a new <iframe></iframe> tag that points to the eventsiframe.htm file that you just created. Here's the what the source of events.htm looks like now: <html> <head> <meta http-equiv="Content-Language" content="en-us"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <title>Events</title> </head> <body> <b><font face="Arial">Events (2006-2007 School Year)</font></b> <br> <hr> <table border="0" width="100%" id="table2" cellspacing="0" cellpadding="0"> <tr> <td> <iframe id="TrumbaIFrame" src="eventsiframe.html" frameborder="no" width="100%" scrolling="no" marginheight="0" marginwidth="0" allowtransparency="true"></iframe></td> </tr> </table> </html> What I'm doing with this fix is that I'm creating the Spud inside it's own IFRAME which in turn lives inside your MainiFrame. This avoids the conflict between the Upcoming and Calendar Spuds and gets your site working again. Let me know how this fix works out for you. -Troy
  12. Thanks Bruce, I'll fix this to use a separate window. -Troy
  13. Inline Frames

    Dr. Hansen-Quao, Using inline frames (IFRAME tag) to embed spuds works fine. However you don't need to do so as we do that for ourselves already. Thus you'd be putting an IFRAME in and IFRAME, an unnecessary step. You need only insert our Spud SCRIPT tag where you desire the Spud in your document. As for keeping you on your site, you need to do as wyndwoman said and define another page on your site that houses a calendar Spud that you want to display when events are clicked in the date finder or upcoming Spuds. You set the trumba_teaserBase variable to point to this calendar page. I recently explained this in the following two threads. http://forums.trumba.com/index.php?s=&...post&p=3205 http://forums.trumba.com/index.php?showtopic=878 I hope this helps. -Troy
  14. bbern, Please see my follow-up at http://forums.trumba.com/index.php?showtop...&gopid=3192. This has nothing to do with web servers, Trumba code or your Apache config. It's simple a scripting issue. -Troy
  15. bbern, I just took a closer look at your code and there's something I missed in your IFRAME example. My recommendation of using calendar.jsp for trumba_teaserBase is incorrect, it should have said to use a different page, the one that contains your calendar Spud. For the sake of example let's simplify things. First off, drop trying to use IFRAMEs. We're going to abandon it in the future and it only adds complexity to your site. I've simplified your example using non-IFRAMEs which works fine for your calendar. There are two files, datefinder.html and calendar.html. datefinder.html will jump to calendar.html when you click on a day. Save these files to your site and load them in the browser. You should find that they work. datefinder.html <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Language" content="en-us" /> <title>Trumba Testing</title> </head> <div id="content" style="width:200px;"> <script> var trumba_teaserBase = "calendar.html"; </script> <script type="text/javascript" src="http://www.trumba.com/k.aspx?calendar=constantcontactEventsAz&widget=datefinder"></script> </div> </body> </html> calendar.html <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Language" content="en-us" /> <title>Trumba Testing</title> </head> <div id="content"> <script type="text/javascript" src="http://www.trumba.com/k.aspx?calendar=constantcontactEventsAz"></script> </div> </body> </html> -Troy p.s. Edited by Jill 25 Aug. to remove sneaky "a href" tags from code