Project:Support desk

From MediaWiki.org
(Redirected from Support desk)
Jump to: navigation, search
vde   This page is for questions relating to the MediaWiki software.

Welcome to MediaWiki.org's Support desk, the central on-wiki place to ask MediaWiki questions!

The greater purpose of this page is to make our Manual and other available help so good that you do not have to come here to ask questions, or making them easier to find.

There are other ways for of communication as well (IRC, mailing lists etc.). Read more here.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using:
    • MediaWiki (reported by your wiki's Special:Version page)
    • PHP (likewise)
    • Database (likewise, e.g. MySQL 5.5)
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new discussion".

Archiving topics

Topics are automatically archived when they have been inactive for three weeks. If a question you have asked is approaching this limit and still has not been answered, please 'bump' it to prevent it being archived. However do not 'bump' for other reasons.

Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

Drop down user menu

Hi how can I create drop down user menu for example please visit http://www.pidgi.net/wiki/Main_Page and lcick guest I would like it to be like that but I have the codes for it but it breakes javascript for everything.

Paladox2017 (talk)20:22, 23 July 2014

Upload File not working with Oracle

After we try to upload an image, mediawiki says that the image doesn't exists (Spanish message: "No existe ningún archivo con este nombre, pero puedes subirlo. "), but we can find the file in the server file system.

The file list special page, does not shows any results. The IMAGE table is empty. The UPLOADSTASH table has several rows like this:

62 1 12gj3imwf6ns.ik9b4y.1.png /tmp/localcopy_c7c5f0e99b18-1.png mwrepo://local/temp/5/59/20140723151607!localcopy_c7c5f0e99b18-1.png file 23/07/2014 03:16:07,000000000 PM -03:00 finished 10424 80i9wcke3o13ipvgr1hhgctj3ilflxk image/png BITMAP 687 327 8 (BLOB)

Another info MediaWiki 1.22.3 PHP 5.3.2-1ubuntu4.23 (apache2handler) Oracle 11.2.0.3.0

200.49.85.19515:47, 23 July 2014

The message you get is MediaWiki:filepage-nofile-link: No file by this name exists, but you can [$1 upload it].

Well, if the image table is empty, then the error is correct: Your MediaWiki installation doesn't have any file uploaded yet.

The Manual:uploadstash table is a temporary table to track unfinished uploads (those uploads that threw a warning to the user, so they're still on hold).

Try uploading the file again, and if it fails, you should post here what error message are you getting on upload.

Ciencia Al Poder (talk)17:23, 23 July 2014

I've tried to upload the file several times (also different files), no error message after that, just the message "No file by this name exists, but you can [$1 upload it].".
As I said, I can find the file in the file system (i.e images/2/22/Screenshot_merge.png), so the file gets uploaded after all, but mediawiki has not register of that happening.
In apache error.log I can see somthing like:

[Wed Jul 23 12:35:37 2014] [error] [client 192.168.215.31] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1146, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png
[Wed Jul 23 12:35:37 2014] [error] [client 192.168.215.31] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png
[Wed Jul 23 12:35:37 2014] [error] [client 192.168.215.31] PHP Warning:  substr() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png
[Wed Jul 23 12:35:38 2014] [error] [client 192.168.215.31] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1146, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png
[Wed Jul 23 12:35:38 2014] [error] [client 192.168.215.31] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png
[Wed Jul 23 12:35:38 2014] [error] [client 192.168.215.31] PHP Warning:  substr() expects parameter 1 to be string, object given in /var/www/mediawiki/includes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php?title=Especial:SubirArchivo&wpDestFile=Screenshot_merge.png

But I also have errors like this on pages that are working well:

[Mon Jul 21 10:40:52 2014] [error] [client 192.168.215.35] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/in
cludes/db/DatabaseOracle.php on line 1146, referer: http://192.168.215.204/mediawiki/index.php/Servidores_de_Integraci%C3%B3n
[Mon Jul 21 10:40:52 2014] [error] [client 192.168.215.35] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/in
cludes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php/Servidores_de_Integraci%C3%B3n
[Mon Jul 21 10:40:52 2014] [error] [client 192.168.215.35] PHP Warning:  substr() expects parameter 1 to be string, object given in /var/www/mediawiki/in
cludes/db/DatabaseOracle.php on line 1142, referer: http://192.168.215.204/mediawiki/index.php/Servidores_de_Integraci%C3%B3n
[Mon Jul 21 10:40:53 2014] [error] [client 192.168.215.35] PHP Warning:  strpos() expects parameter 1 to be string, object given in /var/www/mediawiki/in
cludes/db/DatabaseOracle.php on line 1146, referer: http://192.168.215.204/mediawiki/index.php/Servidores_de_Integraci%C3%B3n
200.49.85.19519:43, 23 July 2014
 
 

Is it possible to set a separate url for thumbs images?

I know $wgUploadPath set the URL of the upload directory. However, I would like to set another sub domain for thumbs images. Is this possible?

Zoglun (talk)18:04, 23 July 2014

Sure :) You can use $wgUploadStashScalerBaseUrl to define a remote base for thumbnailing. Here the description of this value from DefaultSettings.php:

To enable remote on-demand scaling, set this to the thumbnail base URL. Full thumbnail URL will be like $wgUploadStashScalerBaseUrl/e/e6/Foo.jpg/123px-Foo.jpg where 'e6' are the first two characters of the MD5 hash of the file name. If $wgUploadStashScalerBaseUrl is set to false, thumbs are rendered locally as needed.

Florianschmidtwelzow (talk)18:45, 23 July 2014
 
Flag of Japan

Please stop the Thumbnail style update immediately. It is unable to deal with images, that consist predominantly of white space without an outer border, such as the Flag of Japan. --H-stt (talk) 15:01, 23 July 2014 (UTC)

H-stt (talk)15:01, 23 July 2014

Why? I don't see any problem with the file in your post. The thumbnail style update was long wanted and is great.

88.130.70.11415:11, 23 July 2014

You don't see any problems? Well, imagine this image in an article under the new thumbnail style: On a white page, without a border and without a shaded frame. See the issue?

H-stt (talk)16:17, 23 July 2014

Either you say you want a frame, then take a version like "thumb", which has a frame or you say you want no frame like with "frameless", then take one without frame. I still don't see the problem. Or do you want a shadow around the image - also when it's not framed?

Image without frame:

Image intendedly without frame

88.130.70.11418:03, 23 July 2014

I now had a look at a number of image-related use-cases and I think I can now guess, what you mean:

Do you want to have a clearer separation between an image and the surrounding text? Is that the problem? When I see Hywiki-moon-after.png, I must say that I find it rather confusing that the middle image (earth on the axis, with moon) is not separated from the text more clearly. Where does the article text end? Does that half sentence still belong to the article text or should it be part of the image? This separation was much more clear when there still were frames by default.

Is that what you mean? That the default style now does no longer have a frame?

88.130.70.11418:08, 23 July 2014
 
 
 
 

Scrolling with header

Hi how can I make the header top bar when you scroll it will scroll with you like winter because I am updating a skin that someone else created and I would like to add when scrolling it would follow.

94.197.122.8112:27, 23 July 2014

The header of the skins I know will scroll with automatically. If what you actually mean is be fixed at the same position of the screen, CSS, especially position: fixed; will be the way to go.

88.130.70.11412:52, 23 July 2014
Edited by another user.
Last edit: 17:26, 23 July 2014

Hi thanks but that does keeps it up there it doesent move when scrolled and it also removes scroll

div#content {
	margin-left: 178px;
	padding-bottom: 1em;
	padding-top:0em;
	/* @embed */
	background-image: url(images/border.png);
	background-position: top left;
	background-repeat: repeat-y;
	background-color: white;
	color: black;
	direction: ltr;
	height:auto;
	position:absolute;
	bottom:0px;
	top:40px;
	overflow:auto;
	-webkit-overflow-scrolling: touch;
}

