Uploaded the latest ultimatebb.php accelerator script and have the following problem:
Main link is ok: /cgi-bin/ubb/ultimatebb.cgi
PHP link returns 404 error: /ubb/ultimatebb.php
UBB.classic Accelerator Test:
Your PHP version is 4.1.2: OK Your PHP version has zlib: Yes Your PHP version has the md5() function: Yes UBB.classic Accelerator should have no issues under this version of PHP. zlib compression is installed and will be used.
I noticed it only did this when I logged in and then continued after I logged out. I cleared the board cookies and it seems to have solved the problem but I'll keep trying it just in case. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />
I deleted all cookies and entered the board logged out. I could access through both cgi-bin & php links. As soon as I log in the php link returns a 404 error.
Sorry if I've missunderstood your question but the 404 errors are appearing from the accelerator link posted above but it only seems to happen when I'm logged in. If you follow a link ( e.g. /ubb/ultimatebb.php/topic/19/125.html ) with the accelerator there's no problems, it's just the main /ubb/ultimatebb.php that's causing the 404.
Aha. You're using the spider-friendly links, but your web hosting provider is using a weird setup.
You'll need to either turn the spider-fiendly links off, or check the "Compatability Mode" checkbox below the spider-friendly options in your control panel.
Ian, compatibility mode puts the ? in if I'm not mistaken.
Also, he's using a rather old version of PHP, and that might be part of the issue, because if I remember right, older versions handle the query string differently.
Please use that link to open up a support ticket. Inside the ticket body, include the URL to this topic (VERY IMPORTANT), and then a request that the ticket be assigned to me.
Per the ticket, this appears to be a case of your web hosting provider having an open_basedir restriction in place. The Accelerator was throwing users to an invalid URL as a result, which is where the 404 was coming from.