I've been using version 2.3.1 for quite a while now with great results. I decided to upgrade to the latest version and am having problems with sessions. here's the error i'm getting with the newest version:
Fatal error: Failed to initialize session module in /home/miker/public_dir/phpsecurityadmin/include/config.php on line 50
Warning: Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
the settings in the ini file are correct as sessions are working properly with 2.3.1 and other apps.
there is a /tmp directory with the proper permissions.
we're running php 4.2.2 on openbsd 3.1
has anything changed regarding sessions with the new version.
Thanks for any suggestions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The sessions still work the same as in previous versions. The data is stored using custom session handlers for use with Metabase. All the session data is stored in the database rather than on the file system, and has been that way since about version 1.3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-06-23
Thanks for the quick response. Strange that i'm getting a php error regarding writing to disk when the session data is being stored in the db. Is there any config that needs to be done with metabase. Again, 2.3.1 is working fine for us. Are there any reasons to upgrade regarding security. I know there are a lot of enhancements in 3.0, but if the security is fine with 2.3.1 we could just stay with that.
Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
3.0 was nearly completely re-written. The methods were almost all the same programming, but there were quite a number of smaller bugs regarding access between profiles and access to areas that shouldn't have had access. In short, there were a few smaller security enhancements made since 2.3.1 along with all the added features. Also, there is now more people programming with this project than at that time, so bugs that appear are more likely to get fixed quickly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-06-24
Great, I think we'll stay with 2.3 for now. We've used it on a couple of projects and haven't noticed any bugs as yet. Thanks again for this great system. Here's a link to a demo of a hosted service we're starting for users to manage the content of their sites. This is using 2.3.1 for user management. http://businessbc.ca/site_demo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-07-01
Looks good! I just checked out your demo and it looks cool. Do you think it would help to allow the user to view the site they are editing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-07-01
thanks. yes, if you click on the magnifying glass you can view the page your editing. did you have a different way to view changes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been using version 2.3.1 for quite a while now with great results. I decided to upgrade to the latest version and am having problems with sessions. here's the error i'm getting with the newest version:
Fatal error: Failed to initialize session module in /home/miker/public_dir/phpsecurityadmin/include/config.php on line 50
Warning: Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
the settings in the ini file are correct as sessions are working properly with 2.3.1 and other apps.
there is a /tmp directory with the proper permissions.
we're running php 4.2.2 on openbsd 3.1
has anything changed regarding sessions with the new version.
Thanks for any suggestions.
The sessions still work the same as in previous versions. The data is stored using custom session handlers for use with Metabase. All the session data is stored in the database rather than on the file system, and has been that way since about version 1.3
Thanks for the quick response. Strange that i'm getting a php error regarding writing to disk when the session data is being stored in the db. Is there any config that needs to be done with metabase. Again, 2.3.1 is working fine for us. Are there any reasons to upgrade regarding security. I know there are a lot of enhancements in 3.0, but if the security is fine with 2.3.1 we could just stay with that.
Thanks again.
3.0 was nearly completely re-written. The methods were almost all the same programming, but there were quite a number of smaller bugs regarding access between profiles and access to areas that shouldn't have had access. In short, there were a few smaller security enhancements made since 2.3.1 along with all the added features. Also, there is now more people programming with this project than at that time, so bugs that appear are more likely to get fixed quickly.
Great, I think we'll stay with 2.3 for now. We've used it on a couple of projects and haven't noticed any bugs as yet. Thanks again for this great system. Here's a link to a demo of a hosted service we're starting for users to manage the content of their sites. This is using 2.3.1 for user management.
http://businessbc.ca/site_demo
Looks good! I just checked out your demo and it looks cool. Do you think it would help to allow the user to view the site they are editing?
thanks. yes, if you click on the magnifying glass you can view the page your editing. did you have a different way to view changes.