Last modified: 2010-05-15 15:38:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4263 - Users who are logged in can't edit pages.
Users who are logged in can't edit pages.
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.5.x
PC Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://yarse.sourceforge.net/wiki/ind...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-13 02:35 UTC by Bradley Arsenault
Modified: 2010-05-15 15:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bradley Arsenault 2005-12-13 02:35:47 UTC
It seems as though users who have logged in can't edit webpages, where as
anonymous users can. When I log in, all is normal. I can select edit for a
webpage, make my neccecary changes, but when I hit Save, it will redirect me to
the page i would get if i hit preview. Again, and again and again. I'm using
firefox 1.0.7, I've tried turning off the cache, it doens't help. The problem
persists after me trying my orginal user, a new user I made, and an alternate
person on IRC did the same thign with the same problem persisting.

My wiki is installed following the instructions on
http://meta.wikimedia.org/wiki/Running_MediaWiki_on_Sourceforge.net. The
database account on sourceforge was originally the admin account, but I recently
changed that to simply the read/write account (in LocalSettings.php, $wxDBuser)
to see if it would help with the problem, but to no effect.

I have also noticed that my user preferences won't change, no matter how many
timees i try to change them and hit save.
Comment 1 Ævar Arnfjörð Bjarmason 2005-12-13 02:38:26 UTC
Try to reproduce this problem on a box that isn't hosted on sourceforge
Comment 2 Brion Vibber 2005-12-13 04:41:03 UTC
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.
Comment 3 Rob Church 2005-12-13 12:29:11 UTC
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?
Comment 4 Bradley Arsenault 2005-12-14 01:01:16 UTC
It is an accident, I must have picked the wrong version, I just changed it.
Comment 5 Bradley Arsenault 2005-12-14 01:01:39 UTC
It is an accident, I must have picked the wrong version, I just changed it.
Comment 6 Bradley Arsenault 2005-12-14 01:04:17 UTC
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.
Comment 7 Rob Church 2005-12-14 01:10:46 UTC
(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.
Comment 8 Bradley Arsenault 2005-12-14 01:25:15 UTC
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.
Comment 9 Bradley Arsenault 2005-12-14 01:28:09 UTC
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.
Comment 10 Rob Church 2005-12-15 19:46:08 UTC
(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.
Comment 11 pao 2005-12-19 20:24:42 UTC
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.
Comment 12 Brion Vibber 2005-12-19 20:39:34 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links