> what was the concept of this wiki here? Did it save the files into
> this old /tmp/persistent folder and kept a link to the file name?
> Where may the files have moved to? Are they lost?
I found our old files under /home/old-persistent/freemind .
The interactive ssh access seems to be disabled, so I was not able to
transfer the files into the new location. Also the web server seems not
to see the files under old-persistent as symbolic links to it I have
created does not work for the web-server. I think the best you can do is
writing a support request because of the big amount of the data to be
> PHP sessions needs special cares on SF.net servers as SF.net hosts a
> server farm and not a single server. The required actions are the
> following (replace PROJECT_UNIX_NAME with your project's UNIX name,
> as displayed on your project admin page).
> 1. create a folder to store the sessions in /tmp/persistent. for
> instance, /tmp/persistent/PROJECT_UNIX_NAME/sessions (do not store
> this folder under the project directory, it's not writable by the web
> 2. make sure this folder is writable (by typing chmod a+w
> /tmp/persistent/PROJECT_UNIX_NAME/sessions from a shell)
> 3. tell
> MediaWiki to use this folder to store the sessions, by adding
> session_save_path("/tmp/persistent/PROJECT_UNIX_NAME/sessions/"); at
> the beginning of LocalSettings.php.
> Make sure that session_save_path is added right after:
> ini_set( "include_path", ".:$IP:$IP/includes:$IP/languages" );
> Also make sure that the set path has the begining and ending dir
> slashes present!
This step should be repeatedly done with the new persistent directory
for enabling the write access. But I think we should repair the images
before enabling write access to the wiki.
Last not least consider the new user name and server used for scp access:
> As previously announced to project admins by email, the
> method/hostname/username for accessing file management for project web has
> changed as part of our project web migration to the new Chicago
> Details regarding the migration may be seen at:
> In short: SCP/SFTP/rsync over SSH are viable methods; you'll auth against
> web.sourceforge.net; and your username for auth will be
> USERNAME,PROJECTNAME@... which will provide you
> permissions to PROJECTNAME files.