I would like to change the above so that it does the top bar instead of the side bar and any things else just the top bar. like winter.

92.40.250.8716:38, 23 July 2014
 
 

Requesting visitor stats for help pages

Hi,

We would like to know how many users are visiting ULS help pages namely Help:Extension:UniversalLanguageSelector/Input methods/mr-inscript and Help:Extension:UniversalLanguageSelector/Input methods/mr-transliteration

Thanks and regards

Mahitgar (talk)16:08, 23 July 2014

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted [Resolved]

MediaWiki 1.15.4
PHP 5.3.0 (apache2handler)
MySQL 5.1.36-community-log

I am hoping that someone may be able to assist me. I have been using the ‘SiteGround’ method of backing-up my wiki, unfortunately, there is a problem with the memory size shown in apache faults:

Tue May 24 10:09:35 2011] [error] [client 127.0.0.1] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 128368641 bytes) in C:\\wamp\\apps\\phpmyadmin3.2.0.1\\export.php on line 190, referer: http://localhost/phpmyadmin/db_export.php?db=mediawiki&server....

I have checked line 190 of export.php as below, which does not make any sense to me at all!

189 // We export as file - output normally

190 echo $line;

191 }

Kind regards

Ron Barker10:23, 30 May 2011

I have just made things worse. I did some research and came up with changing the memory limit in php.ini from 128M to 150M and now I am unable to export anything, even after changing back to 128M

I would be grateful if anyone can help.

Ron Barker17:32, 30 May 2011
 

Unchecked memory use is probably a given for that method. Increase the memory limit or find a better method (which might involve finding a better host).

Emufarmers(T|C)02:40, 31 May 2011

