phpwcms Support Forum

Try turning on all notices, warnings, and errors in "php.ini" to see if any "descriptive" messages occur

Maybe resetting the webmaster account to user:webmaster password:phpwcms (as described here), to see if that user account get redirected:
http://www.phpwcms.de/forum/viewtopic.p ... b3be#67497

These are for checking your sessions:
http://www.phpwcms.de/forum/viewtopic.p ... 4158#67324

Don't overlook firewall and antivirus settings.

1. Dont create the phpwcms mysql database yourself by hand!
2. Instead let phpwcms create the db by starting the setup procedure
(http://www.phpwcms-docu.de/installation_en.phtml)
3. Then backup your old database (which is on localhost??) into an .sql file, be sure to make the .sql file compatible with the destiny database.
4. Then let the .sql file not create the database tables, cause phpwcms did it. So edit the sql file accordingly.
5. Then insert the sql file in the phpwcms database at http://www.illinois.....org.

good luck!!

Regards, groeten,
vuurvos

Ok, posted the session files and the scripts do not appear to be working. It appears to be a session issue, right?

http://www.illinoislegalaidonline.org/session.php
http://www.illinoislegalaidonline.org/s ... ession.php

I don't know if this has something to do with it but there was a maintenance scheduled for one of our servers around the time the issue started to appear. However, I was able to login into the site the day after.

Due to availability difficulties with RedHat Network (source for the updates), we were unable to complete the planned patch maintenance for Tuesday July 18, 2006. The maintenance has been rescheduled for tonight, Wednesday July 19, 2006. We will install all of the security updates currently available for the server where your website(s) and/or database(s) reside, as well as any patches the machine requires.

This maintenance will occur between 02:00 AM and 06:00 AM EDT and the estimated downtime is between 15 - 30 minutes. All of the patches that will be deployed have gone through our quality assurance process and are currently running with no incident on our test servers.

Also, here is a screensnap that shows the login screen after I attempt to login (plus the phpwcms_userlog screen)

Check that the session folder specified in "php.ini" exists and has free space!

Some OTHER typical issues with session:

-Insufficient free space in the server's session file for the user.
-Various settings in httpd.conf, php.ini, .htaccess files can affect sessions differently when PHP is enabled as ISAPI module, instead of CGI.
-PHP enabled as CGI treats some header directives differently.
-Servers using load balancing may write session data in /tmp dir of A, but when a new page is requested it is being served from B.
-ISP/Webhost issues with server caching proxy/webcache "schemes".
-Browser settings/plugins/addons (also unrecognized user_agent string) and/or local "security" applications (virus/firewall).

Check that the session folder specified in "php.ini" exists and has free space!

I just found the php.ini file on my FTP. What should I look for?

I conclude that there isn't a database problem anymore?

What the php.ini is concerned, you can add entries by adding lines (with php_flag) in the .htaccess, like this:

php_flag magic_quotes_gpc Off
php_flag register_globals Off

It turns out I can't manipulate the php.ini file. However, I did discover that:
This needs to be set to "on" for the login to work correctly, right?

After investigating the CPanel of the host we're using, I ran across the ability to turn on the PHP display errors. When logging into the CMS, this is what was returned

Warning: session_start(): open(path, O_RDWR) failed: Permission denied (13) in /vservers/illinbk3dcd3d/htdocs/login.php on line 24

UPDATE
Problem fixed, it turns out that during a recent update/upgrade on the servers, the permissions were reset on the session folder to readable only.

Thanks to everyone that offered help. I really appreciate it.

Mike