Unable to login to CMS

[milagro]

I just installed CMS made simple on a Windows XP machine running Apache HTTP Server 2.2.4
and MySQL Server 5.0  I have created a database and the front en is up and running.

The problem is that I cannot login.
I am using the correct password and there are no database connection problems.

Can it be that there is a problem in php.ini that session data is turned off?
If so what line must I activate? If not what can be the problem?

[webform]

Didn't you get an error during installation of CMSMS on the page telling you installation status?

It's sounds like you missing a temp folder in the system to store your sessions - the status page should tell you what path CMSMS was expecting to store it's sessions in!

[scooper]

I only mention it because it's fooled me before - but if you have cookies disabled in your browser then you get stuck at the login screen (with no useful feedback - ought to log that.), so first thing to check is that cookies are being set.

If that's not the problem then you could try enabling URL based session management -  There's more info on doing that over in this thread

s.

[Pierre M.]

Yes, it seems it is about PHP sessions don't work. As said above, the install should warn about this. I will add the working PHP sessions requirement in the wiki :
http://wiki.cmsmadesimple.org/index.php ... quirements

To log in the admin, server side cookie based PHP sessions must be enabled and browser side (at least transient) cookies must be accepted.

I think everyone should avoid URL based session ids because of security because these session ids may be stored in the browser's cache. Transient cookies are a smart extension to the HTTP protocol, URL hacking is a perversion.

Pierre M.

[milagro]

At step 5 it ends at this step.

• Updating hierarchy positions...[done]
• Setting up core events...[done]
• Installing modules...

It always stops at Installing modules...
But the web interface works.

Me be this information can help?






     
        Test
        Result
     

     
        Checking for PHP version 4.2+required test passed
     
     
        Checking for Session Functionsrequired test passed
     
     
        Checking for md5 Functionrequired test passed
     
     
        Checking write permission on C:\www\cms\tmp\cacherequired test passed
     
     
        Checking write permission on C:\www\cms\tmp\templates_crequired test passed
     
     
        Checking write permission on C:\www\cms\config.phprequired test passed
     
     
        Checking for basic XML (expat) supportrequired test passed
     
 
 
 
 
    Recommended settings
     
        Test
        Result
     
     
        Checking file uploads required test passed
     
     
        You have "128M" Checking PHP memory limit (min 8M, recommend 16M)
           
            You may not have enough memory to run CMSMS correctly. If possible, you should try to get your system admin to raise this value to the minimum 8M or great. Proceed with caution.Setting meets or exceeds the recommended threshhold
     
     
        You have "2M" Checking max upload file size (min 2M, recommend 10M)
           
            You probably will not be able to upload any files using any of the included file management functions. Please be aware of this restriction.setting is above the required value, but below the recommended value
     
     
        Checking if C:\www\cms\uploads is writable
           
            If uploads is not writable you can still install the system, but you will not be able to upload files via the Admin Panel.Setting meets or exceeds the recommended threshhold
     
     
        Checking if C:\www\cms\modules is writable
           
            If modules is not writable you can still install the system, but you will not be able to install modules via the Admin Panel.Setting meets or exceeds the recommended threshhold
     
     
        Checking for file_get_contents
           
            The file_get_contents function was added in PHP 4.3 and although a workaround has been added that should allow most functionality that uses this function to work properly in PHP 4.2, it may be advisable to upgrade to PHP 4.3 or greater.Setting meets or exceeds the recommended threshhold
     
     
        Checking if session.save_path is writable
           
            Your session.save_path is "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\php\session". Not having this as writable may make logins to the Admin Panel not work. You may want to look into making this path writable if you have trouble logging into the Admin Panel.setting is above the required value, but below the recommended value
     
     
        Checking if ini_set works
           
            Although the ability to override php ini settings is not mandatory, some addon (optional) functionality uses ini_set to extend timeouts, and allow uploading of larger files, etc. You may have difficulty with some addon functionality without this capability.Setting meets or exceeds the recommended threshhold
     
     
        Checking if sessions are enabled
           
            Although the PHP support for sessions is not mandatory, it is highly recommended. Logins and other things may slow down and you may have difficulty with some addon functionality without this capability.setting is above the required value, but below the recommended value
     
     
        Checking for tokenizer functions
           
            Not having the tokenizer could cause pages to render as purely white. We recommend you have this installed, but your website may work fine without it.Setting meets or exceeds the recommended threshhold
     
     
        Checking for Safe mode
           
            PHP Safe mode could create some problems with uploading files and other functions. It all depends on how strict your server safe mode settings are.Setting meets or exceeds the recommended threshhold
     
 


 

[Pierre M.]

At step 5 it ends at this step.

• Updating hierarchy positions...[done]
• Setting up core events...[done]
• Installing modules...

It always stops at Installing modules...

Strange. I have no clue about this. Unless try to be more patient ?

Checking if session.save_path is writable
Your session.save_path is "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\php\session". Not having this as writable may make logins to the Admin Panel not work. You may want to look into making this path writable if you have trouble logging into the Admin Panel.
setting is above the required value, but below the recommended value

I'm fearing a Windoze pathname problem. Couldn't the path just be C:\mydir\session (all littlecase) and be writeable ?
(BTW, on one of my unix hosting providers, the folder has a final "s" for multiple "sessions")

If you have another PHP app running on the same computer, do sessions work for it ?

Pierre M.

[milagro]

Strange. I have no clue about this. Unless try to be more patient ?

I gues 10 minutes waiting is long enough   

[Dee]

Anything in the server (error)logs?

Regards,
D

[Dee]

     
        Checking if session.save_path is writable
           
            Your session.save_path is "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\php\session". Not having this as writable may make logins to the Admin Panel not work. You may want to look into making this path writable if you have trouble logging into the Admin Panel.setting is above the required value, but below the recommended value
     
     

 

It looks like the webserver cannot write the session data in the configured location. Try setting session.save_path in php.ini.
For example by creating a folder c:\tmp\php and setting it like this in php.ini:

Code: Select all

session.save_path = C:\tmp\php

Regards,
D

[milagro]

Perfect I works. I have set to session.save_path = C:\tmp\php

Fore the future:
How can I make the TMP folder writeable on a Windows XP machine?
And where can I find the error logo from the  Apache Web Serve?

[Pierre M.]

Fore the future:
How can I make the TMP folder writeable on a Windows XP machine?

Sorry, I don't know Windows. Try right clicking on the filename in the file manager.

And where can I find the error logo from the  Apache Web Serve?

If you mean a logo, browse the Apache site.

If you mean the error log, you will find it where you have ordered Apache to put it with the ErrorLog directive. See the Apache doc on AccessLog and ErrorLog.

And have fun trying FreeBSD or Linux

Pierre M.