Quote:
Originally Posted by Zachariah
To put less load on the shoutcast server and to speed up page loads. The shoutcast info the script gets is cached to your local webserver in a XML file. The XML file is called up when there is a request to show the data. If your cache file does not update then you are not connecting to the shoutcast server. (cache file is always "zero" kb)
9 out of 10 times this is because of settings (port,ip,password) or your webhost has blocked ports in their firewall. Many hosts only allow queries for data on port 80 (http, rss, xml feeds). This hack will pull the XML feed from your shoutcast server port. I have seen many webhosts designate a port for "other" needs of their clients.
If you are 100% sure your setting and install is correct.
Send a ticket to your webhost and see if ports are blocked (ie:8000). If so they may give you another port you can use. Reset your shoutcast server to output on that port. Lastly, if there is nothing that your host will do, you can move the shoutcast server to output on port 80 vs. 8000 and your webhost should read the feed.
|
thanks its working.. they have opened us the requested port so its all good..
Can you explain the xml a bit more i understand the caching bit etc.. this option:
Please enter in the Update time of your shoutcast station.
Note: seconds untill cache update
if i set this to 5 will it be recommended? as tracks are changed quite often.
Also sometimes it dosent update without a refresh... or is a refresh required all the time?
Cheers!