Bill Myers wrote on Dec 16^th, 2012 at 8:42pm:


ok a error 500 is like the swiss army knife of server error codes when the server give one its like a car owner calling a car mechanic and saying hay my car won't start what is up with it and for obvious reasons the car mechanic can't say over the phone what the problem is and he will have to see it and test some item's.
so back to the error 500 some items it may be.

1.Location
Did you upload your scripts into the right place? This is not as obvious as it may seem. Some servers are configured to run your CGI scripts anywhere. Others will only run it when it is installed in a particular directory. It is not just a matter of creating a "cgi-bin" directory - for example, some hosts configure the server so that it will run scripts only from a particular directory outside the web directory structure (for security reasons). Your web page will still call the script "/cgi-bin/script.pl" but the server maps it to the actual directory. You will have to upload it in the right directory, regardless of what your web page calls it. Find out such information from your web host's documentation.

2.File Upload Mode
Did you upload your Perl script in ASCII mode? Your FTP client may have uploaded the script in binary mode if you did not take any special action. Perl scripts are ASCII files, and since different operating systems have different ways of representing the end of line character (eg Unix uses a line-feed, Windows uses a carriage-return and line-feed pair), it is important that you set the uploading method to ASCII, so that line-end translation is performed.
Re-upload the script, this time making sure that it was uploaded in Text or ASCII mode. Do not use any auto-detection options since the FTP program might assume the extensions you are using for your scripts are for binary files.

3.File Permissions
Did you change the permissions on your script so that it can be executed on your web server? In most cases, simply uploading the Perl script to the server does not necessarily mean that it can run. On Unix web servers (like Linux, BSD, Solaris, etc), it is necessary to change the file permissions to indicate to the operating system that the file may be executed. If you have a Unix FTP client, set the permission ("chmod") of the file to 755, which allows the script to be executed by everybody. If you are using a Windows FTP program, find some way to change the permissions of the file to allow "Read", "Write" and "Execute" permissions for the owner, and "Read" and "Execute" permissions for the group and everyone else.

and so on.

but from

Bill Myers wrote on Dec 16^th, 2012 at 8:42pm:


i have to say look at 1.Location.

hope this is of some help to you  

Bill Myers wrote on Dec 17^th, 2012 at 12:12am:

yes you may have been but when i say
Quote:


i am referring to this part
xnoddyx wrote on Dec 16^th, 2012 at 9:37pm:


1a. so it may just be that your server is setup to run scripts only from your yabb2 directory and thats why setting up a new forum outside of here won't work for you.

2.a but also at the same time it may be that only your yabb2 directory is set to run .cgi and .pl but that your root cgi-bin is only setup to run .cgi.

also as 1a but the root cgi-bin is not the same as your yabb2 /cgi-bin/yabb2 directory as your root cgi-bin may be a maped directory e.g.

say you have /home/a-d/username/host/username/www/public_html
and /home/a-d/username/host/username/www/cgi-bin
and the root ftp login is /home/a-d/username/host/username here you will also have /logs/ and so on, so your server is setup to run .cgi from /home/a-d/username/host/username/www/cgi-bin
but set to run .cgi and .pl from /home/a-d/username/host/username/www/cgi-bin/yabb2
also at the same time it may have a /home/a-d/username/host/cgi-bin and this is set to run .cgi and .pl and is also maped to www.mysite.co/cgi-bin but as the root ftp login is /home/a-d/username/host/username you cannot access this.

i have run a setup similar to this before so you may want to ask your host how your cgi-bin is setup especially if the only .pl scripts that will run are in your /cgi-bin/yabb2 directory 

This Topic was moved from this Topic.

Bill Myers wrote on Dec 17^th, 2012 at 6:11pm:

there you go all fixed for you 

Bill Myers wrote on Dec 17^th, 2012 at 6:11pm:

when you say that what do you mean?.

Bill Myers wrote on Dec 18^th, 2012 at 8:19am:

ah ok i think when you say topic link you mean breadcrumb navigation.

Bill Myers wrote on Dec 18^th, 2012 at 8:19am:

as to the YaBB showcase there is work going on to replace it as it is just a matter of watch this spaces. and when i say work going on i don't mean 9 -5 i mean a mind blowing amount of work going on and that is just scratching the surface.

and this is why we need as much help with bug finding and testing as we can get.

Bill Myers wrote on Dec 18^th, 2012 at 8:19am:


as to the Codex this may or may not be updated or may be replaced agen it is just a matter of watch this spaces.

Bill Myers wrote on Dec 18^th, 2012 at 5:47pm:

sorry but i have to correct you on that, the team that is working now is not the same team as was working then and in the short spaces of time this team has been together there has been a lot of discussion on what if, how, when, some rethinking, and so on at the same time a learning curve for some of us also working out some kinks and all in all i think it has been a good job even with some of the setbacks that there has been.

new team est July 2012 and on.

Bill Myers wrote on Dec 18^th, 2012 at 7:40pm:

yes there are old team members on the new team but their roles and positions have changed Bill Myers wrote on Dec 18^th, 2012 at 7:40pm:

there is no pretend that YaBB is starting up freshly again it is there is alot of code streamlining and cleaning going on this is why the 2.5 code was used for 2.5.2 -> 2.5.4 and so on you can see most of the RoadMap here

although i think there may have been some edits to it,
but even the redundant versions of YaBB like what is running here that some code will be used from will go threw the code streamlining and cleaning and making it more user friendly so by the end of it yabb will be where most of the users of yabb want it to be then next will be streamlining and cleaning and then on the road to the next big need of yabb 

Bill
Have you had any resource allocation problems on your 2.4 forum? I take it the length of time you have been running, it has a fairly large membership?