Manual Installation
#1
Guest_amhaskar_*
Posted 08 September 2004 - 02:10 PM
I checked the password and made sure that the MD5 function was submitting the right value for my selected password.
I added a debug line on the accesscontrol.inc.php file to tell me if my session is validated or not (it isn’t).
Also, I added a debug line in login.processor.php to tell me if it successfully set my validated session variable.
I commented out the redirect on the login.processor.php page to make sure that I could see the debug line above.
What I got from this was that before entering my username and password my session was not validated.
After clicking on the login button I was redirected to the login.processor.php page and my session was validated at this point.
However, when I uncomment out the redirect statement, I find that my session has not been validated. As a result I still see the login form.
Anyone there who can help me out? It would greatly be appreciated.
#2
Posted 08 September 2004 - 03:02 PM
#3
Guest_amhaskar_*
Posted 08 September 2004 - 03:17 PM
I really don't have access to the server per se. I was given ftp and db access. I believe it is a unix server not really sure past that. I am attempting to install RC2 (waiting patiently for the final to come). And my need for a manual installation roots from my lack of permission controls.
I have 4 main directories that i can access:
root Owner: rwx Group: r_x Public:
logs Owner: rwx Group: r_x Public:
php-data Owner: rwx Group: rwx Public:
temp Owner: rwx Group: r_x Public:
I somewhat hacked the pages to install the database, and that is what got me to the login page where I did check the MD5 password.
As for the bug report, I don't see this so much as a bug, I'm trying to install the system from an unprescribed way.
Well I hope that this is enough info for someone to help me with. I'm talking to the server admin hoping he can give me a workaround, but anything you guys can offer will be appreciated.
Thanks,
--amhaskar
#4
Posted 08 September 2004 - 03:37 PM
If you have rights to create directories you should be able to run the installer on the server... The installer will prompt for the database information and handle the tables setup, as long as you have manually created your database or have access to one that has been created for you... Have you attempted to do the install in the root directory, the php-data directory, or another directory... :?: My guess is that you need write permissions for your web root, considering that you don't have a public_html or web directory within your directory tree... It appears that your server admin has you locked down a bit too tight...I have 4 main directories that i can access:
root Owner: rwx Group: r_x Public:
logs Owner: rwx Group: r_x Public:
php-data Owner: rwx Group: rwx Public:
temp Owner: rwx Group: r_x Public:
#5
Guest_amhaskar_*
Posted 08 September 2004 - 03:52 PM
I just tried installing from the php-data directory hoping that by some fluke of security I could inherit some write properties, but to no avail.
--amhaskar
#6
Guest_Alex_*
Posted 08 September 2004 - 05:09 PM
Or you could create a new PHP file, and then put the following in it:
This will give you a lot of information about the setup...
#7
Guest_amhaskar_*
Posted 08 September 2004 - 05:27 PM
#8
Guest_amhaskar_*
Posted 08 September 2004 - 06:50 PM
And thanks again to all who have helped me so much.
#9
Guest_Alex_*
Posted 08 September 2004 - 07:00 PM
Next thing to check is to see if sessions are configured properly. Sessions work by saving a file to the server's hard disk somewhere, but that directory must be accesible for PHP. You can see which directory this is by looking at the following settings in phpInfo():
session.save_handler: this will probably say files, which means it saves the session information to files
session.save_path: this is the directory in which it will try to save the session files.
If it can't write to the session.save_path, the sessions won't work.
Check this info with your host
#10
Guest_amhaskar_*
Posted 08 September 2004 - 07:20 PM
You session problem is that they are assuming that the session key is being automatically stored as a cookie on the users browser. This is a false assumption on our configuration, since we have to discourage the use of cookies. Forcing cookies will generate complaints from our userbase, especially if they are required to operate a site.
The alternate to cookie storage is to write the key into each url dynamically.
Any ideas?
#11
Guest_Alex_*
Posted 08 September 2004 - 07:25 PM
Etomite only works if the session id is saved in a cookie.
I suggest you either ask your host to write a htaccess file allowing Etomite to send the cookie headers, or look for alternative hosting.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users










