We are moving a site from a Windows server to a Unix server. After cleaning up all the text case issues that windows did not care about and Unix choked on the forum is operational on the new server. We DID NOT run the UBBThreads install script. We dumped the database from the current server, edited the database name etc., and ran the .sql file on the new server. We copied over the entire web site and the /forums subdirectories because there was a selection of custom code.
The new site does not produce any UBB errors and the database queries and inserts work properly. There are three errors that I can not figure out:
1) On the login screen after entering Username and Password and clicking on the "log in" button the browser shows a 404 page not found error. Click twice on the back button and you are back at the login page showin "not logged in" but you are in fact logged and and clicking on "Forum List" takes you to the forum list. It appears it does the work but fails when it sends the browser the URL for the next page.
2) Upon adding a new post when you click the "Submit" button the work is completed but the browser displays a 404 error. Click the browser re-load button and you are back to the forum list with the post having been made. You are not sent back to the actual post that was just submitted. This also happens with a reply and the fefresh button re-loads the level 0 forum page. Edit a post works just fine where the "Change Post" button takes you to the changed post page and then to the edited post. It seems like a problem with the "submit" button function() and getting "lost" on the page/post it is supposed to return to. I am too new to UBBThreads to know where in the php code the submit button code is located.
3) In control panel "permission checks" shows "FAIL" almost across the board but all the fourm functions are working. Is it possible there is a set of table entries somewhere that still contain the directory, file, and table information from the Windows server and do to the case sensitive issues the permission check is failing because the data used to assemble the permission checks produces a test string that is not correct for the revised Unix environment?
Abbott
