I got it.

I needed to begin my src from the root folder.

<object classid="clsid:02BF25D5-8C17-4B23-BC80-D3488ABDDC6B" codebase="http://www.apple.com/qtactivex/qtplugin.cab" height="500" width="640">
<param name="src" value="/Lightning.mov">
<param name="autoplay" value="true">
<param name="controller" value="true">
<embed height="256" width="320" src="/Lightning.mov" pluginspage="http://www.apple.com/quicktime/download/" type="video/quicktime" controller="true" autoplay="true">
</object>

See the clip athttp://armstrong.flyingriver.com

I've put an embed tag

<embed src="Lightning.mov">

in a blog entry on my XOOPS site. When I view the blog, I get a download error. When I view the src, I see

<EMBED src=Lightning.mov type="text/html; charset=iso-8859-1">

I'm guessing the type attribute is being supplied automatically by xoops, and that it is causing the download to fail.

Anyone know how to correct this?

I cut my teeth on PostNuke, and its modules resolve relative urls starting from the root folder of the PostNuke install.

So, I was a little surprised to see that XOOPS modules do it differently -- they seem to resolve starting from the specific module's folder.

So, a link like <a href="myFiles/file.txt">my File</a> in a news article, would resolve to

<root folder>/modules/news/myFiles/file.txt

in Xoops

and to

<root folder>/myFiles/file.txt

in PostNuke.

Is this intended behavior? Does anyone know why XOOPS handles it this way? Is there a configuration setting to change this behavior?

Thanks,

David