error on line 8 at column 100: xmlParseEntityRef: no name
jhaggenburg - May 14, 2008 - 15:52
| Project: | XSPF Playlist |
| Version: | 5.x-0.12 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
For a moment it all worked really well, but all of a sudden the flv-player isn't showing and when I go to examle.com/xspf/node/182 I get:
This page contains the following errors:
error on line 8 at column 100: xmlParseEntityRef: no name
Below is a rendering of the page up to the first error.what could be done to fix this? (in short therm..!)
Thanks,
J.
#1
Can you either give me a url to look at, or paste the source of that page here?
#2
I've just reinstalled FLV Media Player, SWFObject and XSPF playlist and this error is now gone. Unfortunately, the player still isn't showing, because "example.com/crossdomain.xml" isn't found. I'm not sure if this is an XSPF-error, but do you know what it could be?
#3
A nasty issue that can bite you with xspf_playlist is that a blank xspf page can get cached, and then you can't get it over ridden without dumping your cache. That might be what's going on. I need to make some kind of interface that prevents this, ala views.
#4
i've just did a Empty Cache with the developer-menu and even added a new node with a flv. Same result :(
This is the final source:
<div class="content"><div id="flashcontent_mediaplayer_1" >Sorry, you need to install flash to see this content.</div>
<script type="text/javascript" src="/sites/all/modules/swfobject_api/swfobject.js"></script><script type="text/javascript">var so1 = new SWFObject('http://maxedamasterclass.nl/sites/all/modules/flvmediaplayer/mediaplayer.swf', 'swf_mediaplayer_1', '400', '320', '5', '#FFFFFF');
so1.addParam('type', 'movie');
so1.addParam('allowfullscreen', 'false');
so1.addParam('allowscriptaccess', 'true');
so1.addVariable('width', "400");
so1.addVariable('height', "320");
so1.addVariable('file', "http://www.maxedamasterclass.nl/xspf/node/184");
so1.addVariable('enablejs', "true");
so1.addVariable('allowscriptaccess', "always");
so1.addVariable('shuffle', "false");
so1.addVariable('overstretch', "none");
so1.addVariable('repeat', "list");
$(document).ready(function () { so1.write("flashcontent_mediaplayer_1");}); </script>
#5
are you seeing an javascript errors? I unfortunately can't get to your page, so I can't see it, but your code looks good and your xspf page looks good to me.
#6
Oh, it could be that your domain is: http://www.maxedamasterclass.nl/xspf/node/184, but your player is being served from http://maxedamasterclass.nl/sites/all/modules/flvmediaplayer/mediaplayer...
The www/maxedamasterclass could be the issue
#7
Hey thanks for your time!
Yeah, it could be easier if you can view the site, so I made a temporary user.
http://www.maxedamasterclass.nl/
user: temp
pass: temp
meanwhile node 184 is deleted, so I also made a new one, #185.
I'll go looking in the javascript-area, but I'm not very familiar with js. Anyway, if you wanna peek once more I'll be very thankful! :)
#8
Good guess, the www.-issue was the one!
problem is.. if a visitor enters the adres without the www, it's not working. Is there a quick workaround for this?
#9
There is a way- basically, you need to make sure that the url that you set for the FLVmediaplayer path is the same as xspf, and the way to ensure this if you're not forcing urls with apache, is to add a config option in your settings.php file
{{{
$config('xspf_playlist_base_url' => 'http://same.domain.com');
}}}
Let me know if that works for you
#10
Thanks. I've tried adding this to my settings.php file, but got some errors. Should I just copy/paste that? Is that php-syntax with those {{{ ?
#11
Ahhhh, woops! wrong text markup format. You should be able to add:
$conf['xspf_playlist_base_url'] = 'http://www.yourdomain.here';There is usually a $conf array in your settings.php file at the bottom that has been commented out. Since I can't see yours, as long as you put this code at the very end of the file, you should be fine.
#12
YEAH! Thanks a lot, this totally did the trick - for now :-)
But now I'm wondering.. Am I the first one that came up with this? It isn't that weard, is it?
Anyway, thanks again for your support!
#13
#14
Automatically closed -- issue fixed for two weeks with no activity.