OpenPHPnuke International Support

Author	linuxbob
Date	2004-08-26 21:03
Posts:	Quote: 2004-08-26 20:43 manne wrote: Some hints for easier testing: When you are testing with OPN you can use the Core Download....Much smaller than the Full and not so much uploadtime. After playing around it' very easy to install the whole modules (or to do the Full Install if you solved the first problems) That's because OPN is fully modular, you can install an deinstall each module from the Modules Package for it's own. It's not necessary to upload all the files before each install. Before doing a fresh install, check the directory html/cache : There you find a file install.lock. Delete this file. This file prevents you from accidentially make a new install. Also delete the subdirectories in html/cache/. These subdirectories are made by OPN while installing. That's all. manne But you must empty the database for OPN before a new install. Those are fine tips for testing, but they don't point me in a direction for solving the problem. File size and upload time are not my concerns. I have two windows open. An ssh connection to provide root access on the web server and a browser window to access the application. I have the opn files unpacked in a personal subdirectory and can copy (cp -r) those files to the web server directory in seconds. My unpacked location is ~/opn2/. I copy everything from ~/opn2/html (including all subdirs) to /srv/www/htdocs/opn. I change the permissions on ./cache to 777 as mentioned in docs, I touch mainfile.php and set it also to 777, then I swap to the browser and point to http://core104/opn/install.php. Each time I do this procedure I drop the database and re-create it. I'd like to know what module in the code, I can troubleshoot to find out what happens at login. In all my attempts, not a single cookie has been generated for the browser. Nor do any subdirectories get created in opn/cache. Thanks for the tip, I can save a little time by skipping the delete and re-copy of the filesystem by removing the install.lock file. Now the login problem needs to be solved.