This is my first post to this mailing list so I hope I am not sending it to the wrong people.
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and added IIS User giving it read permission; unfortunately the site now doesn't work when you try and edit a page and error is returned.
Can someone give me a list of the permissions required for the main Wiki folder; the folder owner is set to the system administrators group, is this a problem?
Thanks for your help Arthur Guy
arthur@astarsolutions.co.uk http://www.astarsolutions.co.uk/ www.astarsolutions.co.uk
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
On 10/06/05, Arthur Guy arthur@astarsolutions.co.uk wrote:
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and added IIS User giving it read permission; unfortunately the site now doesn't work when you try and edit a page and error is returned.
Well, I have no knowledge of IIS and suchlike, so I may not be much help, but: * is there such a thing as an "execute" permission, like there would be on *nix? * the page editting shouldn't cause anything to be written to the file system, only to the MySQL database; the only directory that needs to be writable is the "images" one, IIRC (some versions try to compile the skin template on first run and save that somewhere, but I forget where and recent versions don't bother with this). * the other way editting would be different from viewing is caches of various sorts - are you sure the wiki can actually output fresh content if you by-pass your browser cache etc?
In fact, perhaps the most helpful thing (which people so rarely think to do) would be to say exactly *what* error is returned, in case someone on the list knows what it means, or can deduce.
IIS uses windows file permissions, Full Permission, Modify, List, Read & Exec, Read, and Write. The Wiki Folder has List, Read & Exec and Read selected. I have tried accessing a page I haven't accessed before and it works fine except for the error which only occurs when you save a page or preview a page. The error is a standard http error code, 405 - Resource not allowed.
The only permissions I have changed are for the Wiki Directory I haven't touched the database.
Thanks Arthur Guy
arthur@astarsolutions.co.uk www.astarsolutions.co.uk
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and
added
IIS User giving it read permission; unfortunately the site now doesn't
work
when you try and edit a page and error is returned.
Well, I have no knowledge of IIS and suchlike, so I may not be much help, but: * is there such a thing as an "execute" permission, like there would be on *nix? * the page editting shouldn't cause anything to be written to the file system, only to the MySQL database; the only directory that needs to be writable is the "images" one, IIRC (some versions try to compile the skin template on first run and save that somewhere, but I forget where and recent versions don't bother with this). * the other way editting would be different from viewing is caches of various sorts - are you sure the wiki can actually output fresh content if you by-pass your browser cache etc?
In fact, perhaps the most helpful thing (which people so rarely think to do) would be to say exactly *what* error is returned, in case someone on the list knows what it means, or can deduce.
On 6/10/05, Arthur Guy arthur@astarsolutions.co.uk wrote:
IIS uses windows file permissions, Full Permission, Modify, List, Read & Exec, Read, and Write. The Wiki Folder has List, Read & Exec and Read selected. I have tried accessing a page I haven't accessed before and it works fine except for the error which only occurs when you save a page or preview a page.
Does searching work?
The error is a standard http error code, 405 - Resource not allowed.
What are the URLs of the view and edit pages? Sometimes under Apache, I get 401 Unauthorized when using colons and backslashes in the URL.
According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html, 405 is "Method Not Allowed". This would lead me to wonder if IIS is confusing the POST request with a WebDAV request (though it seems unlikely).
The only permissions I have changed are for the Wiki Directory I haven't touched the database.
Searching does work, the only things that don't appear to work are previewing and saving pages.
I have tried resetting permissions back to everyone with full control and it still doesn't work.
What is different with saving and previewing why would they generate a 405 error.
Thanks Arthur
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and added IIS User giving it read permission; unfortunately the site now
doesn't >work when you try and edit a page and error is returned.
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
I have managed to fix this problem, incase anyone was wondering what was causing it I had recently removed the index.php extention from the local settings file, aparently you can't POST data to a "dir/" you need "dir/index.php" I added the index.php and it worked again. If anyone knows how I can get arround this I would love to here from you.
Arthur
-----Original Message-----
Searching does work, the only things that don't appear to work are previewing and saving pages.
I have tried resetting permissions back to everyone with full control and it still doesn't work.
What is different with saving and previewing why would they generate a 405 error.
Thanks Arthur
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and added IIS User giving it read permission; unfortunately the site now
doesn't >work when you try and edit a page and error is returned.
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
Arthur Guy wrote:
I have managed to fix this problem, incase anyone was wondering what was causing it I had recently removed the index.php extention from the local settings file, aparently you can't POST data to a "dir/" you need "dir/index.php" I added the index.php and it worked again. If anyone knows how I can get arround this I would love to here from you.
Install Apache. ;)
-- brion vibber (brion @ pobox.com)
I believe that this is more of an NT permissions thing than an IIS permissions thing.
For those who have no clue about this, permissions in 2k and XP are based on ACLs. The basic options for permissisions are as follows (each category can be allowed, denied, or neither): * Full Control * Modify * Read & Execute * List Folder Contents * Read * Write * Special Permissions (According to the properties dialog in XP Pro) The full list of perms are: * Full control * Traverse Folder / Execute File * List Folder / Read Data * Read Attributes * Read Extended Attributes * Create Files / Write Data * Create Folders / Append Data * Write Attributes * Write Extended Attributes * Delete Subfolders and Files * Delete * Read Permissions * Change Permissions * Take Ownership
Some of the special NT "security objects" are CREATOR OWNER and CREATOR GROUP. These substitute for the *nix USER and GROUP.
"Everyone" is a special group meaning all users.
(I'm adding this to http://meta.wikimedia.org/wiki/NT_permissions_overview) On 6/10/05, Rowan Collins rowan.collins@gmail.com wrote:
On 10/06/05, Arthur Guy arthur@astarsolutions.co.uk wrote:
I have got Media Wiki installed and working on an IIS server, today I decided to take a look at the file permissions for the instillation and I found that the everyone group had full permission, I removed this and added IIS User giving it read permission; unfortunately the site now doesn't work when you try and edit a page and error is returned.
Try giving the IIS user Full Control and everyone Read and List.
What error?
Well, I have no knowledge of IIS and suchlike, so I may not be much help, but:
- is there such a thing as an "execute" permission, like there would be on *nix?
Kinda, but I am unsure of how exactly it difers from just Read.
- the page editting shouldn't cause anything to be written to the file
system, only to the MySQL database; the only directory that needs to be writable is the "images" one, IIRC (some versions try to compile the skin template on first run and save that somewhere, but I forget where and recent versions don't bother with this).
I'm assuming that the MySQL server runs as a different user from IIS.
The PHPTAL skin compilation is only done in v1.3. It compiles to some odd temporary directory. I think this would happen on first view.
- the other way editting would be different from viewing is caches of
various sorts - are you sure the wiki can actually output fresh content if you by-pass your browser cache etc?
Especially if you are using an SHM (like Turck or eAccelerator). Otherwise, I think caching is done through MySQL.
In fact, perhaps the most helpful thing (which people so rarely think to do) would be to say exactly *what* error is returned, in case someone on the list knows what it means, or can deduce.
Yes! What's the error? It's akin to telling your mechanic, "My car doesn't work. How do I fix it?"
mediawiki-l@lists.wikimedia.org