avarab wrote:

Try to reproduce this problem on a box that isn't hosted on sourceforge

Double-check your session directory. Confirm that it is writable, keeping in
mind that most files on sourceforge.net are no longer writable from web
scripts.

robchur wrote:

SourceForge's server farms don't like sessions, or writing to files, or anything
marginally useful for a web application. Incidentally, the instructions you
followed weren't official, and were written taking the current version of the
software at that time into account. The chances they're out of date or no longer
valid are high, given that MediaWiki has expanded, and SourceForge have made
several administrative changes as of late.

Also; you selected version 1.5rc4. Why are you using a release candidate when we
have release versions (1.5.3) available?

genixpro wrote:

It is an accident, I must have picked the wrong version, I just changed it.

genixpro wrote:

It is an accident, I must have picked the wrong version, I just changed it.

genixpro wrote:

I'm not sure the wiki should behave in this manner even if it is a sessions
problem, I mean the problem and what seems like the solution are unrelated, I
get no errors or anything.

robchur wrote:

(In reply to comment #6)

I'm not sure the wiki should behave in this manner even if it is a sessions
problem, I mean the problem and what seems like the solution are unrelated, I
get no errors or anything.

MediaWiki uses sessions to save something called an edit token. Hence, it uses
sessions to save. Hence, a problem with sessions will cause a problem with editing.

genixpro wrote:

I seem to have found a problem, I configured LocalSettings.php to point to thw
wrong sessions directory (I mispelt persistent). However, even after changing
the directory to the correct place, the problem persists. If there is some sort
of a delay or configuration cache, then its a non issue.

genixpro wrote:

Ok, i have solved a problem, it was a twofold problem, however the new
permission settings on the file are loose. I will remain by the idea that
mediawiki should give some kind of a warning when its sessions directory isn't
writeable or is non existent.

robchur wrote:

(In reply to comment #9)

Ok, i have solved a problem, it was a twofold problem, however the new
permission settings on the file are loose. I will remain by the idea that
mediawiki should give some kind of a warning when its sessions directory isn't
writeable or is non existent.

Resolving fixed. File that as a separate feature request if so desired.

pao wrote:

I'm following this bug, because I still have it!
When a logged user try to save a page, he gets this message:
<<<<<<<
A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

(SQL query hidden)

from within function "Block::load". MySQL returned error "1: Can't create/write
to file '=c:\programmi\xampp\tmp\#sql_970_0.MYI' (Errcode: 22) (localhost)".

the error is generated by the function sendCacheControl (in the file
includes\OutputPages.php) when this test fails:

if( !$this->uncacheableBecauseRequestvars() && $this->mEnableClientCache )

my folder c:\programmi\xampp\tmp\ exists and it is writeble.

Please don't post on unrelated bugs. Please see http://dev.mysql.com/ for
documentation on MySQL, or whatever support forums for XAMPP there are for your
problems with it.