This would depend on how you have configured the RSS. If you have set it to do caching, the apache process needs write permissions on the RSS directory. If it doesn't have write permissions, the cached RSS feeds will never get created and so the index scripts will redirect you to an nonexisting page.
If you set the rss for "live"/"non-cached" feeds you shouldn't have this problem. See rss_conf.php for this information. You also need to define some paths in the configuration file, so you should take a look at it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now that is bizarre. I just looked at the index scripts and it isn't doing any URL-encoding for the actual RSS scripts, unless your browser is doing that, and if then it should be transparent.
Are you using the index_sample.php script?
Are you sure the script exists where the browser is telling it to go? If you are using URL forwarding on your domain name it may not work properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Subdomains shouldn't cause this issue, neither should VirtualHosts in apache. The domain forwarding I am referring to opens up your page in an iframe.
I am wondering if there is a setting for the http server that automatically encodes all URLs. I haven't heard about this from anyone else, and I am using it as well, and I've checked both the script and the output and the ones I'm checking do not do any type of encoding at all.
Are any of your other links encoded in this way?
Also I'm in #phpbttrackerplus on irc.freenode.net if you want to attempt realtime help on this. I'm not always there though so you might have to sit and wait a while. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wait a second, now I know what you mean. I thought it was to do with the URL that linked to the RSS component on the index page, but the links *in* the RSS are like this. I'll take a closer look at this, and while I'm at it, maybe I'll try to add individual subgroup RSS feeds. I don't see why browsers would have a problem with that encoding though.
There may be a v2.2 released in [hopefully early] January.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I like to ask how the RSS work? coz whenever i click the torrent (in firefox's livebook mark) it redirected me to a wrong/invalid page.
This would depend on how you have configured the RSS. If you have set it to do caching, the apache process needs write permissions on the RSS directory. If it doesn't have write permissions, the cached RSS feeds will never get created and so the index scripts will redirect you to an nonexisting page.
If you set the rss for "live"/"non-cached" feeds you shouldn't have this problem. See rss_conf.php for this information. You also need to define some paths in the configuration file, so you should take a look at it.
hm...but i dont have rss cache enabled.
maybe my question is a bit confusing?
the problem is that it replace the "/" of the url with "%2F" (and some other symbol too, like "[" and "]"
^
related to path settings?
Now that is bizarre. I just looked at the index scripts and it isn't doing any URL-encoding for the actual RSS scripts, unless your browser is doing that, and if then it should be transparent.
Are you using the index_sample.php script?
Are you sure the script exists where the browser is telling it to go? If you are using URL forwarding on your domain name it may not work properly.
yup. im using index_sample.php But I modified some part of it (to change the look and feel of the tracker)
Im using a sub domain for the tracker.
ie: http://tracker.somewhere.com
while the actual folder is at:
ie: /home/public_html/www/tracker
^ is this consider as URL forwarding?
Subdomains shouldn't cause this issue, neither should VirtualHosts in apache. The domain forwarding I am referring to opens up your page in an iframe.
I am wondering if there is a setting for the http server that automatically encodes all URLs. I haven't heard about this from anyone else, and I am using it as well, and I've checked both the script and the output and the ones I'm checking do not do any type of encoding at all.
Are any of your other links encoded in this way?
Also I'm in #phpbttrackerplus on irc.freenode.net if you want to attempt realtime help on this. I'm not always there though so you might have to sit and wait a while. :)
Wait a second, now I know what you mean. I thought it was to do with the URL that linked to the RSS component on the index page, but the links *in* the RSS are like this. I'll take a closer look at this, and while I'm at it, maybe I'll try to add individual subgroup RSS feeds. I don't see why browsers would have a problem with that encoding though.
There may be a v2.2 released in [hopefully early] January.
ya...thats what i mean. ^^;
any quick fix for it?
There is now, and it's available on the file releases page.
Look for the patches download called '[v2.1] patches 2005-12-15'. It contains the file with the RSS fixes.