error messages

I have had to manually re-upload my entire site and now my users are getting this message:

Cannot create session file: efe68d56dcd53f104fb5bdbb9c00eecc-8

If I go to aMember admin, all the users are there and I have also tried rebuilding the DB info, which works but doesn't alter the error I'm getting. The database is fine, and the entire script is there too...so what is the problem?

Is that the only folder or file that needs to be chmoded back to it's original permission-state after a re-copy to the server?

The process of recopying to the server unfortunately does not preserve the original permissions of the files. My concern is the other files that no longer have their original permissions retained as a result of new server migration.

Seems like I recall from the aMember initial installation there was more than just one directory that needed to be made writable during the setup procress. I could be wrong though, but for some reason I am concerned if there is more than just the amember/data/new_rewrite/ directory that would need to have the permissions revisited.

Can you publish the exact directories and permissions needed for each of them as was stated in the install screen?

For example, I just did an install where I copied all the amamber files/directories back to the server. There was another directory in addition to the one you mentioned above that also needed to be chmoded. That directory is amember/data/ to chmod 777.

How many other directories (that I haven't encountered problems with yet) are just waiting to produce a permissions error if one of my surfers uses the system? Would like to know the master list of directories that need special permissions so that I can reset all of them appropriately.

-Fred

Add the following two files to that list of manual chmods if you perform a backup/newly copied installation:
amember/data/.htgroup
amember/data/.htpasswd
(You should chmod them to 666 by the way).

Would really like to know if there is a master list of which files require these certain world writeable permissions. I'm not a fan of randomly encountering these errors and fixing them when they show up. I'd really hate it if a customer encountered these type of errors before I was able to discover them on my own.

-Fred