Thank you for your response. I have tried increasing the memory to no avail. I am using media wiki on my pc so I cannot change to a better host. Regards

Ron Barker08:53, 1 June 2011

If increasing the memory limit isn't working, you're probably doing it incorrectly.

Since you're on your own machine, though, you don't actually have to use phpMyAdmin for your export.

Emufarmers(T|C)23:52, 1 June 2011

I think that you are probably correct in that I must be doing something incorrectly.

Many thanks for directing me to the discussion page which led me to:

http://www.mediawiki.org/wiki/Manual:Errors_and_Symptoms#Fatal_error:_Allowed_memory_size_of_nnnnnnn_bytes_exhausted_.28tried_to_allocate_nnnnnnnn_bytes.29

However, the information did not take me any further. One problem I have had is determining which php.ini should be edited! There are two php.ini files one under the PHP directory and the other under Apache/bin. Of course, there is another php.ini file that can be accessed from the taskbar. RJ45 Technologies was of some assistance but following their instructions did not help:

http://www.rj45tech.com/increasing_php_memory_limit_and_file_upload_size_wamp

I am not alone. There are many more people with the same problem as a quick Google of '134217728 bytes exhausted' shows.

I have looked at the mediawiki backup page. The instructions are fine if you know what they mean. You need to have more than a basic understanding of mediawiki to be able to follow the instructions. I could get into more trouble than I am already in if I tried to follow the instructions. To be honest I would not know where to start.

http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki

Many thanks though for at least responding.

Ron Barker07:31, 2 June 2011

I appear to have resolved the issue. I really do not know what I was doing wrong but by changing the memory limit (using -1) in C:\Wamp\bin\apache2.2.11\bin\php.ini to unlimited the backup worked.

memory_limit = -1

Many thanks for responding which pushed me to try to solve the problem

Ron Barker09:20, 2 June 2011
 
 
 
 
 

Disable automatic link parsing

I'm using mediawiki 1.23.1

By default all keywords that link to an existing subsite are automatically parsed to a link.

I know you can disable it for a specific text-area with the <nowiki></nowiki> command, however that conflicts with links in the sidebar.

I have a sub-page called "Quaternion" and want to add a link to that subpage in the sidebar.

If I add "** Quaternion|Quaternion" to the sidebar edit-page, it automatically parses it into "** [[Quaternion]]|[[Quaternion]]", which invalidates both the link and the text:

http://puu.sh/anCeQ/fc8b6d1a45.png


If I try to disable the link using "** <nowiki>Quaternion</nowiki>|<nowiki>Quaternion</nowiki>", the result is this:

http://puu.sh/anCcf/b41ae3d3cf.png


Again, with an invalid link.

What can I do to prevent this behavior?

Silverlan (talk)12:15, 23 July 2014

Hello!

Maybe i missed a change, but i would say, that MediaWiki doesn't parse any strings as link automatically out of the box. That means, with a blank MediaWiki Installation without anay extensions you can save ** Quaternion|Quaternion without any problems and link parsing in MediaWiki:Sidebar. If this isn't so, then maybe an extension parses keywords to Links. Can you give a link to your Wiki or a list of Extensions you have installed?

Florianschmidtwelzow (talk)12:29, 23 July 2014

My mistake, I still had the "LinkTitles" extension installed which ended up in my wiki by mistake - I removed it and it's working fine now. Thanks for the tip.

Silverlan (talk)13:27, 23 July 2014
 
 

[RESOLVED] How can I delete pages?

I have made my user:

Member of: Bureaucrats and Administrators

however I still can not delete pages. I been checking all over the web, but sounds like I should have the ability to, but do not have the ability to. Can anyone tell me what I am missing?

76.90.58.5014:18, 19 July 2014

Hi!

Basically administrators should be able to delete pages. What is the URL of your wiki?

88.130.85.9814:26, 19 July 2014

it is private and password protected and I can not allow access to it because has sensitive work info, but some of the old pages our out dated company polices and info. That is why I need to delete the pages. From my user page:

Ryan (bureaucrat, administrator) (Created on 11 December 2012 at 15:13)

Edit user groups Changing user rights of user Ryan (Talk | contribs | block) You may alter the groups this user is in: A checked box means the user is in that group. An unchecked box means the user is not in that group. A * indicates that you cannot remove the group once you have added it, or vice versa. Member of: Bureaucrats and Administrators Implicit member of: Autoconfirmed users Groups you can change

bot
X administrator
X bureaucrat
76.90.58.5014:34, 19 July 2014

Do I need to have the bot checked too?

76.90.58.5014:35, 19 July 2014

Is this something I can setup when I start a fresh install? I just started another install on another site so I do not break my current one, Once I have that up I can pass along if that would help.

76.90.58.5014:52, 19 July 2014
 

