Hi, I've bought a license of SlideshowPro which is Flash. Now I have problems to include this into my skin file in Dotnetnuke.

The slideshow includes the swf, xml file and a folder with images.

Apart from using it in the skin file I tried using it with the media module, but it doesn't work. I tried different locations (portal/0/...) for the files, but without any success.
With the media module it shows only the flash background, but it didn't load any images from the xml file.

Please can someone come up with an idea where all the files are have to be located?

Thanks in advance

Patricia

At a guess the images will need to be in your skin zip file. - but you will need to ensure that the XML file has the correct URL for the images. - I have not set this up before so I'm taking a stab in the dark,

Thanks,

Hi Lee, thanks for the quick answer. I managed to get it worked, but without my javascript which I included. The javascript code should handle the grey border in IE. For that I have a external javascript file, which pointed to the index.htm file within my skin folder.

Do you have an idea, where I have to include the javascript within Dotnetnuke or do you know some other ways how I can avoid the ugly looking flash border in IE?

Many thanks in advance...Patricia

  If you are wanting to work with an external JavaScript file, have a look here: Incorporating sIFR (Scalable Inman Flash Replacement) with DotNetNuke skins

scroll to the bottom and there are some key points for Video 5 which outlines adding JavaScript to DotNetNuke for 4.3+

...thanks!

Hi,

I've been experiencing a similar issue trying to move a SlideShowPro image gallery into a DNN installation. I can get the .swf container to display on the page fine, but I don't get any of the images to load in the .swf player. The .swf file references a separate .xml file which points to a set of folders that contain the images. I've placed the .swf, .xml and the set of folders with the images into the portal root, ..\Portals\0. The .xml file relatively references the images folder, "gallery/album/large/".

If I double click on the .swf file in it's current location in the Portal directory, it opens Flash player and plays as it should. It just doesn't work when I call up the .swf file in the webpage within DNN. I've tried adding the .swf file using the Text/Html, Media and DigFlash modules. They all show the same result - .swf container loads, but no images. I haven't tried placing the code directly in the skin file as I would like to use the same skin file on different pages, but have different images galleries/.swf files for each.

I'm guessing the issue has something to do with the way DNN changes the URLs, but I'm not certain.

Anyone have any other ideas of how to solve this?

Many thanks,
~Chris

You need to somehow find out what the URL is that DNN is producing for the images - or the url that the swf container is creating - it maybe the swf container that is not using the correct url to call in the images

Hi Lee,

Thanks for the quick response. The page that contains the .swf file is located at...tabid/155/default.aspx. From the source code of the page, it's referencing the .swf file at "src='https://www.dnncreative.com/DNN_492_test/LinkClick.aspx?link=ss_home.swf&tabid=155&mid=489'.

The .swf file references an xml file that is in the same directory as the .swf. That .xml file reference a set of images, one folder level up at "gallery/album/large".

I imagine that the .swf should be able to access the .xml in the same directory and that the breadown is in the .xml file referencing the images folder. I can easily change the reference in the .xml file, however, I'm not clear as to what I should change it to. Any thoughts on how I should fix this?

I tried using a friendly URL rewriter, however, still no luck. I'm guessing that DNN still references objects using the original URLs.

Thanks,
~Chris

If your swf is in a Text/HTML module, and you specified the link to the file as "a file on this site" try going back an unchecking the boxes that provide tracking links.  When you do that, the link should be a standard http link, without the LinkClick.  That way, you might get a more direct look at what DotNetNuke is trying to do.

Thanks. Once I did that, I was able to clearly see the pathway and updated my .xml file to have "/FCC/Portals/0/" in front of the original file path and it worked fine. Thanks again.