I am not sure why the logo is not disabling. The manual has always proven to be correct, but somewhat cryptic. I am including a copy of the script I am using. I changed the path (and I am actually using a .php program to generate the .xml on the fly, but just pretend it says “monoslideshow.xml” not “monomovie.php”.

The trick may be separating the flashvars list with commas, or making sure the quotes are all in the right place.

Hope this helps:

var flashvars = {dataFile: “monomovie.php”,
showLogo: “false”,
showRegistration: “false”
};
var params = {wmode: “transparent”};
params.allowfullscreen = true;
params.allowscriptaccess = “always”;
params.bgcolor = “#000000″;
swfobject.embedSWF(“../../mono/monoslideshow.swf”, “flashContent”, “600″, “420″, “9.0.124″, false, flashvars, params);

Thank you for your responses. Gary you were right. I just needed to change the path of my monoslideshow.xml file. It works great. I was able to customize the size and set it to autoplay. I still cannot, however, get rid of the logo when it first loads the slideshow. I tried the code as instructed in the manual but still doesn’t work.

Anyone I do appreciate the quck response from both of you!

I suspect the issue is where the monoslideshow.xml file resides. I am assuming the slideshow can be played in Lightroom and only gives that error when you run the sports photography page on your web site.

By default Monoslideshow looks for the monoslideshow.xml file in the same directory as the web page code which contains the script to run the slideshow. If the .xml file resides elsewhere, you have to change the path. I used the example script on page 8 of the Monoslideshow 2.16 manual. The section “Loading Custom .XML file” shows how to set: var flashvars = {dataFile: “yourCustomeFile.xml”}; where “yourCustomFile.xml” should contain the path to the xml file. For example if it is called monoslideshow.xml and is in the directory above the calling code, it would read: var flashvars = {dataFile: “../monoslideshow.xml”};

Another problem which can occur is specifying the path correctly. If you are developing on a PC and loading to a UNIX web server, be careful to only use forward slashes (/) in the paths. Also, check for proper cases of the letters. “datafile” and “dataFile” are equivalent on a PC server, but not on a Unix server.

I hope some of this helps.

The Changelog above on this web page shows 1.0.1 still “In development”. Am I missing something? I would like to get the 1.0.1 version.

I had been working with MSS 2.15 for an application that doesn’t use Lightroom and never thought to update MSS in the LR plugin..