Hello! If you are an administrator and not able to delete pages, then check the LocalSettings.php for wgGroupPermissions['sysop']['delete'] please. Is this on true or false (or doesn't exist?)?

Do you see the "delete" link or not (it's in the menu behind the "arrow")? Which MW Version you have installed?

Florianschmidtwelzow (talk)15:20, 19 July 2014

I checked the local settings and was not there. Was not Permissions listed in the file at all, and my version are as follows:

Installed software

Product Version MediaWiki 1.19.11 PHP 5.3.27 (cgi-fcgi) MySQL 5.1.39-log

76.90.58.5019:37, 19 July 2014
 
 
 
 
 

Pagecontent Help

n mediawiki 1.21, i want to append some text in wikitag format at prefix and postfix of the original content(page_content), on which file and where i want to make change regarding this. Please guide me.


Mediawiki 1.21 Postgresql 9.2

125.19.34.8612:36, 17 July 2014

Hello,

unhappily i'm not really sure, what you want to do :) Do you want to add some text before and after each content page (but not on Special pages or Category pages?)? If so, you can use templates to add before and after every page, or edit the skin files, or using hooks to add the content (so you can use this one to add content after the content e.g. https://www.mediawiki.org/wiki/Manual:Hooks/SkinAfterContent).

Hope that helps you :)

Florianschmidtwelzow (talk)19:18, 17 July 2014

Florian's ideas are good, except the one to edit the skin files. If you are using one of the MediaWiki default skins (or a skin, which you do not maintain yourself), you should not edit its files as your changes will e.g. be overwritten after an update.

88.130.87.11320:16, 17 July 2014

Yeah, right :) Sorry, sometimes i forget, that i'm using a custom skin :) If you created itself there are much more posibillities (and more problems you have to solve too :P)

Florianschmidtwelzow (talk)07:10, 18 July 2014
 
Edited by another user.
Last edit: 07:09, 18 July 2014

@Florianschmidtwelzow Thanx for your response.Actually in mediawiki 1.12 what we did, we created one customized module like page_precontent and page_postcontent two column we added in page table, by using our module user can add what should print at the beginning of the content and what should print at end of the content can able to add and modify. For ex consider "Test_Page" is containing original content like "Hi This is test Page", by using our customized extension user have to enter only the title of the page then two text area user can able to see ,like precontent and post content, if user is adding some text in precontent text area like "''This this before text''" and in post content text area like "'''This is end of the content'''", if you load the page "Test_Page" it will show like

This this before text Hi This is test Page This is end of the content


In mediawiki 1.12 we customized the article.php like below in custom code you can see.,

