Mozilla Problems

I've just upgraded to the latest Ximian Desktop, and mozilla has given up the ghost for being able to read the empeg xml data. I'm running Mozilla 1.3.1.. Are there any other Linux geeks that could confirm/deny this problem?

If you're trying to use the charcoalgray9? XML web interface to the Hijack web server (just say yes if you didn't understand that), then I also have never had much luck with it. I use only Mozilla and Konqueror here, and the charcoalgray thingie hals always seemed IE-centric.. or at least it only seems to work with IE.

I'm currently using Mozilla-1.4beta, and still no joy.

Cheers

Yes, I'm Using Charcolgrey's XML interface. Ug, is there a way to get it to just display html when I'm at work?

Yeah, just surf to http://your.empeg.ip.address/?FID=101&EXT=.htm

Mark, I've narrowed down the problem with Charcoalgray99's web interface with Mozilla. One thing that is a problem is the way Hijack sends the mime type for .xsl files - it should be text/xml just like you have noted on line 833 in kftpd.c. Mozilla will not recognize the xsl transformation unless the mime type sent by the server is text/xml. If you could change this line in Hijack, we'll be one step closer.

Secondly, there is a problem with either the linked .css file or the linked .js file in Charcoalgray99's xsl file that makes Mozilla hang when viewing the playlists. Here are the steps I took to get the playlist view working (somewhat) with Mozilla:

1. Commented out the two lines 17 and 18 in default.xsl:

<!--link rel="stylesheet" type="text/css" href="/drive0/opt/khttpd/charcoalgray99/css/default.css"/-->

<!--script language="javascript" src="/drive0/opt/khttpd/charcoalgray99/js/jscripts.js"/-->

2. FTP'd the new default.xsl file into the root directory

3. When going to a link, use the URL http://empeg/?fid=101&ext=.xml NOT http://empeg/?fid=101&ext=.xml&style=/drive0/opt/khttpd/charcoalgray99/xsl/default.xsl. The latter does not work in Mozilla.

4. Alternately, if you would like to have the default.xsl file in another location, you will need to set the khttpd_style entry in config.ini to the full path to the default.xsl. By default, the .xml documents are generated linking to /default.xsl unless this config.ini entry is set.

Here's a screenshot of the playlist running on Mozilla:



I will PM Charcoalgray99 to see if he wants to fix his stuff. If he doesn't, I will consider writing a new xsl stylesheet to work with Mozilla. I might anyway, just because I like to have a lightweight interface with no graphics.

That's cool. The next Hijack release will include the one-liner you suggested.

Cheers

>One thing that is a problem is the way Hijack sends
>the mime type for .xsl files - it should be text/xml

Done. Hijack v339 is now available.

Thanks, Mark!

I pm'd charcoalgray99 and he said he would not have the time to work on the web interface to make it compatible with Mozilla. He did tell me to feel free to modify anything in the web interface to make it work with Mozilla, and I am assuming that means that anyone else is free to do so also. If someone decides to modify his current web interface to make it work with Moz, I would probably check with him first to arrange hosting/distribution of the new web interface.

I won't be doing this, though. I will probably be rewriting the web interface to learn more about XSL and Mozilla, and I prefer a simpler, more graphics (and javascript) free interface anyway. There will be one more release of Palantir before this, then I'll work on the web interface for Mozilla (and standards-compliant browsers).

I will probably be rewriting the web interface to learn more about XSL and Mozilla, and I prefer a simpler, more graphics (and javascript) free interface anyway.

Hallelujah and thank you. If someone can come up with something that runs properly in Mozilla and its derivatives (Safari would be a nice bonus for me) I am sure there are at least a few of us who would appreciate it.

-Mike

Anyone ever have a chance to look at this?

(Mmmm... 18 month old threads....)

Nope, no progress yet. It did get put into the front of my mind, though!