Realmac Software

Hello,

I am a noob here and am hoping someone can help me with a problem with CrossSlide using the Glide 2.0 theme.
I have managed to get the slideshow running, however a user on Windows NT 6.0 using IE 8.0 cannot see the CrossSlide show. They do report they have Javascript turned on but that an error was reported.
Here is the reported error:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
Timestamp: Thu, 18 Mar 2010 03:49:36 UTC

Message: ‘plan[...].src’ is null or not an object
Line: 276
Char: 4
Code: 0

I’m just getting my brain around CSS so I’m totally in the dark here. Is there a code patch that I can inlcude in the javascript code for CrossSlide?

Here is the javascript inputted into the custom javascript pane in the page inspector;

var $cf = jQuery.noConflict();
$cf(document).ready(function() {
  $cf(’#pageBanner’).crossSlide({
shuffle: true,
sleep: 22,
  fade: 2
  },
[
  { src: ‘assets/triplog_index_header_01.jpg’ },
{ src: ‘assets/triplog_index_header_02.jpg’ },
{ src: ‘assets/triplog_index_header_03.jpg’ },
{ src: ‘assets/triplog_index_header_04.jpg’ },
{ src: ‘assets/triplog_index_header_05.jpg’ },
{ src: ‘assets/triplog_index_header_06.jpg’ },
]);
})

This works fine in both Safari and Firefox on OS X
I hope I have done all the right things in making my first post.

jaden85 - 18 March 2010 05:14 AM

I hope I have done all the right things in making my first post.

Welcome to the forums! A great first post~

In regards to your question, the problem you’re running into is due to an error in your CrossSlide code. There should be no comma at the end of the line for the last image you specify. For example, in your code above you have six images added like so:

See the comma at the end of the last line? You’ll need to remove that to get things working in IE - Mac browsers are quite flexible about working around small errors like this, but IE’s javascript support is horrible, so everything needs to be just right to work properly.  Once fixed, this section should look like so:

Once you’ve done that, IE should behave properly.

Hope this helps.

Best,

Jonathan
NimbleHost.com

Hope this helps.

Best,

Jonathan
NimbleHost.com

Oh my gosh! It most certainly does help Johnathan and yes, you are a guru!
One little comma…sheesh!

Thank you very much for this, you Rock!