public function outputWikiText( $text, $cache = true ) {
		global $wgParser, $wgUser, $wgOut, $wgEnableParserCache;
 
		$popts = $wgOut->parserOptions();
		$popts->setTidy(true);
		$popts->enableLimitReport();
 
		/**************** CUSTOME CODE **************************/
 
                $this->mPreContent = Title::getPreContent($this->mTitle);
                $this->mPostContent= Title::getPostContent($this->mTitle);
                $text = $this->mPreContent.$text.$this->mPostContent;
 
		/********************************************************

In mediawiki 1.21 im not able to find where to make this change.

59.163.27.1105:47, 18 July 2014

Like 88.130.87.113 said: Never change skin files, the same is for all other files provided by core, see for this: Do not hack MediaWiki core

Better is to do this with an extension, if possible.

But like i said: I really don't know, what you want to do? You want to save a pre and post content into the database for each text? Then maybe it's really better to instruct your users that they can add this content into the "normal" textfield for content of page?!

Florianschmidtwelzow (talk)07:20, 18 July 2014

@Florianschmidtwelzow it is not possible to instruct the user.already in production if i want to change more than 2000 pages i want to modify it, So i want to customize mediawiki core only, so guide me on which file i want to make change yaar, It is very difficult. Developing extension also right now it is not possible, i want to complete this task within 2 days , so please guide.

125.19.34.8609:17, 18 July 2014

Sorry for the direct answer: I think you go a totally false way. This what we discuss here is one of the reasons why it's never an alternative to hack the core: At some point you don't know, what to do (if you are not in the actual development process or are the Wiki administrator, not the developer). I will give you a possible solution for your problem next to this text, but please (really!) notice, that it will comes the point, where this solution again won't work. And in my opinion, that can't be the right approach.

So, to solve this problem (I have still the opinion that you shouldn't do this) you can change inclueds/page/Article.php (in MW1.24wmf11+) or includes/Article.php (in MW1.24wmf11 and under): Find function getContentObject() (somewhere around line 280 or 250):
Add following before
fProfileOut( __METHOD__ );
return $content;

$text = ContentHandler::getContentText( $content );
$newText = 'preContent' . $text . 'postContent';
$content = ContentHandler::makeContent( $newText, $this->getTitle() );

Like ever: use it for your own risk.

Florianschmidtwelzow (talk)20:45, 19 July 2014
 
 
 
 
 

Where to change the powered by MediaWiki link?

The bottom right "powered by MediaWiki" photo was changed by myself, yet when I click on it, it takes me to www.mediawiki.org

Does anyone please know what file contains "http://www.mediawiki.org" on that bottom right photo so I can change it to point to my website?

Thank you:)

Tonywiki (talk)07:06, 20 July 2014

Hello! You can use this Hook to do this. Just add this code to your LocalSettings.php:

$wgHooks['SkinGetPoweredBy'][] = 'onSkinGetPoweredBy';
function onSkinGetPoweredBy( &$text, $skin ) {
   $url = '<url-to-the-new-poweredby-image>';
   $text = '<a href="<the-link-to-your-new-poweredby-location>"><img src="' . $url
       . '" height="31" width="88" alt="Powered by MediaWiki" /></a>';
}
Florianschmidtwelzow (talk)13:33, 20 July 2014
 

Don't expect us to give you support for your wiki if it doesn't contain the MediaWiki logo :)

Ciencia Al Poder (talk)13:39, 22 July 2014
 

MediaWiki installation and Short URLs

I have tried everything that that anyone has told me to do. I just can't get make it so that the url just reads "athena.my-domain.local". (Athena is my wiki's name). I added the proper DNS settings in my Domain Controller as well so that the Server itself can be resolved by name.

Maybe I did this all wrong from the beginning so if anyone can clarify for me if what I did was right or wrong it would be great:

When I downloaded Mediawiki, the .tar.gz file was placed in the directory /home/mhtadmin/mediawiki-1.23.1.tar.gz then I decompressed the file and it remained in the same directory but was then called "mediawiki-1.23.1" then I renamed the file to just "mediawiki" and moved it (and all of its contents) to /var/www/ because I thought that's what I was supposed to do since /var/www/ is where index.html is. The directory is now /var/www/mediawiki. I then moved the LocalSettings.php into /mediawiki where it needed to be. At this point I was able to access my wiki page but now the URL reads "http://ip-address/mediawiki/index.php or I can browse to it by typing in "athena.my-domain.local/mediawiki/index.php" but when I log in it goes back to the IP address URL.

The directions on the mediawiki website on how to create a Short URL for Apache talk about "/w" and "/wiki" directories, I do not have these. This is frustrating me to say the least.

Can anyone help me? Please don't be vague in descriptions, be as specific and detailed as possible. I just wanna get this thing fully working :?(

Gti guy25 (talk)18:47, 11 July 2014

Your steps are not entirely clear to me. (I hope you moved LocalSettings.php into /var/www/mediawiki instead of just /mediawiki and that you forgot to provide a full path only? I'm not sure whic file you renamed to "mediawiki" and hope that you meant a folder instead?) Which "directions on the mediawiki website" do you refer to? Clear links welcome.

In any case: Did you already make some edits to Apache's httpd.conf file?

AKlapper (WMF) (talk)20:52, 12 July 2014

Can somebody please put this back with Thread:Project:Support desk/MediaWiki installation and Short URLs, which it was apparently a reply to? I looked all over but couldn't find out how to undo the thread splitting by what is apparently a vandal (or spammer -- he retitled this thread with a website he seems to be promoting).

Edit: Never mind -- got it fixed. Should have been obvious to begin with. 23:08, 12 July 2014 (UTC)

Cathfolant (talk)22:05, 12 July 2014
 

AKlapper,

I renamed mediawiki.1.23.1 (which is the folder name after downloading the tar.gz from mediawiki website) to "mediawiki", and yes I moved localsettings.php to the proper folder, my mistake I was typing while frustrated. But I moved my "Mediawiki" folder to /etc/. It does not matter where you place it, as long as you change where Apache points to. Having said that, the httpd.conf file exists but is a completely blank file. Apache.conf is the file I have been told is what needs editing. So to answer your question, no I have not made any edits to httpd.conf because the directions and everything else I have read specifically state that httpd.conf is no longer used with Apache.

Gti guy25 (talk)13:54, 21 July 2014

To prevent your wiki from redirecting to the IP URL instead of staying on the domain URL, update Manual:$wgServer so it points to the domain and not the IP.

After that, just follow the instructions about Manual:Short URL. Be sure to plan your URL scheme before trying to follow those instructions.

If you want your "edit" urls be on /w/index.php, you should rename your directory to w instead of mediawiki. That's the directory that needs to exists. the /wiki/PAGENAME directory for short urls shouldn't exist, because it will be a "virtual" one, which would be rewritten internally to point to the first one with rewrite rules.

Ciencia Al Poder (talk)13:34, 22 July 2014
 
 
 

Upgrade Trouble - no content gets loaded anymore

Hi,

I have a serious issue with my mediawiki installation. I am using Mediawiki as supported by my hoster "Strato". It worked very well. Then it did an update to 1.19.1-2 - and I have got serious problems. I can log in into my wiki - but nearly no page gets loaded. This looks like this: http://www.imgbox.de/users/public/images/uCp33WB1FS.PNG The only pages that get displayed somewhat correct are the special pages. Even the profile is messed up, as there are many field missing and such. The Sourcecode of the page I posted the screenshot of can be found at: https://piratenpad.de/LAs2W1GzFw

I do have access to the sql database - but it seems that I can't export the sql, as i only do get empty files / folders.

I can nevertheless navigate to a page in my wiki, push the "edit" button - and inside the edit window I do see every information that should be there.

Has anyone an idea how I can rescue my wiki?

Thanks,

Christian

86.103.211.2215:38, 20 July 2014

Hi!

This is a rather common upgrade issue. Usually it is a missing PHP extension, iIrc. However, right now I do not remember, which module it was exactly. Maybe the updater at mw-config/index.php shows more information on the missing module.

88.130.119.22116:58, 20 July 2014
Edited by another user.
Last edit: 21:41, 21 July 2014

My Index.php in MC-Config sais the following:

--- (PHP source code of the file) ---

What am I therefore missing?

86.103.211.2218:24, 20 July 2014

I mean when you execute this file with your webbrowser, enter this update-string it asks for and then... ;-)

88.130.119.22120:50, 20 July 2014

When I open this adress I get at first the language selection. Then I get:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, service@webmailer.de and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

86.103.215.19718:20, 21 July 2014
 
 
 
 

Why is this software so complicated?

Looking at open-source wikis, MediaWiki seems to be the best however, extremely confusing when diving into the back-end of it. I don't understand why they want to use complicated variable names and extremely confusing settings that require hard edits to a config file. Why can't there be one administrators panel that contains everything you need without needing FTP to access the wiki files to manage simple things?

Now the template engine, it's crazy. It's way easier to learn HTML than it is to form a table using their confusing engine. I see many bad practices when diving into the back-end and I'm wondering, why? Why does such a popular wiki software have just bad engines? I'm not going to lie, it's a powerful software however it can be written so much better to make it friendly to other developers.

24.47.179.3716:14, 21 July 2014

As for the file system access: Sure, config settings could also be done via a web interface. For MediaWiki that already partly is the case with the pages inside the MediaWiki namespace, where you can e.g. define CSS, which then is used for all users. However, usage of the file system amongst other things is an important barrier of additional security: The credentials of one of your admins might get lost and then attackers can manipulate e.g. these pages inside the MediaWiki namespace. However, what they cannot do is e.g. delete your complete database, because in order to gain access to the DB they would have to know the DB credentials, which only are available with direct file system access. And - another security-relevant aspect: You can have a hugh amount of wiki admins, but there should only be a very limited number of people with actual access on the file system level, which strengthens security even more.

As for the complexity of MediaWiki as a tool for the internet just have a look at other tools: MediaWiki is one of the bigger and more powerful wiki engines, no question. However, compared with other tools it is just like baby software: It does not offer full CMS options, workspaces, versioning, sophisticated user access levels, timed display of content, content rotation and so on, just to name a few.

However, I want to invite you: When you know how MediaWiki can be improved - made more simple, using better practises in the backend, then participate in its programming: Get Developer access and contribute your patches! Welcome aboard!

88.130.118.21117:21, 21 July 2014
 

You're right, MediaWiki is complicated to use. The quality of the help guides is inconsistent, editing config files directly rather than using a GUI is counter-intuitive, extending MediaWiki is a pain, and Wiki-markup drives away potential editors in droves.

However, there are some very good extensions, the most comprehensive being Bluespice. It has a comprehensive feature list (including a very good WYSIWYG editor) and since I installed it on my work wiki, editor retention is much higher.

Qiubov (talk)12:51, 22 July 2014

As I said: Baby software. If you want to know, what is really complex, have a look beyond your own nose. E.g. have a look at TYPO3. After a few months, when I successfully work with MediaWiki since a really long time already, we can then speak back and see, how far you made it.

88.130.109.10113:06, 22 July 2014
 
 

Points of discussion before going on-line

Dear Sir,

I installed and configured MediaWiki.

Before going on-line I like to discuss next points.

I am creating New York Wiki for New York City organisations.

Sysop, users and guests are the groups.

The MainPage is blocked.

From DefaultSettings.php I copied line 4141 (@ name user rights) to line 4811 (end of user rights settings)

Permission ['*'] all True Permission ['user'] all True Permission ['bot'] all False Permission ['sysop'] all True Permission ['bureaucrat'] all True

Do you have any comment on this?

Thank you in advance.

hansie

Hansie (talk)17:52, 29 June 2014
Edited by 2 users.
Last edit: 21:57, 29 June 2014

If you do not configure group permissions yourself, the default from DefaultSettings.php will be applied automatically - you do not have to copy it. Apart from that, information on how to configure user groups properly are available on page Manual:$wgGroupPermissions.

You will e.g. find that the permissions of multiple groups are cumulative: If a user is member of different groups, then the user will get a right if it is granted to at least one of these groups - even if it is not granted to his other groups. That means you do not have to grant all available rights (like the "block" or the "delete" right) to all users - in fact I think that you might not want to give ordinary users special rights like these.

Only grant special rights to the special groups.

88.130.94.7521:13, 29 June 2014

Thank you for your response.

Which rights should I give ordinary users?

hansie

Hansie (talk)06:55, 22 July 2014

Supplementary question:

Which rights should I give to "*"?

Hansie (talk)09:38, 22 July 2014

The group "*" is automatically given to all users. Users, who are not logged in, are in this group (and in this group only). The group "user" is automatically assigned to all users, who are logged in. Since user group permissions are cumulative, these users will then have all permissions of group "*" and additionally those, which are assigned to group "user".

Manual:User_rights#List_of_permissions is a list of all possible rights, which a user group can have. Which of them you want to give to e.g. the group "user", depends on what ordinary users should be able to do. See Manual:$wgGroupPermissions for details on how to assign permissions.

Which rights which group currently has can be seen in your wiki on the page Special:ListGroupRights. The rights, which are assigned by default (meaning without you assigning anything special yourself), already are more or less fine for most wikis.

As an example, if your wiki is publicly accessible and you then assign the group "*" the right to edit pages and to upload files, this will be a guarantee that you get spam en masse: In form of spammy pages and in form of trash uploads. You should better not do that. ;-)

88.130.118.21112:19, 22 July 2014
 
 
 

Please do not edit DefaultSettings.php. This configuration file includes, like the name say, default settings, so, if you update your MediaWiki version, this file will be override normally (and your changes are away). To define user rights and/or user groups, please use the LocalSettings.php and $wgGroupPermissions, like 88.130.94.75 explained. Additionally, you can use Manual:$wgRevokePermissions to revoke a permission for a special group (also, if this right is given by another group the user is a member of).

Florianschmidtwelzow (talk)06:16, 30 June 2014

Hello Florian,

What do you mean by "88.130.94.75"? It's a German IP address!

Thank you,

hansie

Hansie (talk)06:58, 22 July 2014

I mean the user :) The IP adress has no user account, so his ip address is shown as username (that's the only possibility for me to refer to) :) I mean this post: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Points_of_discussion_before_going_on-line/reply

Florianschmidtwelzow (talk)07:41, 22 July 2014
 
 
 

Cannot go forward when try to Edit ?

The website is http://www.trueerp.com/wiki/Main_Page Current Mediawiki version is 1.16.0 Php/5.4.28

Whenever we try to edit the help content the following message comes up and there is no apparent way to edit the help files on the websites wiki help. What is the problem with it? and you please provide the solution.

Omer Farooq

Ofarooq (talk)07:23, 20 July 2014

Hello! Can you provide the Error message please? Can you give a link to the page you want to edit?

Please notice, too: MediaWiki 1.16 isn't supported anymore. Please think about to upgrade your Installation.

Florianschmidtwelzow (talk)13:29, 20 July 2014

Hi!

This message show up every time we hit Edit to do editing on every page

Please note that all contributions to TrueERP wiki are considered to be released under the GNU Free Documentation License 1.2 (see TrueERP wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

There are different pages; try this one: http://www.trueerp.com/wiki/General

Awaiting.. Thanks

217.165.230.10606:44, 21 July 2014
 

Hi!

This message show up every time we hit Edit to do editing on every page

Please note that all contributions to TrueERP wiki are considered to be released under the GNU Free Documentation License 1.2 (see TrueERP wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

There are different pages; try this one: http://www.trueerp.com/wiki/General

Awaiting.. Thanks

Ofarooq (talk)05:31, 22 July 2014
 
 

Why is this software so complicated?

16:14, 21 July 2014

That depends on an individual point of view, i think :) In my view MediaWiki isn't complicated all over (yure, there are some points, which are complicated but the most aren't). If you say us, what exactly you feel as complicated, we can help you :)

Florianschmidtwelzow (talk)17:19, 21 July 2014
 

mediawiki URL

Currently my mediawiki url reads as follows: http://192.168.x.x/mediawiki/index.php/Main_Page

I want it to read http://wiki-name.domain-name.local/index.php/Main_Page. https:// would be nice as well.

I am using Apache2 but the mediawiki directions are too confusing for me to understand. Can anyone help me with this?

MediaWiki ver. 1.23.1

The directory of my mediawiki is /var/www/. I do not know what to edit to change the URL.

Please help, thank you!

Gti guy25 (talk)18:04, 10 July 2014

The URL to your wiki must be set in LocalSettings.php (just like e.g. $wgLogo, which is also set in that file) and you can change it by setting $wgServer to another value. This will then make MediaWiki output URLs starting with the domain you want. Take care however, that Apache also needs to be configured accordingly so that it maps that domain to the webroot directory. (Don't ask me how that is done - I have no clue.)

88.130.86.17418:36, 10 July 2014

And the Apache part is where I get stuck because I do not see where you need to edit the Apache config. I will play around some more and see if I get it. The wiki I'm working on is only a test. Thank you though.

Gti guy25 (talk)19:20, 10 July 2014

You can edit the documenroot in the virtualhost configuration, most in /etc/apache2/sites-available. You can add the ServerName, too, to make an alias to wiki-name.domain-name.local. Be sure, that wiki-name.domain-name.local in your local DNS Server points to 192.168.x.x (the IP adress where apache is running). Https you get, when you use ssl in apache2 (and enable it for your host). Notice, that you can use a self signed certificate, when you use the wiki only locally (which i think, because you want to use a local domain), but you must add the certificate as a trusted (or add an exception in your clients, that they won't check this certificate). If you want to use the wiki on a wider range outside of your local network you can manage, then maybe it's better to use a certificate of a trusted CA (they take money ;)).

Florianschmidtwelzow (talk)19:37, 10 July 2014
Edited by another user.
Last edit: 09:37, 11 July 2014

Florianschmidtwelzow: when you say I can edit the document root in the virtualhost configuration, is it the <VirtualHost *:80> OR do I add what I need under <VirtualHost> at the bottom of the "default" file inside sites-available? And by my "local DNS Server" you mean to add wiki-name.domain-name.local or the IP Address to the DNS settings in Active Directory or something like that, correct? Sorry to be such a newbie, this is a project that was assigned to me at work and I am not a programmer nor do I know anything about Linux stuff.

Maybe this will help you more, this is exactly what I see when I am in /etc/apache2/sites-available/default:

<VirtualHost *:80>
        ServerAdmin webmaster@localhost
 
        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

I know that I need to change one of these AllowOverrides None to AllowOverride All but not sure which

Maybe you can show me what it should look like when it's done?

Anything would be a great help. In the meantime, I will add the appropriate DNS entry.

Gti guy25 (talk)20:25, 10 July 2014

Florianschmidtwelzow: I just added the DNS record, and was able to ping my wiki server by name. Then I opened up IE and browsed to wiki-name.domain-name.local/mediawiki/index.php and it brought me right to my wiki page. Now, my question is how can I get it to just say: wiki-name.domain-name.local/index.php/Main_Page? Do I still need to edit the default file? If so please proceed to respond to my last post, if not please let me know how if you can. Thank you.

Gti guy25 (talk)20:40, 10 July 2014
 

Hello! You have to edit the file, where you entered the host configuration :) If this is the file you posted in your post, then change DocumentRoot /var/www to DocumentRoot /var/www/mediawiki and <Directory /var/www/> to <Directory /var/www/mediawiki/>. Restart/reload the server settings and navigate to your wiki. In order to use (maybe you want) short URL you can change AllowOverride in the directory section(<Directory /var/www/>) to All, or add the rewrite rules directly in the host configuration and leave allowoverrides to none.

Florianschmidtwelzow (talk)05:49, 11 July 2014
 
 
 
 
 

Searching in Documents

Hey, is it possible to search through the content of Uploaded Documents ? I didnt find any extensions and the inbuilt Search feature just looks at tht names of the documents

213.208.144.3608:31, 21 July 2014

What file formats are "Uploaded Documents"?

AKlapper (WMF) (talk)12:43, 21 July 2014

Sorry i forgot. Im talking about mostly PDF files.

213.208.144.3612:59, 21 July 2014
 
 

Weird Navigation items in Sidebar

So trying as best I can to get the 1.23 Monobook skin up to the functionality that we had previously...

And seemingly out of nowhere, some strange stuff appeared at the top of our navigation bar, here: http://awoiaf.westeros.org -- I've no idea where that random S or its lavel p-.3c-label came from.

It did appear after I attempted to use the PCR GUI Insert extension to try and place an ad unit in that sidebar, but even after removing it, and even removing the extension, the problem persists. I've looked in SkinTemplate.php and my base skin to see if a stray typo somewhere has caused this, but I'm running empty. Any thoughts as to how I might discover the culprit?

Balerion300 (talk)18:41, 20 July 2014

I don't see a random S or p-.3c-label on that page or in its source code. Any screenshot? Or does one need to be logged in for that and use a different skin?

AKlapper (WMF) (talk)00:00, 21 July 2014

I saw it yesterday, but I didn't have a solution. However, as André says: It is no longer there now.

88.130.81.6609:07, 21 July 2014
 
 
First page
First page
Previous page
Previous page
Last page
Last page