No, as the thread itself has been destroyed. You will need to delete the topic file. Please upgrade to beta 2.1...
I can't delete it. I get the same error message when I try. I've downloaded the 2.1 upgrade as you suggested, but if I upgrade with that thread still there, won't that cause a glitch during/after the upgrade?
Also, I noticed that the upgrade has a PHP test and another PHP file. How do I use these? Since things are a bit changed around here at Infopop, is there a forum for the PHP information?
Delete the actual topic file using FTP - that's the only way to get it done. You can find out more information on the Accelerator at this URL
Thanks, Charles, you're the fastest tech in the west <img src="https://www.ubbcentral.com/boards/images/graemlins/laugh.gif" alt="" />
My site host has this info on PHP4:
PHP 4 is now available as CGI binary on all servers. We are keeping PHP 3 as an Apache module to prevent any possible problems with people's current scripts. Thus, any files you already have with the .php extension will still run the exact same.
To use PHP 4 you: 1. Put the path to php4 as the VERY FIRST LINE of your script, before anything else: #!/usr/bin/php4 2. save your PHP files with the .cgi extension. 3. Set the permissions of the script to 755.
I'm guessing this would cause a problem changing the script to read the way they want for the files to work, plus I wouldn't have a clue what all files would have to have that change. At any rate, as always, thanks for your very quick responses. I really appreciate your patience.
Second, rename ultimatebb.php and ubbaccel_test.php with .cgi extensions.
Third, edit those two files to include the path to PHP, as noted by your host.
Fourth, set permissions on the files - 755 should do it.
Fifth (phew), visit ubbaccel_test.cgi in your browser, note the output. Make sure that the tests pass.
Sixth (getting there), edit ubb_lib.cgi. There's a line pointing to $vars_config{NonCGIURL}/ultimatebb.php. Change that to point to $vars_config{NonCGIURL}/ultimatebb.cgi
Seventh... turn on the Accelerator, clear the UBB cache, and see if it works. <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" />
We officially do not advise running the Accelerator using the PHP CGI binary, but if that's all your host has, the above procedure SHOULD work.
-- Charles Capps Programmer, Infopop Corporation Please do not contact me privately for support - post on the board or open a support ticket instead!
Okay, Charles, I followed your instructions. The upgrade to 2.1 went perfectly and so moved on to the next steps you gave. I got this on the ubbaccel_test.cgi (nee php):
UBB Accelerator Test Your PHP version is 4.06: OK Your PHP version has zlib: Yes
Your PHP version will have no issues with the UBB Accelerator. The UBB Accelerator will use zlib compressed output.
I edited the ubb_lib.cgi as you instructed. Turned on the accelerator, but this is what I got as a message on the main board page:
Warning: Cannot add header information - headers already sent by (output started at /home/redboot/public_html/cgi-bin/ubb/ultimatebb.cgi:2) in /home/redboot/public_html/cgi-bin/ubb/ultimatebb.cgi on line 490
That's where I have a board set up for testing upgrades and such and I keep it closed except if the real board (same site host provider) goes down. However, the above error repeats itself from "line 490" to "line 494".
So, I took a wrong turn at Albuquerque somewhere. It's too bad, I have to tell you, Charles, that accelerator feature is Batmobile cool <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" /> Maybe if my site host ever goes with PHP 4.06 as its Apache module version, I'll have no problems.
It does show how versatile UBB is, though, since I almost got it to work even with my site host's round about approach to PHP 4. Thanks so much for trying to get it to work. I at least got some PHP experience our of it and that was very cool.
Make sure there's no blank line between the #! and the <?PHP lines. If there is, PHP throws that error.
Okay, allow me an indulgment <gush> Charles, is a genius!</gush> <img src="https://www.ubbcentral.com/boards/images/graemlins/laugh.gif" alt="" />
Seriously, you were right on the money. That got rid of the warnings.
I did a test post and test reply and they went perfect, though it shows it as the cgi-bin/boards/ultimate.cgi (where it always was before turning on the accelerator) as opposed to the cgi-bin/ubb/ultimate.cgi(the php that was saved as cgi as per my site host's instructions). Is that where/how it's supposed to work?
I mean when I'm on the main page, it shows ubb/ultimate.cgi and all the forum topics when I hover the cursor over them also show the ubb/ultimate.cgi, but once I go to them, they show the /boards/ulitmate.cgi. If that's how it's supposed to work, then it's working fine, and I really appreciate the instructions and help!
OKay... time to explain things. <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" />
The UBB can be really intense on the server. To help ease up on the potential load, it saves cached copies of most pages.
The Accelerator cheats. <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" /> It tries to find a cached copy of the page you're trying to get to. If it finds one, it serves it up. If it does NOT find one, it redirects the request to the UBB, which will serve the page AND make a cached copy.
That's why the links are that way. Whenever possible, you'll be directed to the cache. If there's no cached copy (as there wouldn't be after you reply to a topic, or if you post a new topic), you'll get redirected.
-- Charles Capps Programmer, Infopop Corporation Please do not contact me privately for support - post on the board or open a support ticket instead!