I am using the template infobox person and getting an error for the image part only

Everything else is working fine.

Where a person should have an image, it shows:

Script error: No such module "InfoboxImage".

How can I fix this? 174.48.154.154 (talk) 08:34, 1 May 2013 (UTC)

Have you looked at the Lua debugging help on "Causes of Script Error"? ☠MarkAHershberger☢(talk)☣ 14:53, 1 May 2013 (UTC)

Question on Title Class properties

Hi, my company will use a wiki within intranet, probably version 1.19.0. The Wiki is not accessible from www. We wanna have articles with same article names but different namespaces, eg. BAR:foo / BAZ:foo / RAB:foo. To build navigation links, I'm looking for the object properties to get the Namespace name and article name for the displayed article. I've looked over the title class reference but didn't get through really. Maybe you can help me out telling me which methods / property will hold this vars?

To be exact, if the article would be BAR:foo, i would need to call a property to return "BAR" and one to return "foo".

Thanks in advance, regards, Dennis 82.135.88.167 (talk) 11:08, 1 May 2013 (UTC)

Why not just split the title on ":" to get that information? ☠MarkAHershberger☢(talk)☣ 14:55, 1 May 2013 (UTC)

Also, you don't make clear what you are using to get at the title object. Assuming you're writing an extension or skin for MediaWiki, look at the getNamespace and getText methods. ☠MarkAHershberger☢(talk)☣ 15:02, 1 May 2013 (UTC)

Hi, you guess right, I try to make a small extension to add extra tabs right beside the page / talk / edit tabs of the used skin. The idea is to have a simple navigation to swap betweeen the three namespaces. The namespaces represent different views on the same topic, say customer service info, technical support info, product management info on a certain product.

I've found a code sample that will do so with a static url to stick with the new tab, now I'm searching an easy way to get it working dynamic. I've added the php code below, to make it possibly more clear. To get it work dynamically, I would need to compare if the actual display page is one of the 3 namespaces Tec / PM / CS and which is the title of the page ('Seite' in the code below). I Could parse the URL by myself of course, but hoped there is an easy way to access the values though wiki object attributes.

Next step will be to detect if the specific Namespace:title exists yet, so I can make the extension decide to display the action tab in red or blue and to skip making the extra tab buttons in case the actual displayed page is a specialpage.

My problem is, I am not too familiar with the wiki object modell, I read accross the manual for article and title classes, but didn't get the clue yet how access the values I needed. Just hoped to find someone here, who is so familiar with that so he/she can tell this out of sleep :) If this was to optimistic, I'll go on trying to understand from the manual :)

Regards,

Dennis

<?php
// ParserHook
 $wgHooks['SkinTemplateContentActions'][] = 'ReplaceTabs'; 
// Function to add the tabs
 function ReplaceTabs ($content_actions) {  
     $tectitle = Title::newFromText('Tec:Seite');
     $pmtitle = Title::newFromText('PM:Seite');
     $cstitle = Title::newFromText('CS:Seite');
 
     $main_action['tec'] = array(
        'class' => false,						//if the tab should be highlighted
        'text' => 'Tec',						//what the tab says
        'href' => $tectitle->getFullURL(),		//where it links to
      );
     $main_action['pm'] = array(
        'class' => false,						//if the tab should be highlighted
        'text' => 'PM',							//what the tab says
        'href' => $pmtitle->getFullURL(),		//where it links to
      );
     $main_action['cs'] = array(
        'class' => false,						//if the tab should be highlighted
        'text' => 'CS',							//what the tab says
        'href' => $cstitle->getFullURL(),		//where it links to
      );
 
	  $content_actions = array_merge( $main_action, $content_actions);   //add tabs to the bar
      return true;
 }
 ?>

62.153.144.77 10:11, 2 May 2013 (UTC)

To make your code dynamic, you would need the current page's title object from the global variable $wgTitle or (in newer MediaWiki) from the request context.

Once you have that you can use the getBaseText() method to get the part of the title you want. So instead of

$tectitle = Title::newFromText('Tec:Seite');

you would have (note that this is untested):

global $wgTitle;

$tectitle = Title::newFromText( 'Tec:' . $wgTitle->getBaseText() ); ☠MarkAHershberger☢(talk)☣ 13:16, 2 May 2013 (UTC)

Cool, it works! Thx Mark! 62.153.144.77 13:29, 2 May 2013 (UTC)

[RESOLVED] Link to folder within Wiki (conflict with short URL)

Alrighty,

Now that I've go the short URL working nicely, I have another challenge. I have a folder within my wiki that has another index, so when I do wiki.domain.com/folder...instead of launching the index page within folder, I get a new wiki page called Folder...naturally.

Is there a way to get the index under my other folder now that I have the short URL set up?

Thanks much! 98.189.165.213 (talk) 18:27, 1 May 2013 (UTC)

Add another RewriteCond before your first RewriteRule so you have two then:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

☠MarkAHershberger☢(talk)☣ 18:57, 1 May 2013 (UTC)

Awesome! I don't know how or why that works (don't know much about php) but am glad for this support!!

Thanks much! 98.189.165.213 22:41, 1 May 2013 (UTC)

That isn't php, though. Those are Apache mod_rewrite rules. ☠MarkAHershberger☢(talk)☣ 00:08, 2 May 2013 (UTC)

Oh! Even less familiar with that ;-) 98.189.165.213 17:54, 2 May 2013 (UTC)

Headings and numbered lists

I am trying to create an article which is an employee manual that is basically a large numbered list with many sublists. I would like to use the Table of Contents to be able to jump to specific sections but I cannot work out a way to use headings IN a numbered list. For example:

1. Heading 1
   1. item 1.1
   2. item 1.2
2. Heading 2
   1. item 2.1
   2. item 2.2

But of course taking a new line for the heading breaks the list, as per:

Backup Mediawiki

Hi I would like to know how to backup Mediawiki because they have realised a new version I have read the guide on how to back it up but dint get it my host is 000webhost which lets you backup MySQL please could I have some help on backing it up 109.155.55.77 (talk) 16:35, 2 May 2013 (UTC)

What guide did you read? Where are you stuck? ☠MarkAHershberger☢(talk)☣ 16:38, 2 May 2013 (UTC)

This guide Manual:Backing up a wiki and I am stuck do you just backup the server which is MySQL or do you back up the other files because I know how to backup MySQL because on the main page it allows you to backup the MySQL but I doint know how to backup the other part of the wiki 109.155.55.77 17:09, 2 May 2013 (UTC)

Hi!

You need to backup two things:

• The database from the MySQL server => you know that already.
• And you should backup all files inside your wiki folder. Create an archive of this folder. In the guide, which you are reading that is the part under "3. File system". 88.130.68.116 17:30, 2 May 2013 (UTC)

Ok thanks but after the upgrade do I just copy the codes which I added from the old version to the new one and then delete the backup and re do the backup 109.155.55.77 17:40, 2 May 2013 (UTC)

Is there any videos on how to backup Mediawiki and how to upgrade 109.155.55.77 17:48, 2 May 2013 (UTC)

I'm not sure what you mean by "the codes which I added". If you modified the source code of MediaWiki -- modified it more than just installing extensions in the extensions directory -- then an upgrade takes more care.

Otherwise, after you have successfully run the update script, you will only need the backups if you need to roll back your wiki to the old version for some reason. ☠MarkAHershberger☢(talk)☣ 18:28, 2 May 2013 (UTC)

Ok thanks 90.216.85.28 16:26, 3 May 2013 (UTC)

How to choose multiple groups in the per page protection in Simple Security extension in Vector skin in Mediawiki 1.20.3?

How to choose multiple groups in the per page protection in Vector skin in Mediawiki 1.20.3? I want to give read permissions to more than 3 custom user groups as I have a total of 14 custom user groups. How can I select multiple groups .please reply ASAP.--Satyamcompany (talk) 17:34, 2 May 2013 (UTC)

See Extension:Lockdown. ☠MarkAHershberger☢(talk)☣ 18:21, 2 May 2013 (UTC)

Internal image links not working

On an older version of MediaWiki I was able to do an internal link with an image like this <img>imagelink</img>.

When I upgraded, this stopped working...so I've tried multiple combinations to no avail.

External links work well in this format - [External_link Image_link] - but I don't want to do that for internal links because I have my external links set up to open a new window, which I don't want for internal links.

I have all my images in a folder called "images", and I couldn't get this format to work so I just went with the external images

Anything I'm missing? 98.189.165.213 (talk) 17:53, 2 May 2013 (UTC)

I think you were using an extension for the <img> tags. I helped a client upgrade from 1.11 to 1.19 and saw this was something they were using.

What happens if you use [[Image:Image_name.jpg]] to link show your internal images? Also, see Help:Images. ☠MarkAHershberger☢(talk)☣ 18:14, 2 May 2013 (UTC)

That format was a bit confusing for me...as it talks about storing images on a mediawiki server, where I have all my images on my web host's server. I'm under the impression that if I want to upload a bunch of pictures, say if I have some edits to do, I would have to do them one at a time with the upload utility.

But, I did try the upload utility and that [[Image:Image_name.jpg]] format...but when I used that syntax and saved the page, it gave me a red link, so I clicked that and it took me to the utility to upload the picture...which I did, but the image never showed up. 98.189.165.213 18:35, 2 May 2013 (UTC)

Interesting. So you did everything right, it sounds like. Maybe uploads aren't working.

Could you look at your error log and tell me what you see when you try to upload a picture? See Manual:How to debug if you need some help with that or ask more questions here. ☠MarkAHershberger☢(talk)☣ 18:52, 2 May 2013 (UTC)

Well, I'm not really interested in doing the upload method for pictures, because there are times when I need to upload a bunch at one time...so I'd rather just pick and choose which one's I need uploaded and then do them all at once through my FTP client.

Does this mean there is no way to have an external image link for an internal link unless I do it that way?...or perhaps find out why my img tags don't work anymore? 98.189.165.213 20:22, 2 May 2013 (UTC)

If you do this in-wiki, you'll have access to better scaling and other amenities that are mentioned in Help:Images. Multiple uploads can be handled with Extension:UploadWizard or Extension:MsUpload.

Still, you haven't lost the ability to show non-wiki images. As Help:Images says, set $wgAllowExternalImages correctly and then you'll be able to just use a url for the image like https://en.wikipedia.org/upload/b/bc/Wiki.png to get an image: https://en.wikipedia.org/upload/b/bc/Wiki.png ☠MarkAHershberger☢(talk)☣ 21:40, 2 May 2013 (UTC)

Thanks Mark...I'm not making myself clear.

So, that's good to know about the upload to wikiserver that I can do multiple images. Will have to play with that later...but in the mean time, I'd like to be able to have my external images link to internal pages. If I put the full url for the internal page, then it treats it like an external page and opens a new window, since I have a rule set up to do that for external links. I don't really want that when the user is navigating within the wiki.

It doesn't work with any syntax I've tried, so I might have to enable the rawhtml (which is seems is not advisable) to use the img tags..? I have done the allowimgtag thing, but that doesn't seem to work for it either.

I'll play more around with it tomorrow and post anything if I get successful.

Thanks much! 98.189.165.213 00:15, 3 May 2013 (UTC)

So, what I gave you works except for the external image in a new window ($wgExternalLinkTarget) setting. You could make what I gave work if you used the LinkerMakeExternalLink hook to keep $wgExternalLinkTarget from affecting the image links. ☠MarkAHershberger☢(talk)☣ 14:57, 3 May 2013 (UTC)

[RESOLVED] .htaccess RewriteCond help...I think?

Mark...ya helped me with the folder issue I had before by telling me to add one more RewriteCond line in the .htaccess, so I tried adding another line and changing the letter to -e, so I could get to a different folder but that didn't work completely.

What I have is a folder/large/image and a folder/small/image setup...and for some reason the small image folder shows my image, but the large image is trying to create a new wikipage.

Since you have a firm grasp of Apache it seems, I thought I'd ask you first, if ya don't mind as this is all new territory for me ;-)

Thanks! 98.189.165.213 (talk) 18:29, 2 May 2013 (UTC)

Just to be clear: I'm not the only person here. There are a few other people who help users with some regularity here.

Why did you use -e? That works if you are using Unix's shell test syntax, but it isn't listed as an option option for RewriteCond. -d tests if a directory exists at the given name, and -f tests if a file exists. So, the code I gave should work the same for this other directory.

Since it isn't, could you provide some more details of what you're trying? ☠MarkAHershberger☢(talk)☣ 18:43, 2 May 2013 (UTC)

Alrighty...it didn't make any sense to my either how one worked and the other didn't, so I reuploaded the whole file and images, and now it works. :-/

Thanks again! 98.189.165.213 20:55, 2 May 2013 (UTC)

How to move a wiki and all it's files?

Hi, I'm currently trying to move a wiki to a new domain. I can't access the files directly, because the wiki I want to fork is on Wikia. They have told me their is no way they can give me a package of all files and articles. Is their some software I can use to copy the wiki and it's history? Thanks in advance. 95.145.110.98 (talk) 19:05, 2 May 2013 (UTC)

Use Special:Export on your Wikia wiki and then Special:Import on your own. Note that anyone who contributes to your wiki will have to create a new account. You can see the extensions you need on Special:Version although they do have some customization. ☠MarkAHershberger☢(talk)☣ 19:19, 2 May 2013 (UTC)

So will everyone's editcount still be the same? 95.145.110.98 19:48, 2 May 2013 (UTC)

Only if they can get the same usernames on your wiki that they have on Wikia's. ☠MarkAHershberger☢(talk)☣ 21:23, 2 May 2013 (UTC)

On Wikia you can request a dump of all articles in XML format (you can then import this following Manual:Importing XML dumps). Note that the dumps don't contain log actions nor user accounts.

To associate user accounts from the wikia wiki to your wiki you may want to install Extension:MediaWikiAuth, but I don't know if it still works. Ciencia Al Poder (talk) 09:31, 3 May 2013 (UTC)

Is there anyway I can keep log actions, user contributions, etc? 95.145.110.98 09:38, 5 May 2013 (UTC)

Can you install MediaWiki extensions? Maybe there is an extnsion, which allows you to create a MySQL dump of your database. Thta would then not only include the pages and the texts, but also all user data, all log entries and everything else. 88.130.107.236 13:35, 5 May 2013 (UTC)

Installing an extension on Wikia? hah, good joke!

You can check out Edward Chernenko's MediaWiki Dumper Ciencia Al Poder (talk) 18:25, 5 May 2013 (UTC)

Images not working on Infobox

I have exported Wikipedia's Infobox person and I'm using it on my wiki. However, in the image section i get this:

{{#invoke:InfoboxImage|InfoboxImage|image=|size=|sizedefault=frameless|alt=|suppressplaceholder=yes}}

Please be very thorough on instructions I don't know anything about coding and I just want to have a simple wiki :S 174.48.154.154 (talk) 04:59, 3 May 2013 (UTC)

Do you have Extension:Scribunto installed? If not, you may want to roll the template back to this version before they it Lua was installed on Wikipedia. ☠MarkAHershberger☢(talk)☣ 14:53, 3 May 2013 (UTC)

I do have it. However, enabling it in LocalSettings nukes my wiki. 174.48.154.154 16:32, 3 May 2013 (UTC)

Does rolling back to the previous version fix your problem? ☠MarkAHershberger☢(talk)☣ 17:02, 3 May 2013 (UTC)

How would I export this template if the name of the article is exactly the same as the new one? 174.48.154.154 17:24, 3 May 2013 (UTC)

Quick overview of how to do this:

1. Export the entire history of the template.
2. Delete the template from your wiki.
3. Import the template and all its history.
4. Rollback to a version that doesn't include the Lua bits. ☠MarkAHershberger☢(talk)☣ 18:32, 3 May 2013 (UTC)

How do you export the history?

Is it like Infobox person/history 174.48.154.154 19:00, 3 May 2013 (UTC)

On Special:Export, uncheck the box that says "Include only the current revision, not the full history". ☠MarkAHershberger☢(talk)☣ 19:16, 3 May 2013 (UTC)

Last question for the moment: is there a quick way to remove all templates? Perhaps through FTP? 174.48.154.154 20:23, 3 May 2013 (UTC)

Not out of the box, no. ☠MarkAHershberger☢(talk)☣ 22:34, 3 May 2013 (UTC)

So you just delete all of them manually? 174.48.154.154 22:36, 3 May 2013 (UTC)

Why do you want to delete them *all*? If you import a new one, it should overwrite the current one. I just said you should delete them to be safe. ☠MarkAHershberger☢(talk)☣ 22:38, 3 May 2013 (UTC)

It doesn't overwrite it :/ 174.48.154.154 22:45, 3 May 2013 (UTC)

ExtensionDistributor

How can I use ExtensionDistributor because I have installed it but I doint know how to provide extensions through it 90.216.85.28 (talk) 16:07, 3 May 2013 (UTC)

The WMF has trouble keeping ExtensionDistributor up and running here. Why do you want to use it? ☠MarkAHershberger☢(talk)☣ 17:04, 3 May 2013 (UTC)

Because I would like to host downloads through my website but I doint know how to add them 90.216.85.28 17:20, 3 May 2013 (UTC)

If you can upload files to your site, you can host downloads. You don't need ExtensionDistributor. ☠MarkAHershberger☢(talk)☣ 18:29, 3 May 2013 (UTC)

How can I upload file so I can download them 90.216.85.28 18:51, 3 May 2013 (UTC)

See Help:Upload. ☠MarkAHershberger☢(talk)☣ 18:53, 3 May 2013 (UTC)

But how would I use ExtensionDistributor I have installed iron my wiki but how do I add extension so I can download them 90.216.85.28 18:59, 3 May 2013 (UTC)

Unless you have your extension in some sort of version control like git, you're talking overkill. ☠MarkAHershberger☢(talk)☣ 19:15, 3 May 2013 (UTC)

Oh ok 90.216.85.28 19:31, 3 May 2013 (UTC)

Bugzilla Reports extension. Bug activity report

I need a report that lists bugs that have status changed from "Resolved" to "Reopen" and back to "Resolved. "

Is this something that can be done with this extension? 65.51.148.226 (talk) 17:25, 3 May 2013 (UTC)

I don't think anyone here can answer you. You should try contacting the author or check with one of the wikis that uses it. ☠MarkAHershberger☢(talk)☣ 18:36, 3 May 2013 (UTC)

Change the page users are redirected to when they log in

is it possible to change which page users are redirected to when they log into the wiki? Imperfectbacon (talk) 18:12, 3 May 2013 (UTC)

See Manual:$wgRedirectOnLogin. ☠MarkAHershberger☢(talk)☣ 19:57, 3 May 2013 (UTC)

Uploaded images aren't uploading to server; returning a 404 file not found when I click on the link

Hello all, I could really use some help: Using a bluehost server; after having this error repeatedly, I guessed that the problem was that I used Installatron to install Mediawiki To correct that, I did a REAL install last night-- didn't correct the problem. Tried switching from PHP 5.3 to 5.4 - no effect Adjusted images folder to 777 - no effect Uploads are enabled in both

 Local Settings:
      $wgEnableUploads  = true;
      $wgUseImageMagick = true;
      $wgImageMagickConvertCommand = "/usr/bin/convert";

AND

  php.ini
      file_uploads = On

The upload process on the wiki itself seems to work fine-- the upload screen shows the thumbnail of the image about the imported. Once the upload is done however, no image displays-- just the question marked thumbnails. When I click on the image link itself, it takes me to a 404 screen with the URL typically /w/images/'number or letter'/'number or letter'/'my filename'. No folder or file is created in /images, however.

This led me to believe that the wiki was handling the upload properly, but that the php was not.

The only thing I could think was that the temporary file wasn't being handled appropriately by the php, so I started by editing upload_tmp_dir. I created an {IP}/tmp folder and set it to 777. Changed the value in php.ini to: upload_tmp_dir = /tmp no effect

Next I tried to force the move of the uploaded files-- I'm not an experienced coder, so this is the best I could find of how to actually do that: move_uploaded_file($_FILES['userfile']['tmp_name'], "/home2/icozeroc/public_html/w/images")

no effect

This is getting very frustrating because I can't upload images (or any file for that matter) to my site.

I'm also confused because I've imported numerous templates, including all of the mbox and associated families, all which have image thumbnails in them I also have successfully used many instances of Extension:EmbedImg with <img> tags, so I'm really not sure what the problem is, but I can't go further without the solution.

PLEASE HELP!!!!!!!!!! 75.131.251.37 (talk) 20:02, 3 May 2013 (UTC)

Try setting $wgTmpDirectory to $IP/images/tmp.

If that doesn't work, look at How to debug and see if turn on logs or other things on that page helps.

Let me know how it goes. ☠MarkAHershberger☢(talk)☣ 20:08, 3 May 2013 (UTC)

I added the $wgTmpDirectory line, but I didn't create images/tmp folder to see what it would do. When I tried to upload an image, the error message on the upload screen was "Error creating thumbnail: Unable to save thumbnail to destination". After adding /tmp and setting to 777, the original issue continued-- blank thumbnail and a bad link. Also, no files were created in /images or /tmp (I read that they are deleted from /tmp automatically?).

I'm not sure exactly how to use the debug commands, because other than the bluehost 404 page, no obvious error message comes up.

Suggestions? Ptesvi2 (talk) 20:56, 3 May 2013 (UTC)

Try adding

error_reporting( -1 );
ini_set( 'display_errors', 1 );

to the end of your LocalSettings.php ☠MarkAHershberger☢(talk)☣ 22:32, 3 May 2013 (UTC)

I added it before, but I didn't know where to look for the errors. Uploading works fine from the wiki end, but the file never gets copied into the appropriate directory, so I get the 404 page. How can I view the error reporting? Ptesvi2 (talk) 22:52, 3 May 2013 (UTC)

Ok, I figured it out...

I had Extension:SocialProfile loaded into the wiki. The hooks dealing with uploading avatar images seem to have been interfering with standard uploading.

Thanks! The error at the top of my page had to do with the upload avatar command, so I disabled the social profile extension, and now uploading works. Awesome. Thanks again!! Ptesvi2 (talk) 23:02, 3 May 2013 (UTC)

Sorry, forgot a few things:

Mediawiki version 1.20.5

MySQL 5.5.30 75.131.251.37 20:11, 3 May 2013 (UTC)

Restrict Usergroup Access to Specific Page Group

I have a debates section that I want default users to be able to access, but I don't want them to be able to edit any other pages, including templates. I looked at Manual:User rights but it simply uses a broad edit permission rather than letting me restrict editing to a specific class of pages. I looked at Category:Page_specific_user_rights_extensions but don't see anything that clearly restricts editing to only a class of pages without security holes. When I look at Special:ListGroupRights I don't see any permissions specific to page classes, just a generic Edit permission. Would I need to install some kind of extension and perhaps change the Debates section to a Special section, i.e. Special:Debates instead of Debates?

MediaWiki: 1.20.3
PHP: 5.3.23
MySQL: 5.5 Jzyehoshua (talk) 01:20, 4 May 2013 (UTC)

You could create a debates namespace and then use $wgNamespaceProtection to only allow debaters to edit pages in the namespace. ☠MarkAHershberger☢(talk)☣ 18:36, 4 May 2013 (UTC)

Alright, thank you for the help! I'll try this and see if it works. Jzyehoshua (talk) 10:38, 10 May 2013 (UTC)

Alright, so adding the following line in LocalSettings.php restricts editing of the main directory it seems:

$wgNamespaceProtection[NS_MAIN] = array( 'editinterface' );

However, I am confused as to how to specify an additional namespace that can be edited, a debates section. If the debates section is wiki/debates, then how do I declare a namespace that declares this page can be edited, unlike the others?

I think I understand how to setup a custom namespace for debates that can be edited using the following:

$wgNamespaceProtection[NS_DEBATES] = array( 'debates-edit' );

$wgExtraNamespaces = array(100 => "Debates",);

$wgGroupPermissions['user']['debates-edit'] = true;

$wgGroupPermissions['administrator']['debates-edit'] = true;

$wgGroupPermissions['bureaucrat']['debates-edit'] = true;

$wgGroupPermissions['sysop']['debates-edit'] = true;

What I don't understand is how to assign this new namespace to the debates section itself. Since the debates section is apparently part of the main namespace, I'm not sure how to separate it so it can be edited. Or else, if the coding is now declaring a new namespace called Debates can be edited, I'm not sure how to create pages at this namespace for editing.

At any rate, the coding right now is having no effect. While the entire wiki can't be edited by registered accounts apart from talk pages (which I want) the debates section also can't be edited (which I don't want). Jzyehoshua (talk) 11:45, 10 May 2013 (UTC)

Ohh, I get it, never mind. :) A page has to be at wiki/Debates: to work, so e.g. wiki/Debates:Debates. Now registered accounts can create pages through the Debates namespace but not through the main namespace, which works for me. Thanks again for your help! Jzyehoshua (talk) 13:11, 10 May 2013 (UTC)

Problem with Image thumbnailing

I use this code to insert uploaded images to wiki articles

[[Файл:Baby.jpg|200px|thumb|left|Image description]]

It works fine! But when I try to change its size, there is a message: error creating thumbnail /usr/bin/convert not found! And when I use different sizes the image apperas, but in some cases there is the error messages.
For example when I do so:

[[Файл:Baby.jpg|200px|thumb|left|Image description]] - I have error message
[[Файл:Baby.jpg|200px|thumb|left|Image description]] - I have image 
[[Файл:Baby.jpg|300px|thumb|left|Image description]] - I have image
[[Файл:Baby.jpg|400px|thumb|left|Image description]] - I have error message
[[Файл:Baby.jpg|500px|thumb|left|Image description]] - I have error message
[[Файл:Baby.jpg|600px|thumb|left|Image description]] - I have image

And so on ... How can I fix it? Fokebox (talk) 15:31, 4 May 2013 (UTC)

One of the following will solve this:

• Set $wgUseImageMagick to false.
• Set $wgImageMagickConvertCommand to the correct path for ImageMagick's convert.
• Install ImageMagick. ☠MarkAHershberger☢(talk)☣ 18:34, 4 May 2013 (UTC)

Thx! $wgImageMagickConvertCommand helped to solve my problem! Fokebox (talk) 19:14, 4 May 2013 (UTC)

Putting the wiki files on github

Need to get the username in the login.--Shiva

Hello I am a newbie to mediawiki,I have a project of setting up a mediawiki integrated to ldap.I was able to get the mediawiki integrated to ldap.Just modified the apache config and added the ldap credentials. Now I want to see the username on top of my page instead of IP.I tried various extensions - MyVariables,GetUserName,UserFunctions mentioned,but none seem to work after I add the required once line in LocalSettings.php file. Can anyone please give me a step by step process to get this done?

Thanks 12.44.85.98 (talk) 19:17, 6 May 2013 (UTC)

Details:

1.15.5-1--Mediawiki

5.3.3-0 -- Php

5.0.51a-24+lenny2 -- MySql 12.44.85.98 19:28, 6 May 2013 (UTC)

I've used Extension:AutomaticREMOTE_USER for this. You should upgrade your installation to the one available with Debian Wheezy. ☠MarkAHershberger☢(talk)☣ 19:31, 6 May 2013 (UTC)

syntaxhighlight and source tags not recognized

Product Version

MediaWiki	1.15.3
PHP		5.3.3-7+squeeze9 (apache2handler)
MySQL		5.1.49-3

Hi,

I'm trying to display an XML file and can't get the code to display properly. For some reason syntaxhighlight and source tags aren't recognized and are displayed directly when previewed. According to the extension page this tag is supported in my version, so why won't it work?

Thanks! Jdmswong (talk) 19:36, 6 May 2013 (UTC)

First, could you upgrade? Wheezy has a new version of MediaWiki.

Second, what does your Special:Version page show? ☠MarkAHershberger☢(talk)☣ 20:03, 6 May 2013 (UTC)

[RESOLVED] Can't upload mwstore://local-backend/local-public

I have a mediawiki 1.20.3, I have migrated the mediawiki on a new server.

Since I can't upload file, i have error: could not create a directory mwstore://local-backend/local-public/f/fe

It's not a permission problem on a folder because if I create a new database with the install script, and I change in my configuration file the database by the new database, I can upload.

I have upgraded the mediawiki in 1.20.5 and I have always the same problem.

Regards,

-- nishiki Nishiki~mediawikiwiki (talk) 07:59, 7 May 2013 (UTC)

Can you try turning on logging and tell us what it shows? ☠MarkAHershberger☢(talk)☣ 02:26, 8 May 2013 (UTC)

When i upload a file, i have this in my log:

Start request POST /wiki/Sp%C3%A9cial:T%C3%A9l%C3%A9verser
HTTP HEADERS:
CONTENT-LENGTH: 1307125
CONTENT-TYPE: multipart/form-data; boundary=---------------------------3923318973004936151503758169
ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
ACCEPT-ENCODING: gzip, deflate
ACCEPT-LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
CONNECTION: keep-alive
COOKIE: _wiki_session=5sk8h43m6n0rsb62irlj5kch43; _wikiUserID=1; _wikiUserName=Admin
DNT: 1
HOST: site.net
REFERER: http://site.net/wiki/Sp%C3%A9cial:T%C3%A9l%C3%A9verser
USER-AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Iceweasel/20.0
CACHES: EmptyBagOStuff[main] SqlBagOStuff[message] SqlBagOStuff[parser]
session_set_cookie_params: "0", "/", "", "", "1"
Class LanguageFr not found; skipped loading
LocalisationCache: using store LCStore_DB
Connecting to site.net _wiki...
Profiler::instance called without $wgProfiler['class'] set, falling back to ProfilerStub for safety
Connected to site.net _wiki.
Fully initialised
User: cache miss for user 1
User: loading options for user 1 from database.
User: logged in from session
User: loading options for user 1 from override cache.
Connecting to site.net _wiki...
Connected to site.net _wiki.
MessageCache::load: Loading fr... got from global cache
Unstubbing $wgParser on call of $wgParser::firstCallInit from MessageCache::getParser
Parser: using preprocessor: Preprocessor_DOM
Unstubbing $wgLang on call of $wgLang::_unstub from ParserOptions::__construct
User::getBlockedStatus: checking...
IP: 58.237.68.11
Unstubbing $wgAuth on call of $wgAuth::getCanonicalName from User::getCanonicalName
UploadBase::createFromRequest: class name: UploadFromFile
FSFile::getProps: Getting file info for /tmp/phpIelsJG
MimeMagic::__construct: loading mime types from /home/wiki/www/w/includes/mime.types
MimeMagic::__construct: loading mime info from /home/wiki/www/w/includes/mime.info
MimeMagic::doGuessMimeType: analyzing head and tail of /tmp/phpIelsJG for magic numbers.
MimeMagic::doGuessMimeType: getimagesize detected /tmp/phpIelsJG as image/png
MimeMagic::guessMimeType: guessed mime type of /tmp/phpIelsJG: image/png
MimeMagic::improveTypeFromExtension: improved mime type for .png: image/png
FSFile::getProps: /tmp/phpIelsJG loaded, 1306004 bytes, image/png.
mime: <image/png> extension: <png>
UploadBase::verifyExtension: mime type image/png matches extension png, passing file
UploadBase::detectScript: checking for embedded scripts and HTML stuff
UploadBase::detectScript: no scripts found
ZipDirectoryReader: Fatal error: zip file lacks EOCDR signature. It probably isn't a zip file.
UploadBase::detectVirus: virus scanner disabled
UploadBase::verifyFile: all clear; passing.
ContextSource::getContext (UploadForm): called and $context is null. Using RequestContext::getMain() for sanity
Class PEAR_Error not found; skipped loading
OutputPage::sendCacheControl: private caching;  **
Request ended normally

78.237.69.11 19:36, 8 May 2013 (UTC)

I don't see an error message in these logs like the one you describe. ☠MarkAHershberger☢(talk)☣ 20:18, 8 May 2013 (UTC)

I hope you've found the solution already, but if not, this is maybe a solution for you. I had the same error message, and all I had to do is to run chmod -R 777 ./images inside my mediawiki root directory (this is the default upload directory, if yours are different, then of course you have to do it for your upload directory), since it was a permission problem. Since then, the file upload and the math expression generation (this is where I first found error) works perfectly. Csega (talk) 15:50, 4 December 2014 (UTC)

How to add a globle login extension

Hi could I have some help to install the global extension for all the wikis I have read the installation guide on the extension page but didn't know how to install it 86.171.33.224 (talk) 18:33, 7 May 2013 (UTC)

How to enable merge account

Hi how do I enable merger count across all my wikis there is no extension for it 86.171.33.224 (talk) 18:59, 7 May 2013 (UTC)

I don't understand what you mean by "enable merger count". Do you mean that you want some statistics (which ones?) counted across your different wikis? ☠MarkAHershberger☢(talk)☣ 02:20, 8 May 2013 (UTC)

What I mean how do I merge your account on multiple wikis Paladox2014 (talk) 12:53, 8 May 2013 (UTC)

Third-party wikis have to install Extension:CentralAuth, although Manual:$wgSharedDB may be simpler. Jasper Deng (talk) 07:44, 10 May 2013 (UTC)

Ok will it work with different MySQL databases 90.201.14.127 11:48, 10 May 2013 (UTC)

CentralAuth, in my opinion, works best when you don't use database prefixes and you use separate databases. Jasper Deng (talk) 17:09, 10 May 2013 (UTC)

ok is there any instruction on how to install it on to different wikis with different MySQL databases 86.171.33.224 15:43, 11 May 2013 (UTC)

The instructions provided are for multiple MySQL databases. Jasper Deng (talk) 17:35, 11 May 2013 (UTC)

ok 86.171.33.224 10:15, 12 May 2013 (UTC)

Do I put the $shared database on every wiki I want to log in to with one account and o I put the database of the one currently on mywiki and on the other one do I out the one on that one which is on the one I do I put the same one because I am with a free hoster for my website 86.171.33.224 20:36, 12 May 2013 (UTC)

The $wgConf information must be available to all your wikis. Jasper Deng (talk) 20:55, 12 May 2013 (UTC)

how would i enable $wgConf on my wiki do i put it on all my wikis or just mine one 93.93.218.196 12:18, 13 May 2013 (UTC)

because my mysql databse is u733145970_my for my wiki and my other wiki dtabase is different how wouldi get it to work i am currently with a free web host 93.93.218.196 12:22, 13 May 2013 (UTC)

$wgConf has to be put in LocalSettings.php for every single wiki - you should consider making a common configuration file for all of your wikis. Jasper Deng (talk) 17:08, 13 May 2013 (UTC)

Ok so I create the file and I put it on all my wikis Paladox2014 (talk) 18:17, 13 May 2013 (UTC)

How to set up global account on different wiki

Hi could I have some help on setting up global usage for users because I have different MySQL servers and I would like to have user log on with there account without needing to create new one 86.171.33.224 (talk) 19:21, 7 May 2013 (UTC)

It looks like you could use Extension:MediaWikiAuth to send all users to a single wiki to sign up and then use those creds to login.

Another option, of course, is Extension:CentralAuth. You could also look at Extension:LDAP_Authentication, although that does involve an LDAP server. ☠MarkAHershberger☢(talk)☣ 02:25, 8 May 2013 (UTC)

How would I apply the patch it is asking you to on Extension:MediaWikiAuth Paladox2014 (talk) 12:56, 8 May 2013 (UTC)

I have installed it on to my two wikis I havent added the patch because I doint know how to but I installed the extension Mediawiki auth and it doesent let me log in Witt my account from the other wiki could I have some help to let it to log in from the other wiki please Paladox2014 (talk) 13:41, 8 May 2013 (UTC)

What does your error log say? Are you sure you applied the patch correctly? ☠MarkAHershberger☢(talk)☣ 20:09, 8 May 2013 (UTC)

I doint know how to apply the patch 86.171.33.224 21:05, 8 May 2013 (UTC)

Do these instructions help? "Applying patches" on drupal.org ☠MarkAHershberger☢(talk)☣ 00:42, 9 May 2013 (UTC)

No I doint have git 86.171.33.224 06:21, 9 May 2013 (UTC)

If you have access to the command line on your host, you just need patch, not git. If you don't have command line access, we need to do something else. ☠MarkAHershberger☢(talk)☣ 13:12, 9 May 2013 (UTC)

I doint have a command line on my hot Paladox2014 (talk) 20:18, 9 May 2013 (UTC)

What version of MW do you use?

You can patch the file by hand by downloading includes/specials/SpecialUserlogin.php and editing the file by had according to what is in the patch file. Wherever the file as a line that starts with "+ ", you add that line. Where it starts with "- ", you remove that line. The surrounding lines give you context. ☠MarkAHershberger☢(talk)☣ 17:47, 11 May 2013 (UTC)

Well I found a new free host which supports php 5.4 so now I have Mediawiki 1.20.5 86.171.33.224 08:10, 12 May 2013 (UTC)

I now have access to ssh 86.171.33.224 08:11, 12 May 2013 (UTC)

No I doint use git my hosting company is 000webhost 86.171.33.224 06:23, 9 May 2013 (UTC)

What does the patch do 86.171.33.224 06:24, 9 May 2013 (UTC)

I doint have a command line on my host 90.219.251.60 16:13, 9 May 2013 (UTC)

[RESOLVED] - Cannot access our page's content (Error sending mail: authentication failure)

Hi, so we are trying to access the content on our wiki page: prowiki.computerharpoon.com It requires a login to view this content, and we don't seem to have the correct credentials..but when we try to "send new password" I was given the error: Error sending mail: authentication failure [SMTP: Invalid response code received from server (code: 535, response: 5.7.8 Error: authentication failed: PDk0NjIyNzMzNTE1NjE5NjMuMTM2Nzk5MDE2M0BzbXRwMTAucmVsYXkuZGZ3MWE+)]

Is there a way to make this content public? we are just trying to access it once and PDF the pages to archive them.. Or is there a way to actually receive the new credentials for our page?

Thanks in advance for any advice you guys have! 74.192.220.242 (talk) 05:43, 8 May 2013 (UTC)

For making the content public: you might undo Manual:Preventing access#Restrict viewing of all pages. Changing $wgGroupPermissions['*']['read'] = false; to $wgGroupPermissions['*']['read'] = true; should be sufficient.

To receive new credentials, you should fix the email settings that are preventing a correct authentication to the mail server. Ciencia Al Poder (talk) 09:40, 8 May 2013 (UTC)

What file would $wgGroupPermissions['*']['read'] = false; be in? PhPMyAdmin? 74.192.220.242 20:28, 8 May 2013 (UTC)

You would put that in your LocalSettings.php ☠MarkAHershberger☢(talk)☣ 20:33, 8 May 2013 (UTC)

I found it in LocalSettings.php and $wgGroupPermissions['user']['read'] = true; already...but the page is still password protected.

Can I manually change the password to what I need? or what email settings can I change to fix this error? 74.192.220.242 21:11, 8 May 2013 (UTC)

You need to look at how $wgSMTP is set. "authentication failed" sounds like the password there is wrong. ☠MarkAHershberger☢(talk)☣ 00:39, 9 May 2013 (UTC)

[RESOLVED] MediaWiki 1.20.5 LocalSettings.php not found (Mysql installation option not displayed)

I have copied MediaWiki 1.20.5 files to my linux (RHEL 6) server. Mysql database is also created. But when I try to start MediaWiki site by typing the MediaWiki URL in the browser, it shows "LocalSettings.php not found. Please set up the wiki first." When I start following the instructions by clicking the link "set up the wiki first",Mysql option is not displayed although Sqlite option is displayed. Dighosh (talk) 06:08, 8 May 2013 (UTC)

Most likely cause is that PHP is missing mysql support. You probably need to install the php-mysql package. Ciencia Al Poder (talk) 09:45, 8 May 2013 (UTC)

Thanks a lot! I had to install the compatible versions of php-mysql, php-common and php-pdo modules. Now Mysql option is displayed. Thanks again. Dighosh (talk) 06:12, 20 May 2013 (UTC)

.htaccess and sidebar

Hi, my name is Yannick and I'm from Italy. English is not my best :(

I have installed mediawiki 1.20.5 on a website already started. All ok except 2 things:

1) There isn't the .htaccess in any root and I don't know how to create one for this platform; 2) I am going to modify the sidebar but... how? I changed (in localsetting.php) the default skin to "monobook" and if I am going to */wiki/MediaWiki:Sidebar I have a 404 page

Can you help me?

Thank you very much Yannick

Ps: without an administration panel this platform is not exactly easy :) 79.11.0.74 (talk) 11:22, 8 May 2013 (UTC)

Hi Yannick!

To the first question: The file ".htaccess" belongs in the root folder of your wiki. That is the folder, in which you have the folders images/, skins/ or extensions/ and the file LocalSettings.php. If such a file is not there, you can just create it, e.g. create it on your PC and upload it to the wiki server via FTP. Creating a file without name infront of the dot is not possible on Microsoft Windows. What you can do is: Create the file with any name and upload it to your server. On the server, rename the file to ".htaccess".

To the second question: You should be able to access the sidebar just like any other wiki page, e.g. here it is in this wiki: MediaWiki:Sidebar. 88.130.126.133 12:03, 8 May 2013 (UTC)

reset password by senting email

Hi, Current I'm using 1.19 version and I try senting reset password, but not able to?

how can i solve this issue? 220.255.2.100 (talk) 11:39, 8 May 2013 (UTC)

Hi I am not very good at this but I had this problem some time back and a search of the web gave me the below and it worked for me:

Go to phpMyAdmin and select the MediaWiki database from the menu on the left. The page will refresh and the database tables will be displayed on it. Open the SQL tab (located at the top navigation bar).

In the text field write the following SQL query:

UPDATE user SET user_password = MD5( CONCAT( user_id, ‘-’, MD5( ‘NEWPASS‘ ) ) ) WHERE user_id =1

Then click on the GO button to submit the query. If everything goes fine without errors, you should be able to login to MediaWiki with the new password. Ron Barker (talk) 15:59, 8 May 2013 (UTC)

title=Main_Page throwing 404 - cannot access MW

Server: Windows Server 2003 HTTP: IIS 6 MW v: 1.20.5 PHP v: 5.3.8 MySQL v: 5.0.8

• New User

After installation: MW throws a 404. After navigating through some of the code it appears that this is happening when the MW tries to grab the current user or when the data is trying to be pulled from the DB. I have checked the DB and it appears to be empty. All appropriate tables exist... but no data (page/user/tag/query/etc...) 64.126.7.66 (talk) 19:13, 8 May 2013 (UTC)

During installation, did you create a user for MediaWiki? ☠MarkAHershberger☢(talk)☣ 20:26, 8 May 2013 (UTC)

This can happen if the main page hasn't been created. MediaWiki sends a 404 response on pages that don't exist, but the contents is like any other page, and it's perfectly normal, unless your IIS server is intercepting the 404 response and sending it's own 404 error page. If that's the case, see this.

If that's not the issue, maybe the installer failed to properly configure $wgUsePathInfo or $wgArticlePath, etc, specially if you have rewrite rules. Check out the error logs of IIS to see what physical path is trying to access and if it really exists. Ciencia Al Poder (talk) 09:28, 9 May 2013 (UTC)

Reviewing pending changes here on MediaWiki.org

Is there any coordination of people reviewing pending changes here on MediaWiki.org. I made a few changes which are still pending. Seems to be taking quite a while. But I'm not very familiar with Flagged Revisions. Maybe I just have to wait.

My changes were to Extension:NukeDPL and some related pages (see Special:Contributions/Harry_Wood) Maybe for extensions the expectation is that a maintainer of the extension would also be reviewing wiki changes? That's not going to work in this case, because it seems the extension itself isn't very well maintained Harry Wood (talk) 10:44, 9 May 2013 (UTC)

Sorry. Just realised I asked the question in the wrong place. It's over here: Project:Current issues#Reviewing_pending_changes_here_on_MediaWiki.org_27264 Harry Wood (talk) 11:11, 9 May 2013 (UTC)

MW1.20.5 Upgrade

Hello,

I have installed the following Wiki and Extensions Software:

Installed software

Product Version

• MediaWiki 1.19.0
• PHP 5.3.10 (apache2handler)
• MySQL 5.5.20-log

Installed extensions Semantic extensions

• Semantic Drilldown (Version 1.2.4) A drilldown interface for navigating through semantic data Yaron Koren and David Loomer
• Semantic Forms (Version 2.5.2) Forms for adding and editing semantic data Yaron Koren, Stephan Gambke and others
• Semantic MediaWiki (Version 1.8.0.4) Making your wiki more accessible - for machines and humans (online documentation) Markus Krötzsch, Denny Vrandecic, Jeroen De Dauw and others

Special pages

• CategoryTree Dynamically navigate the category structure Daniel Kinzler
• Renameuser Adds a special page to rename a user (need renameuser right)Ævar Arnfjörð Bjarmason and Aaron Schulz
• Parser hooks CategoryTree Dynamically navigate the category structure Daniel Kinzler
• InputBox (Version 0.1.4) Allow inclusion of predefined HTML forms Erik Moeller, Leonardo Pimenta, Rob Church, Trevor Parscal and DaSch
• Wiki Category Tag Cloud (Version 1.1) A Category Tag Cloud derived, improved, and fixed from the YetAnotherTagCloud Extension Daniel Friesen

Other

• Validator (Version 0.5.1) Provides generic parameter handling support for other extensions Jeroen De Dauw
• WikiEditor (Version 0.3.1) Provides an extendable wikitext editing interface and many feature-providing modules Trevor Parscal, Roan Kattouw, Nimish Gautam and Adam Miller

Extension functions efCategoryTree, sffSetupExtension and smwfSetupExtension

Parser extension tags <categorytree>, <describe>, <gallery>, <info>, <inputbox>, <listerrors>, <nowiki>, <pre>, <smwdoc> and <tagcloud>

Parser function hooks

anchorencode, arraymap, arraymaptemplate, ask, autoedit, basepagename, basepagenamee, canonicalurl, canonicalurle, categorytree, concept, declare, defaultsort, describe, displaytitle, drilldownlink, filepath, formatdate, formatnum, forminput, formlink, fullpagename, fullpagenamee, fullurl, fullurle, gender, grammar, info, int, language, lc, lcfirst, listerrors, localurl, localurle, namespace, namespacee, ns, nse, numberingroup, numberofactiveusers, numberofadmins, numberofarticles, numberofedits, numberoffiles, numberofpages, numberofusers, numberofviews, padleft, padright, pagename, pagenamee, pagesincategory, pagesize, plural, protectionlevel, queryformlink, set, set_recurring_event, show, smwdoc, special, subjectpagename, subjectpagenamee, subjectspace, subjectspacee, subobject, subpagename, subpagenamee, tag, talkpagename, talkpagenamee, talkspace, talkspacee, uc, ucfirst and urlencode

In a bug suggested me to download last Wiki version (1.20.5), but I have read that could have problems.

Is possible someone give me guarantee I haven't problems with my extensions in MediaWiki 1.20.5 version ?

I had a lot of problems with Semantic Extension and I don't want to repeat it.

Thank you. Jesus.perez (talk) 18:41, 9 May 2013 (UTC)

Hey Jesus!

If you want to have a secure system, then you could first try an update to 1.19.6. This version is current, updating to it from 1.19.0 is rather easy and you will still get security updates for version 1.19 for a while.

When you want to update to 1.20, you should make a backup first (that is always a good idea). After updating MediaWiki itself, you also need to update the extensions to the version, which is provided for MediaWiki 1.20. Then you will have to test, that all extensions are still working (which might not be the case). Having a look at the Git repo of the Symantic Extension they at least do regular updates. However, no one can guarantee you, that your installation will not be affected by a bug. To know that you must try and see. :-) 88.130.98.96 19:38, 9 May 2013 (UTC)

Customize Title Pagename

Hello,

I want to customize the title of the pagename of my Wiki. Concretly I have activated "$wgUseCategoryBrowser = true;" (Main page > P01 > Page01) in my "LocalSettings.php" and I want to see it in the Title of all my Wikipages. Now I see it at the bottom of the page, after "Categories".

Thank you. Jesus.perez (talk) 18:49, 9 May 2013 (UTC)

See Manual:Skinning/Tutorial. ☠MarkAHershberger☢(talk)☣ 17:56, 11 May 2013 (UTC)

Eliminating Wiki Markup from Search Results

Is there any solution to removing Wiki markup from Search results? 65.122.93.130 (talk) 22:11, 9 May 2013 (UTC)

You may be able to use Manual:Hooks/ShowSearchHitTitle to modify what is displayed. ☠MarkAHershberger☢(talk)☣ 17:41, 11 May 2013 (UTC)

If you understand how hooks work (and thus were able to define this hook that's really not documented), that might work.

For mere mortals who understand a little php, edit includes/search/SqlSearchResult.php, define the function strip_tags_content (as found in the comments for strip-tag), and then use it on mText:

$clean = $this->strip_tags_content($this->mText);

 if ( $wgAdvancedSearchHighlighting ) {

  return $h->highlightText( $clean, $this->terms );

 } else {

  return $h->highlightSimple( $clean, $this->terms );

 }

This ensures that you're stripping out the HTML before the highlighting is applied (or else that would get stripped out too!). It looks like getTextSnippet is only/mostly used for search results, so hopefully the impact is limited there.

Maybe someone will add mortal-level doc on how to use that Hook, though it's been 9 years since this question was asked, so... 76.102.130.155 (talk) 05:32, 24 September 2022 (UTC)

Wiki on Other Computers Do Not Show CSS Style

Hello everyone,

I installed mediawiki 1.20.5 today with a mysql 5.5 database using xampp for apache and python. All the initial configuration and installation went with no errors. When I load the wiki on the hosted machine everything looks perfect. However, on another computer in the office network, none of the css loads so the wiki just shows up as a long text list. Please advise, thank you! 38.104.77.126 (talk) 05:40, 10 May 2013 (UTC)

Hello,

Check out Manual:Errors and symptoms#The wiki appears without styles applied and images are missing Ciencia Al Poder (talk) 09:52, 10 May 2013 (UTC)

Customize Category pages

Hello,

For customizing Category Pages I need to modify php file? There are others possibilities?

Thank you. Jesus.perez (talk) 07:48, 10 May 2013 (UTC)

If you know, or learn, CSS and/or JavaScript, you can customize the look of category pages with them, adding the code at the pages listed in Manual:Interface/Stylesheets and Manual:Interface/JavaScript. Ciencia Al Poder (talk) 09:56, 10 May 2013 (UTC)

Random page from certain category?

Can I use Special:Random to show pages from a certain category?
As I understand from Help:Random page I can only show pages from a certain namespace, not category...

Thanks! Stefahn (talk) 10:22, 10 May 2013 (UTC)

See Extension:Random In Category. ☠MarkAHershberger☢(talk)☣ 17:38, 11 May 2013 (UTC)

Thanks. I will check this out. Stefahn (talk) 08:49, 12 May 2013 (UTC)

Load User group CSS for anons

Is it possible to load a User group CSS file for anons via Manual:User group CSS and Javascript ?
The manual says it's not possible to load a CSS file for User group *.

Up to now I use a hack to do this - a User group CSS file would be better I think... Stefahn (talk) 10:40, 10 May 2013 (UTC)

You should make a feature request on Bugzilla: http://bugzilla.wikimedia.org/ ☠MarkAHershberger☢(talk)☣ 17:36, 11 May 2013 (UTC)

Still getting User spam even after disabling registration

Hello,

I'm hoping someone can help me find why this is happening. I get hundreds of fake User: pages created daily so after removing my extensions and trying several captchas, I finally just disabled registration. However, I'm still getting tons of fake user pages.

Does anyone have an idea of how this could be happening? I think I may have a security hole or something but I'm just not sure. Any help/suggestions would be appreciated.

MediaWiki 1.20.4 PHP 5.3.24 (cgi-fcgi) MySQL 5.5.30-cll-lve

mediawiki URL: wikitardia.com

Thanks! Steve 66.55.20.18 (talk) 13:22, 10 May 2013 (UTC)

Hi Steve,

checking your Special:Version page, the extension "AWC`s MediaWiki Forum" is still installed. Try if uninstalling it helps.

Note that security issues in extensions might still be exploitable, also when the extension has already been uninstalled. If you want to be really on the safe side, you might want to actually delete the extension from the server.

You say that new user pages are created. This is still possible, also after you deactivated registration. Or do you mean that new users can still register? 88.130.119.222 13:30, 10 May 2013 (UTC)

Hi Thanks for the quick reply.

I will try removing that extension as well although that ext was installed recently and I was having this problem even before installing it. I'll see if there are other extentions I need to remove from the server.

Yeah it seems to be new user pages (see screenshot)

http://screencast.com/t/ZreSzUfmKqK

I assume this is different than new users so disabling registration would not fix this? (sorry for the noob questions) 66.55.20.18 13:54, 10 May 2013 (UTC)

Yep still getting those user pages even after removing those extensions.

I'm always seeing an index.php page created as well.

http://screencast.com/t/T1atzsNVdXr

I just keep deleting and deleting... 66.55.20.18 14:57, 10 May 2013 (UTC)

• I just tried to register at your wiki; registration really is disabled.
• This index.php, which you see there is only a normal page in your wiki. As a registered user, you can create it like any other page.
• Yes, creating a user page is something different than creating a user (= a user account).
• Your registration log does not show new users since April 29th. That looks good (if this information is correct).
  • Please check in the your database the table "user". Sort the rows by "user_id". What does the row with the highest id contain? Especially the username and the content of the field "user_registration"? 88.130.119.222 15:11, 10 May 2013 (UTC)

Yea it seems to be user pages that are being created rather than new users. Is there anyway to stop these fake user pages? I'm getting several hundred per day and deleting them with the Nuke extension.

Here's an example of some that were created in just the last few minutes:

http://screencast.com/t/Q2lzy2ykyg

http://screencast.com/t/zIpXhxgxNUc

Thanks again for all your help! 66.55.20.18 15:17, 10 May 2013 (UTC)

Ok, if that is all, it does not look like a hack, but just like "ordinary" spam.

Yes, there for example is the extension Deleteuser. However, this may damage your database. Better would be User Merge and Delete, which also allows you to remove user accounts. You just have to merge them to "no account", which will remove them. 88.130.119.222 15:22, 10 May 2013 (UTC)

Extension:User Merge and Delete won't work for this since it renames/deletes user accounts, not userpages with unexisting user account,

To stop new spam userpage creation, you can apply some of the options listed in Manual:Preventing access, from restricting page editing on the User: namespace for unregistered users, or restricting edits on all pages for unregistered users and force them to create an account (with Extension:ConfirmAccount). Extension:AbuseFilter can also be helpful preventing those edits, but you should learn how to create a filter for that kind of edits. Ciencia Al Poder (talk) 18:06, 11 May 2013 (UTC)

He already mass-deletes the pages with Nuke. Unregistered users also are no problem in this case; why should you only remove the spam while leaving the spammers there, always being in danger that they could return when instead you could also delete them making it impossible for them to create new pages or do anything else? 88.130.88.226 21:35, 11 May 2013 (UTC)

I had a similar problem. I first prevented access to create new spam accounts with Extension:ConfirmAccount. Then I deleted all spam accounts (about 50,000 of them). And then I started cleaning up all the pages that were created by these spam accounts (about 35,000 pages).

It is true that only preventing spam accounts to be created, doesn't prevent existing spam accounts from adding new pages or altering existing pages. Therefore it is important to delete spam accounts as soon as possible. Patrick Vanhoucke (talk) 22:27, 11 May 2013 (UTC)

rev_id in revision table is very very loosely packed

Our wiki has about 600,000 rows in our revision table, but somehow has gotten to a point where our max(rev_id) is 1.7b which makes the php scripts for updating links etc very, very, very slow and sort of discourages the update process. we are running MW 1.20

I'm just curious if there is a safe fix for this of if I need to grin and bear it.

sean http://www.baseball-reference.com/bullpen/ 76.99.118.65 (talk) 15:33, 10 May 2013 (UTC)

What do you mean with "our max(rev_id) is 1.7b"?

You can remove old revisions from the table by using the deleteOldRevisions.php script. However, this will influence page history (as these revisions will then no longer be there). Maybe you could also compress the content in that table, however, this will not reduce the number of rows.

If all doesn't help you can update your links via a cron job, e.g. every Friday at 2 a.m. The performance decrease during that time should not hurt your users much. ;-) 88.130.88.226 12:58, 11 May 2013 (UTC)

We have only 600,000 actual revisions in the table, but for some reason the max(rev_id) = 1,700,000,000

Running update links with a max rev_id that high takes about 10 hours because it is going from 0 to 1,700,000,000 by 1,000's. 76.99.118.65 17:27, 13 May 2013 (UTC)

I see. The unused revion numbers can have several reasons: Maybe a script like deleteOldRevisions.php has been used in the past, which left these holes. Or you had spam and mass-deleted those entries permanently or or or. However, I don't know of a way to reduce the values of rev_id without loosing referential integrity. 88.130.120.134 22:05, 13 May 2013 (UTC)

Thanks, that is what I was afraid of. A quicker route I guess might be to revise the update scripts to handle these cases. 76.99.118.65 12:55, 14 May 2013 (UTC)

If you find something in the update scripts, which is superfluous, don't hesitate to make a patch, which removes it. However, there won't be a sleep(2), which you just remove and the issue will be solved. ;-) 88.130.123.15 02:56, 20 May 2013 (UTC)

magic quotes runtime

Hi,

When I instal mediawiki, I get a warning that magic_quotes_runtime should be turned off. If I check my php.ini file, it is clearly marked 'Off'. My version of php is PHP 5.3.3-7. Has anyone had this problem before?

Thanks in advance, Jelle 109.130.234.250 (talk) 15:40, 10 May 2013 (UTC)

Maybe it is not this php.ini file, which finally sets the value. Check the output of phpinfo() to see, what the value actually is. 88.130.119.222 16:51, 10 May 2013 (UTC)

Error migrating mediawiki built with php5.2 to server with php5.3

Mediawiki version: 1.14.0 PHP version: 5.2.5 (apache2handler) MYSQL Version: 5.0.26 OS: SUSE Enterprise Linux Server 10

Hi,

I have a mediawiki built with the above specifications. It is working very perfectly on the current server where it is. However, the server is old as well as the versions of PHP and MYSQL. The mediawiki is in the process of being moved over to a new MAC OS X 10.7 Server with PHP 5.3.15(apache2handler) and MYSQL 5.5.25a-log.

The problem

After successful migration of both the mediawiki site and databases, the pages of the mediawiki cannot be edited and always comes up with the error below

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 "Revision::insertOn". MySQL returned error "1048: Column 'old_text' cannot be null (localhost)".

I was able to fully confirm it was not a database error since the mediawiki works well on MAMP when php 5.2.17 is selected from the preferences and still running well on the SUSE server.

Question

1) How can I upgrade the current mediawiki installation version to more recent versions such as 1.20.4 which works well with php5.3?

2) What steps can I take to achieve this please?

The mediawiki is being moved to a Mac OS X 10.7 Lion Server with PHP 5.3.15(apache2handler) and MYSQL 5.5.25a-log. I have tried different things such as installing mediawiki 1.20.4 and then dropping the tables and importing the tables from the .sql database dump of the old mediawiki 1.14.0 to the 1.20.4 but that did not work at all. I have also tried changing some lines (where the error is being reported) in the main .sql database file of the mediawiki but did not work. I know however that the reason it won't work was because this old version of mediawiki is not compatible with php 5.3 and not a database issue.

I have also tried to manually move some installation folders folders from mediawiki 1.20.4 to the old 1.14.0 to upgrade it but that did not work. I have also ran the /maintenance/update.php script severally but it won't update the 1.14.0 to 1.20.4 or later. I have been trying different things for weeks now but to no avail. Please I need a solution as this is the last stage of the our website migration process at work.

This help and solution will be highly beneficial and appreciated.

Thanks. Kuxy09 (talk) 16:14, 10 May 2013 (UTC)

For information on how to upgrade your wiki see Upgrade.

You should not have to change anything with the old database. Import the complete DB on the new MySQL server, update MediaWiki and run the database updater. Afterwards maybe you still have to update some extensions, but things should work then. :-) 88.130.119.222 20:42, 10 May 2013 (UTC)

On starting MediaWikik - server not found

Hi all,

Just installed MediaWiki on Godaddy. An email confirming successful installation has been received stating; MediaWiki is ready.

MediaWiki 1.20.4 is installed and ready for your personal touch. MediaWiki login: http://wiki.satimis.com/mwsat/ Hosting account: Log in ....

MediaWiki is installed on /wiki.satimis.com/mwsat/

But on browser running http://wiki.satimis.com/mwsat/ it popup "Server not found". index.php is on /wiki.satimis.com/mwsat/

Please help. TIA

B.R. satimis Satimis (talk) 17:42, 10 May 2013 (UTC)

You need to talk to GoDaddy support. I'm getting a 404 on that page, so it looks like they haven't installed it. ☠MarkAHershberger☢(talk)☣ 17:34, 11 May 2013 (UTC)

Problems resetting password via e-mail reset

Howdy,

I inherited a wikips.tamu.edu, a mediawiki site that was running version 1.6. Users could only access the site when they used the "forgotten your login details" link to generate a temporary password, login with the temp password, enter a new password and then are logged in to the Wiki. However, once users logout, they can not login again with the new password they set, or the emailed password either. the error is "incorrect password entered"

I have updated the site to MediaWiki 1.20.5 and did not update PHP 5.4.7 (apache2handler) or MySQL 5.5.27 and the password problem followed along. We are running XAMPP on Windows 2008R2.

The database is updated and new users can be created, everything is working fine except for this password issue. I have tried manually changing passwords using php.

php changePassword.php --user=example --password=newpassword

and using sql both Salted

 UPDATE `user` SET user_password = CONCAT(':B:somesalt:', MD5(CONCAT('somesalt-', MD5('somepass')))) WHERE user_name = 'someuser';

and unsalted

 UPDATE `user` SET user_password = CONCAT(':A:', MD5('somepass')) WHERE user_name = 'someuser';

disabled and enabled password salting in the localsettings.php file.

If I use the user_newpassword field instead of the user_password field in the sql requests, I can login once with the password set with sql, but it makes me change my password and I can' login again.

This issue applies to both new users added after the 1.2 update and existing users before the 1.2 update. here is the localsettings.php

<?php

# This file was automatically generated by the MediaWiki installer.
# If you make manual changes, please keep track in case you need to
# recreate them later.
#
# See includes/DefaultSettings.php for all configurable settings
# and their default values, but don't forget to make changes in _this_
# file, not there.
#
# Further documentation for configuration settings may be found at:
# http://www.mediawiki.org/wiki/Manual:Configuration_settings

# If you customize your file layout, set $IP to the directory that contains
# the other MediaWiki files. It will be used as a base to locate files.
if( defined( 'MW_INSTALL_PATH' ) ) {
	$IP = MW_INSTALL_PATH;
} else {
	$IP = dirname( __FILE__ );
}

$path = array( $IP, "$IP/includes", "$IP/languages" );
set_include_path( implode( PATH_SEPARATOR, $path ) . PATH_SEPARATOR . get_include_path() );

require_once( "$IP/includes/DefaultSettings.php" );

# added for admin approval before accounts created
require_once("$IP/extensions/ConfirmAccount/ConfirmAccount.php");

# added for ApproveRevs extenion
require_once("$IP/extensions/ApprovedRevs/ApprovedRevs.php");

if ( $wgCommandLineMode ) {
	if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
		die( "This script must be run from the command line\n" );
	}
}
## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;

$wgSitename         = "ProcessSafetyWiki";

## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs please see:
## http://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath       = "";
$wgScriptExtension  = ".php5";
## The relative URL path to the skins directory
$wgStylePath        = "$wgScriptPath/skins";

## The relative URL path to the logo.  Make sure you change this from the default,
## or else you'll overwrite your logo when you upgrade!
$wgLogo             = "http://wikips.tamu.edu/images/psclogo.JPG";

## UPO means: this is also a user preference option

$wgEnableEmail      = true;
$wgEnableUserEmail  = true; # UPO

$wgEmergencyContact = "webmaster@psc.che.tamu.edu";
$wgPasswordSender = "webmaster@psc.che.tamu.edu";

$wgEnotifUserTalk = true; # UPO
$wgEnotifWatchlist = true; # UPO
$wgEmailAuthentication = true;

## Database settings
$wgDBtype           = "mysql";
$wgDBserver         = "localhost";
$wgDBname           = "XXXXXXX";
$wgDBuser           = "XXXXXXX";
$wgDBpassword       = "XXXXXXX";

# MySQL specific settings
$wgDBprefix         = "mw_";

# MySQL table options to use during installation or update
$wgDBTableOptions   = "ENGINE=InnoDB, DEFAULT CHARSET=binary";

# Experimental charset support for MySQL 4.1/5.0.
$wgDBmysql5 = true;

## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = array();

## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads       = true;
# $wgUseImageMagick = true;
# $wgImageMagickConvertCommand = "/usr/bin/convert";

## If you use ImageMagick (or any other shell command) on a
## Linux server, this will need to be set to the name of an
## available UTF-8 locale
$wgShellLocale = "en_US.utf8";

## If you want to use image uploads under safe mode,
## create the directories images/archive, images/thumb and
## images/temp, and make them all writable. Then uncomment
## this, if it's not already uncommented:
# $wgHashedUploadDirectory = false;

## If you have the appropriate support software installed
## you can enable inline LaTeX equations:
$wgUseTeX           = false;

## Set $wgCacheDirectory to a writable directory on the web server
## to make your wiki go slightly faster. The directory should not
## be publically accessible from the web.
#$wgCacheDirectory = "$IP/cache";

$wgLocalInterwiki   = strtolower( $wgSitename );

$wgLanguageCode = "en";

$wgSecretKey = "d19ead04a5b64a61c2e9a371b7907d12b04871f1919d08786e867ee305164cc1";

## Default skin: you can change the default skin. Use the internal symbolic
## names, ie 'vector', 'monobook':
$wgDefaultSkin = 'monobook';

## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
$wgEnableCreativeCommonsRdf = true;
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsUrl = "http://creativecommons.org/licenses/by-nc-sa/3.0/";
$wgRightsText = "Attribution-NonCommercial-ShareAlike 3.0 Unported";
$wgRightsIcon = "http://i.creativecommons.org/l/by-nc-sa/3.0/88x31.png";
# $wgRightsCode = "[license_code]"; # Not yet used

$wgDiff3 = "/usr/bin/diff3";

# When you make changes to this configuration file, this will make
# sure that cached pages are cleared.
$wgCacheEpoch = max( $wgCacheEpoch, gmdate( 'YmdHis', @filemtime( __FILE__ ) ) );

# require_once("$IP/extensions/FCKeditor/FCKeditor.php");
# $wgFCKEditorToolbarSet   = "Default";

$wgGroupPermissions['*']['read']             = false;
$wgGroupPermissions['*']['edit']             = false;
$wgGroupPermissions['*']['edit']             = false;
$wgGroupPermissions['*']['createpage']       = false;
$wgGroupPermissions['*']['createtalk']       = false;
$wgGroupPermissions['*']['writeapi']         = false;
$wgWhitelistRead = array ("Special:Userlogin", "Special:RequestAccount", "ProcessSafetyWiki:Terms_of_Service", "Help:Contents");

require_once("extensions/table-tab.php");
require_once("extensions/def-tab.php");

$wgFileExtensions = array_merge( $wgFileExtensions, array( 'pdf' ) );

//require_once( "$IP/extensions/WikiEditor/WikiEditor.php" );

require_once("$IP/extensions/WYSIWYG/WYSIWYG.php");

# Register the MobileSkin extension
//require_once("$IP/extensions/MobileSkin/MobileSkin.php");


## Default skin: you can change the default skin. Use the internal symbolic
## names, ie 'vector', 'monobook':
if (preg_match("/(mobile|webos|opera mini)/i", $_SERVER['HTTP_USER_AGENT'])) {
    $wgDefaultSkin = 'wptouch';
} else {
    $wgDefaultSkin = 'monobook';
}

Any ideas how to fix this issue without starting over from scratch?

Thanks

Jeff

Jeff Polasek 165.91.142.153 (talk) 21:44, 10 May 2013 (UTC)

It doesn't look like you have any setting for $wgServer. Is it possible that is being assigned the wrong value? ☠MarkAHershberger☢(talk)☣ 17:28, 11 May 2013 (UTC)

Hi Mark,

I tried setting the $wgServer in the localsettings file but this did not help. It seems like the change password process is using the wrong hash to create the password.

Thanks

Jeff 165.91.142.153 18:23, 13 May 2013 (UTC)

I just reproduced the problem on your wiki. I wonder if it might be one of the extensions you have installed. I'm wondering if you disable ConfirmAccount briefly to test this if it will work. ☠MarkAHershberger☢(talk)☣ 22:00, 13 May 2013 (UTC)

[RESOLVED] Missing "Continue --->" button during installation wizard

Hi,

I have an issue where i cant proceed to "Connect to database" wizard due to missing "Continue" button after the below message appeared.

Welcome to MediaWiki!

Environmental checks Basic checks are performed to see if this environment is suitable for MediaWiki installation. You should provide the results of these checks if you need help during installation. PHP 5.3.3 is installed. GNU diff3 not found. Found GD graphics library built-in. Image thumbnailing will be enabled if you enable uploads.

More details of snapshot, please visit http://gyazo.com/8314dac37f53bdf89b77f83bfa264cfe.

I'm running: - CentOS release 6.4 (Final) - MediaWiki 1.20.5 - PHP Version 5.3.3 - mysql Ver 14.14 Distrib 5.1.67, for redhat-linux-gnu (x86_64) using readline 5.1 - zpanel

Please help.

Thanks. Chickobueno (talk) 05:05, 11 May 2013 (UTC)

Hi!

Do you get a PHP error? If I remmber correctly the page should continue at this point: Not only with a button, but also with some more text, e.g. on Unicode support in PHP. This information seems to be missing already as well. 88.130.88.226 10:10, 11 May 2013 (UTC)

Hi,

There is no PHP error as I gone through the installation wizard. I have also downgraded the installation files to 1.17 but have no luck so far.

The PHP version seems to be fine at this stage where its run on version 5.3.3.

Thanks. Chickobueno (talk) 07:42, 12 May 2013 (UTC)

I'm very interested to hear about any progress you make on this. I too am having a similar issue and just posted a new thread (not seeing yours here).

At the bottom of my pre-check stage, I get all the way through, even get the message "You can successfully install Mediawikia", but THEN also have displayed a "Fatal Error: Out of Memory" message, and no Continue button to take me to the database config screen.

Oddly, someone replied to my post saying they were actually able to hit my install URL, and proceed without error to the DB config step.

I'm am very perplexed by this (and your somewhat similar sounding issue). It almost seems like there are browser compatibility issues with the pre-check install scripts. But I wouldn't think that was possible in this way with PHP, being server-side.

Anyway, sorry for the ramble, just wanted to chime in that I too am having odd behavior at the very end of the pre-check step.

Good luck-

JWeicher 64.43.232.10 14:55, 13 May 2013 (UTC)

Activate PHP error reporting and see again. I am pretty sure there is a PHP error. Otherwise there would be no reason why the output should suddenly stop.

Btw. this one looks similar to the problem in ""Fatal Error: Out of Memory" During Installation". However, without knowing what is happening on your machine, it's only guessing. 88.130.120.134 15:20, 13 May 2013 (UTC)

I just ran into this same problem. I fixed it by logging into zpanel as zadmin, going to Admin -> Module Admin -> Apache Config, go to the section "Suhosin Value", look for the words "passthru" and "escapeshellargs", remove them, then go to Admin -> zpanel Config, then click the Go button next to "Run daemon now" to reload the configs.

The continue button should be there now. 67.9.143.112 17:45, 2 April 2014 (UTC)

Still having this issue after trying the fix above. Any other leads? 69.70.183.150 15:03, 23 June 2014 (UTC)

Did you activate PHP error reporting? What error message do you get? Ciencia Al Poder (talk) 11:15, 24 June 2014 (UTC)

Cleaning up externallinks table

I'm looking for a way to find and delete all records in the externallinks table with a page identifier el_from that doesn't exist as a page_id in the page table.

I'm having:

• MediaWiki 1.19.1
• PHP 5.3.21-1
• MySQL 5.1.61

I'll explain why I want to do this.

I'm running a fairly new wiki about genealogy in Brussels (Belgium). A few days ago, the wiki was under attack and about 50,000 spam accounts were created. This was due to the fact that anyone could create his own account without a bureaucrat or administrator having to approve it (my mistake, it's the very first wiki ever I installed).

I took away the initial cause of the problem by installing Extension:ConfirmAccount. That seems alright, no new (spam) accounts have been created since.

Now I'm working on cleaning up the database. I'm doing this with phpMyAdmin, directly into the MySQL itself, since I couldn't find any MediaWiki extension that not only removes the spam accounts, but also all other data (in other tables) related to them (e.g. the spam accounts created pages, user pages and all other sorts of data in quite a few tables). I do know little about MySQL and PHP, but let's say I have sufficient insight to proceed in a reasoned way.

To clean up the mess, I go through all the tables and I remove records related to the spam accounts. Luckely, the wiki is fairly young and only two real user accounts exist, so I could filter on user_id to remove the spam accounts in the user table itself, and filter on foreign keys to remove related records in all other tables. After removing large portings of records from a table, I defragment and optimize the table. Although still time consuming, this seems to work fine and I believe I didn't mess up things.

Now I'm at the stage that only two more tables should be cleaned up. These are the page table and the externallinks table.

There are about 35,000 spam records in the page table, I will have to manually remove them by sight, since there is no formal criterion to tell if a page is real or spam. But spam pages are grouped in large chuncks, so this simplifies the process a bit.

The externallinks table contains about 200,000 links. There's no way to clean up the table manually by sight, because I can't always tell which link is real and which is spam (even if I could, this process would be very error-prone). So, this is why I'm looking for a way to find and delete all records in the externallinks table that refer to non-existent / no longer existing pages in the page table.

Thank you in advance! Kind regards. Patrick Vanhoucke~mediawikiwiki (talk) 08:00, 11 May 2013 (UTC)

Hi Patrick,

I cannot help you directly, but I know that what you want is possible. It is a MySQL question: In table "externallinks" you have the column "el_from", which contains the number of the refering wiki page; this should be the "page_id" from the "page" table.

What you need is a query, which returns all rows from externallinks, which have a number in el_from, which is not present in page_id. 88.130.88.226 13:03, 11 May 2013 (UTC)

Please note that modifying or altering stuff directly on the database may produce inconsistencies and cause errors on some pages, specially page histories or user contributions.

For fixing the externallinks table, simply run refreshLinks.php Ciencia Al Poder (talk) 19:31, 11 May 2013 (UTC)

Ha, Ciencia is right! I also checked Manual:refreshLinks.php and it did mention soe tables, but it did not mention externallinks... I have just made that more clear. :-) 88.130.88.226 21:30, 11 May 2013 (UTC)

Thank you for rephrasing my question.

I checked Manual:refreshLinks.php and this indeed seems to delete records in the externallinks table that refer to non-existing id's in the page table. So, I'll have to delete all unwanted pages first, and then run refreshLinks.php.

I'm aware of the fact that modifying the database directly may produce inconsistencies. But because in this case the wiki was under heavy spam attack, I think there is no other way. I couldn't find any extensions that make this kind of maintenance (deleting all unwanted spam users and all related data entries in other tables) possible.

Now, since I'm a newbie vis-à-vis PHP and MySQL, how do I run refreshLinks.php? Or rather, where do I run refreshLinks.php from? My browser? Or phpMyAdmin? Or do I need something like PuTTY to perform a SSH connection? If I try it from my browser, it says that I don't have permission to access the file on the server, although I am logged in as a bureaucrat / administrator.

Thanks again for your kind assistance. Patrick Vanhoucke (talk) 21:59, 11 May 2013 (UTC)

> So, I'll have to delete all unwanted pages first, and then run refreshLinks.php.

Yes.

You run refreshLinks.php from the command line, meaning from the Shell. If the PC you are currently sitting at uses Microsoft Windows you will need PuTTy to connect to your server in order to get to the command line. Then you navigate to the folder with cd commands and execute the file with php refreshLinks.php or similar. 88.130.88.226 00:44, 12 May 2013 (UTC)

After downloading and trying to use PuTTY, I'm a little bit lost. I filled out host name etc. and finally could open the command line screen (at least, that is what I believe it is). But the server isn't asking any login name or password.

I'm already using FileZilla as an FTP client. Can't I just as well use FileZilla to execute php files from command line? Sorry for asking, but I'm new in these kind of things. Patrick Vanhoucke (talk) 08:08, 12 May 2013 (UTC)

Hi Patrick,

no, you cannot use an FTP programme (like FileZilla) to access the command line. :-(

You might be able to set up a cron job to run the script, but if that is possible depends on your server and your host; maybe it is not.

Putty is the right way. If Putty did not gicve you an error message (popup window with some error text), then I would say you did things right. The "command line screen" basically is a black window with some lines of white text in it: Some information about the server, maybe a copyright notice, a kind of a system string. And you should be able to type things, which then appear on the last text-line of this screen.

Is that what you see? 88.130.110.67 12:47, 12 May 2013 (UTC)

I do get the black (DOS-like) window, but there's no text and I can't type anything. The title bar of the screen shows the Host Name of the server that I added in PuTTY Configuration. I filled out my username in PuTTY Configuration > Connection > Data. Patrick Vanhoucke (talk) 13:13, 12 May 2013 (UTC)

No text at all; maybe your host does not offer SSH access to the server? However, here is a how to: Manual:Maintenance_scripts, on what you can do and what you should see.

If things don't work via the command line, you can try using one of the extensions, whih are mentioned on that page. 88.130.110.67 13:24, 12 May 2013 (UTC)

Could it be that I need a SSH-key? When I go to my hosts Controlpanel, it says that there are no SSH-keys and that I will need such a key to login via SSH. I suppose I have to generate such a key myself and then add it via Controlpanel and use the same key in PuTTY. Right?

I did take a look at the maintenance extensions, but as far as I can see, the refreshLinks.php is not included. One of the extensions mentions a way to add as many maintenance scripts as you like, but I don't really understand how I should do that. Patrick Vanhoucke (talk) 13:35, 12 May 2013 (UTC)

> Could it be that I need a SSH-key?

Maybe; that depends on how the server is configured...

> When I go to my hosts Controlpanel, it says that there are no SSH-keys and that I will need such a key to login via SSH.

So you WILL need them to use SSH.

> I suppose I have to generate such a key myself and then add it via Controlpanel and use the same key in PuTTY. Right?

Yes. 88.130.110.67 18:26, 12 May 2013 (UTC)

Changes only visible after repeated login

Hi,

all changes I make to a page or to the navigation are saved but only visible after a logging out and log back in again.

What could be the reason for that?

Thanks

Toby 2A02:8071:28E:7C01:A564:2B8C:1175:136B (talk) 16:20, 11 May 2013 (UTC)

Probably a caching issue. Try changing the file and then clear your cache. ☠MarkAHershberger☢(talk)☣ 17:15, 11 May 2013 (UTC)

[help] extension Echo

hi how do I get extension Echo to work on my website ive installed it and it has the link at the top of my website but just a plain link I would like the look like Wikipedia Echo 86.171.33.224 (talk) 14:51, 12 May 2013 (UTC)

How does it not look like the Echo installed on Wikipedias? Do you have a screenshot or a link or something? Krenair ^{(talk • contribs)} 15:47, 12 May 2013 (UTC)

ok I will upload a photo of it not showing correctly here is the link to the image 86.171.33.224 19:56, 12 May 2013 (UTC)

I think you want to set $wgEchoShowFullNotificationsLink to false. (false is the default, just remove the override from your config.) Krenair ^{(talk • contribs)} 16:11, 13 May 2013 (UTC)

Ok so do I add it to my local settings or which file in the extension do I edit Paladox2014 (talk) 18:18, 13 May 2013 (UTC)

That doesent make it show like the Wikipedia notification does Paladox2014 (talk) 18:39, 13 May 2013 (UTC)

It'd help if you gave more info about your setup, such as the version of MediaWiki you are running. TK-999 (talk) 20:03, 23 May 2013 (UTC)

I am running version 1.20.5 and website link is http://random-wikisaur.tk 86.168.53.89 06:24, 24 May 2013 (UTC)

Do you regularly update the extension with Git? TK-999 (talk) 11:15, 24 May 2013 (UTC)

No I used the screenshot download should I download it through git 94.0.34.97 13:37, 24 May 2013 (UTC)

This is an extension under active development; you can either regularly update with the tarballs or keep a git repo in sync to keep it up-to-date. Try and see if updating helps. TK-999 (talk) 13:50, 24 May 2013 (UTC)

Hi I have managed to get it working on my other wiki running the beta or alpha version of Mediawiki 21 it now shows better but how can I get it to when you click on the grey square next to your user name to show your notification without go onto the notification page should I update it to Mediawiki 1.22 does it work better with that one then Mediawiki 1.20 and 1.21 94.0.34.97 14:25, 24 May 2013 (UTC)

hi I have an image to help File:Notifications-Flyout-Screenshot-Closeup-04-30-2013.png it shows the grey swure at the top but doesent show the grey and white box when clicked it goes to 94.0.34.97 14:42, 24 May 2013 (UTC)

how do I enable notification flyout 2.218.19.225 21:49, 24 May 2013 (UTC)

how can I enable flyout on echo because when I click the grey badge it goes to the special notification page so I would like it when you click on it a box comes out please 90.215.249.160 16:33, 31 May 2013 (UTC)

Instead of bumping this thread, you may try asking on the extension's talk page. Ciencia Al Poder (talk) 09:49, 6 June 2013 (UTC)

extension Wikibase

hi I seem to have a problem with extension wikibase I have a problem in wikibase lib the error says

Warning: array_key_exists() expects parameter 2 to be array, null given
  in .../extensions/Wikibase/lib/WikibaseLib.php on line 202

Warning: array_key_exists() expects parameter 2 to be array, null given
  in .../extensions/Wikibase/lib/WikibaseLib.php on line 202

Fatal error: Class 'Wikibase\TemplateStore' not found
  in .../extensions/Wikibase/lib/WikibaseLib.php on line 221

could I please have some help to fix the error Paladox2014 (talk) 20:05, 12 May 2013 (UTC)

"Fatal Error: Out of Memory" During Installation

I am seeing a strange "Fatal Error: Out of Memory" during the installation process of MW. It seems to occur right at the end of the pre-checks step, and even *after* saying I can successfully install MW (The "Next" buttons never get a chance to render for this step.)

I say it is strange because in an attempt to address it myself, I have already gone through the process of incrementally adjusting my PHP memory limit upwards in php.ini (I've gone all the way up to 512MB, and even 1GB!), and with each increase in memory I still get the error, but it's like the install script gets a little further and then throws the same error from within a different install-related php file.

The output of my pre-check is:

Welcome to MediaWiki!


Environmental checks
Basic checks are performed to see if this environment is suitable for MediaWiki installation. You should provide the results of these checks if you need help during installation.
PHP 5.3.3-7+squeeze14 is installed.
Warning: Could not find APC, XCache or WinCache.
Object caching is not enabled.
Found ImageMagick: /usr/bin/convert.
Image thumbnailing will be enabled if you enable uploads.
Using server name "http://family.weicherworld.com".
Using server URL "http://family.weicherworld.com".
Warning: The intl PECL extension is not available to handle Unicode normalization, falling back to slow pure-PHP implementation.
If you run a high-traffic site, you should read a little on Unicode normalization.
The environment has been checked.
You can install MediaWiki.
Fatal error: Out of memory (allocated 24379392) (tried to allocate 258 bytes) in /home/vg011web00/55/31/2923155/web/family/languages/Language.php on line 2833

As I mentioned, the file in which the error is thrown would change (here it's Language.php) as I increase the memory_limit parameter in php.ini. And when I look at the offending file/line it appears to be "require" statements. So it's like increasing the memory limit lets this step get further but still ends up failing.

I am trying to install MW 1.19.6, using PHP 5.3.3-7+squeeze14 (I'll also be using MySQL, but I haven't gotten that far in the process obviously. I had started with the most current stable version of MW (1.20.5 I think?) but after seeing the same issue though trying to install a slightly older version might avoid the problem.

I will admit I'm new to MediaWiki and PHP, but I've tried to read up at least a little. Would APC or one of the other object-caching capabilities help me here if it's a memory issue? It didn't seem required.

Any recommendations would be highly appreciated.

Thanks JWeicher 64.43.232.10 (talk) 13:49, 13 May 2013 (UTC)

Hi!

I don't know if/what you have changed, but I just tried going through the Installation process on your server and I could get past the step at which you say you always got the error. E.g. I saw the database selection screen.

It seems to be working now.

You might now try starting with 1.20.5; this will save you an update in a few months. :-) 88.130.120.134 14:06, 13 May 2013 (UTC)

Whoa - are you serious?

Thanks for the information! That makes me wonder now - can any of this be *browser* related? Like something on my personal end affecting the installation (browsers, etc), and not my hosting server itself? I though PHP is completely server-side so I wouldn't think so.

Because that is utterly bizarre - after seeing your reply, I went and tried it again with Chrome, IE and Firefox just to eliminate that possibility, and I still get the same error at the same point.

Any other suggestions? I do appreciate your input!

JWeicher 64.43.232.10 14:16, 13 May 2013 (UTC)

> Whoa - are you serious?

Absolutely. :-)

Hmm, no you should not be able to cause a PHP error like that just because you use another browser. Btw I tested that with Firefox, newest version, AdBlock Plus and NoScript installed, nothing special.

Maybe it is a language problem? You also say the errors also popped up in Language...php. I tried it with German.

Ha, and I get the error when I use English as well! Then I clicked back and forth a bit in the browser history and then suddenly it also worked with English. 88.130.120.134 15:17, 13 May 2013 (UTC)

Well, I want to thank you again for your input - I appear to have successfully installed!

In your last response you mentioned that you went back and forth at that point using the browser history buttons. I will admit I had been afraid to do that as I didn't know what sort of temporary files were being created, used, etc as part of the install process, and didn't want to muck up anything during the install

But seeing as you did it, I gave it a shot and it worked! I simply hit "back" on the erroring pre-check page, which really just reloaded the same page, but this time with some additional output and a continue button. I was able to proceed on through the rest of installation/db-config, etc, with no errors.

So this one is still a mystery, but your comment help me proceed and finish.

Thanks again for your input!

JWeicher

By the way, how can I mark this thread as resolved? 64.43.232.10 15:54, 13 May 2013 (UTC)

The interaller surely uses cookies, but I am not aware of any files created there. Maybe some PHP session data, but that will be deleted sooner or later anyway. I am also not sure, what exactly caused this problem, however, installation obviously worked now.

Note one thing:

Now you can still easily throw the wiki (files and DB) away and start directly with 1.20. That way you do not need to update to 1.20 in a few months. 88.130.120.134 16:22, 13 May 2013 (UTC)

About gadget edittop.js

It's not work anymore. An [edit] link for the lead section of a page not shown up. Is there anyone can fix this? Other wikis maybe link to that gadget by "mw.loader". Thanks in advance.  Ę-oиė  >>>  ™ 18:11, 13 May 2013 (UTC)

You should ask on the talk page for the gadget. ☠MarkAHershberger☢(talk)☣ 19:18, 13 May 2013 (UTC)

Why I must go to wp.en to talk about it? It's not a problem at that wiki. I'm talking about gadget at this site.  Ę-oиė  >>>  07:33, 14 May 2013 (UTC)

Sorry, I didn't see it installed here when you first asked. I've updated the copy here with the one on enwp and it seems to work. ☠MarkAHershberger☢(talk)☣ 13:44, 14 May 2013 (UTC)

Oh, ok. Thanks, Sir.  Ę-oиė  >>>  16:37, 14 May 2013 (UTC)

[RESOLVED] Retrieving category page using API

I'd like to use the MediaWiki API to retrieve a category page, complete with the links to subcategories and pages. But when I use the technique I use for regular pages, I only get the content of the page (the text I see when I edit the page) and not all the links to subcategories and pages that have that category. Is there a way to get the whole content?

For example, http://www.mediawiki.org/wiki/Category:Tools is a category page.

I can use this query to get its content: http://www.mediawiki.org/w/api.php?action=query&prop=revisions&rvprop=content&format=xml&titles=Category:Tools

But that gives me only the basic content, whereas the Category:Tools page shows me the subcategories and pages and files.

I could use the API:Categorymembers to get the subcategories, pages, and files. But then I'd have to build a page myself from the lists of subcategories and pages returned.

I tried using action=parse, and that expanded templates, but still didn't give me the Subcategories and Pages sections: http://www.mediawiki.org/w/api.php?action=parse&prop=text&format=xml&page=Category:Tools Llarqq (talk) 21:40, 13 May 2013 (UTC)

Category links are skin-specific, so you can't get that as the resulting text.

You can query that info through the API as well. See Ciencia Al Poder (talk) 09:36, 14 May 2013 (UTC)

Thanks for the response. It helps to know that category links are skin-specific.

And your sample API query did provide some helpful hints that can make it easier to pull together the information I need (even it it's not quite as simple as I hoped).

Thank you for taking the time to respond! Llarq (talk) 20:49, 15 May 2013 (UTC)

You're welcome! Just for clarification, when I said that category links are skin-specific, I mean that it's left to the skin the task to appropriately render those links, so they can be placed anywhere in the UI, or not rendered at all. But categories are part of the core functionality of MediaWiki, not a skin addition. Ciencia Al Poder (talk) 09:42, 16 May 2013 (UTC)

Enabling CACHE_ACCEL causes fatal exception of type mwexception

Hello everyone,

I've been reading into optimizing my mediawiki site and tried enabling $wgMainCacheType = CACHE_ACCEL; into the code. However, if i add this line, my wiki does not function at all and reports "[2fd7b859] 2013-05-13 21:39:56: Fatal exception of type MWException"

Please advise, thank you! 38.104.77.126 (talk) 21:42, 13 May 2013 (UTC)

Maybe your system doesn't have any PHP code acceleator listed in Manual:Cache#PHP caching.

The MediaWiki installer checks if a supported PHP accelerator is present. If it didn't detect it, enabling it on a running wiki may cause that error. Run the installer just to see if it detects the accelerator. Otherwise you should install it first. Ciencia Al Poder (talk) 09:39, 14 May 2013 (UTC)

Extension:MaintenanceShell

hi how do I install Extension:MaintenanceShell I have downloaded the files and it is on my wiki but it says the following when I type in the special page for it

Permissions errors
  
 
  
Jump to: navigation, search 
  

You do not have permission to the maintenance shell, for the following reason: 


You are not allowed to execute the action you have requested. 

86.171.33.224 (talk) 06:41, 14 May 2013 (UTC)

Have you followed the instructions at Extension:MaintenanceShell#User_rights? Ciencia Al Poder (talk) 09:45, 14 May 2013 (UTC)

Yes Paladox2014 (talk) 12:55, 15 May 2013 (UTC)

export mediawiki page in pdf

hello am not english, please forgive my english

extension pdfbook to export mediawiki pages in pdf does not work. I have the following error message: adobe reader can not read the file because the file type is not supported or is damaged

please help me 81.91.233.200 (talk) 14:54, 14 May 2013 (UTC)

my configuration:

mediawiki: 1.15.2

PHP 5.2.0

MYSQL 5.0.27 81.91.233.200 14:57, 14 May 2013 (UTC)

Hi

I have no idea if this is the solution but it is worth a try: From BooksOnBoard

Error: "Adobe Reader could not open because it is either not a supported file type or because the file has been damaged."

If you are getting the above error message, it means your computer is attempting to use Adobe Reader to open a secure ePub or PDF book. Secure ePub and PDF books are only compatible with Adobe Digital Editions (ADE), they will NOT work with Adobe Reader.

If you don't already have Adobe Digital Editions, you can download it from the Adobe website here: http://www.adobe.com/uk/products/digital-editions.html Ron Barker (talk) 08:10, 15 May 2013 (UTC)

thanks Ron

the pdf file size in 0 octet.

same probleme with you solution 81.91.233.200 11:51, 15 May 2013 (UTC)

how do htmldoc for mediawiki on windows 81.91.233.200 16:35, 15 May 2013 (UTC)

extension wikibase and wikibaselib andd wikibase client

hi please can I have some help to install it because ive downloaded the files but it isent letting m install it 86.171.33.224 (talk) 18:27, 14 May 2013 (UTC)

Please, elaborate. The description of your problem is very vague. Ciencia Al Poder (talk) 09:29, 15 May 2013 (UTC)

Well I have installed both of the extension but when I click on create new labe in special pages and type for example wiki and click create it says this error

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 "DatabaseBase::selectRow". Database returned error "1146: Table 'u719470057_my.wb_id_counters' doesn't exist (mysql.2freehosting.com)".

I doint have access to ssh Paladox2014 (talk) 12:54, 15 May 2013 (UTC)

Ok, Extension:Wikibase needs database changes to work (for example, creation of new tables). You must run update.php after installing the extension. If you don't have shell access, see the section about Web updater on that same page. Ciencia Al Poder (talk) 09:46, 16 May 2013 (UTC)

i have installed maintence shell on my wiki but it keeps saying for security reason you must have javascript enabled but i have it enabled please help 93.93.218.196 12:18, 16 May 2013 (UTC)

Extension:MaintenanceShell is not needed to perform an upgrade. See Manual:Upgrading#Web_updater. Ciencia Al Poder (talk) 08:12, 20 May 2013 (UTC)

Vector skins aren't working

I just created the VectorBlue skin, which works fine. The code for it is here: https://github.com/Sturmkrieg/mw-VectorBlue

I also created VectorRed and FieldGray, but they aren't working. I used the same method and checked to make sure everything is correct (it looks like it is) but it still doesn't work. I figure there's something subtle I'm missing.

Here's the source code for the other skins:

• https://github.com/Sturmkrieg/mw-VectorRed
• https://github.com/Sturmkrieg/mw-FieldGray

I'm testing it on MediaWiki 1.19.1 Lieutenant Aleksandr Reznov 19:11, 14 May 2013 (UTC)

1.17+ backwards-compatibility with IE7

Hi all-

We're currently running 1.16.5 at my work, and were hoping to update to 1.20 soon for various reasons (one being the CKEditor extension for our many, many Wikitext-hatin' users).

Unfortunately, statistics show that the vast majority of our users are running Internet Explorer 7. They're slowly deploying IE8 (srsly), but it'll be another year or more before everyone has that version. Since we have no control over what browsers our users use (for example, Chrome is installed on every desktop but not everyone uses it), we have to make our products backwards-compatible.

I've upgraded our staging version to 1.20, and it seems to run OK on IE7, but the big issue is that anything jQuery-related doesn't want to play nicely -- for example, switching between tabs on the Preferences pages just doesn't work at ALL.

Are there any tips/tricks on what areas of the newer MediaWiki versions that can be altered to work with IE7? If there are only a few things I could fix, then it'd be a huge help toward pushing the upgrade so we're no longer in the stone ages.

Info
MediaWiki: 1.16.5
PHP: 5.3.24 (FastCGI)
MySQL: 5.1.58 Kchurch05 (talk) 19:30, 14 May 2013 (UTC)

I don't know anything offhand. Try MW 1.19? It is the LTS version and will supported for a while. ☠MarkAHershberger☢(talk)☣ 19:17, 20 May 2013 (UTC)

If MediaWiki 1.20 is having issues in IE7, it is likely something related to your configuration. Because to my knowledge no MediaWiki version since 1.17 (1.18, 1.19, 1.20, 1.21 and – currently in development and deployed to MediaWiki.org and Wikipedia – 1.22) has issues with IE7.

The bug you describe (javascript not working on the preferences page) suggests there may be a different (IE7 incompatible) script being loaded that causes MediaWiki's script to no longer execute.

Either way, please report the bug, if it is caused by MediaWiki I'm sure we'll do our best to find a solution because it sure was not an intentional decision for javascript to break fatally in IE7 in MediaWiki 1.20. There are no known bugs like the one you describe in IE7. Krinkle (talk) 18:45, 22 May 2013 (UTC)

Sorry for the late reply -- we figured out the issue. The preferences tabs thing was skin-related and fixed.

Unfortunately the IT geniuses set all our intranet sites to be displayed in IE7 standards as a default, so no CKEditor. (Srsly?!! WTF.) In the meantime, we'll just have to use FCKEditor (old version which still works in IE7) until the official WYSIWYG editor is deployed to the public. Kchurch05 (talk) 14:42, 27 June 2013 (UTC)

extension:wikibase

how do i run You will need to run the populateSitesTable.php maintenance script in Wikibase Lib: I have no access to ssh and my freehost for my website is 2freehost 86.171.33.224 (talk) 19:37, 14 May 2013 (UTC)

You would have to set up a web page to call the script. If you don't know how to do this, you should hire someone to work on it for you. ☠MarkAHershberger☢(talk)☣ 02:17, 15 May 2013 (UTC)

Oh ok do they have the guid on how to do it on mediawiki Paladox2014 (talk) 16:16, 15 May 2013 (UTC)

Wikibase is pretty new, not a lot of documentation has been written for it yet. ☠MarkAHershberger☢(talk)☣ 19:24, 20 May 2013 (UTC)

How long will the Change history kept in database?

Hi,

My question is. How long will the change history kept in database. Can i keep it forever or its a default behaivor or do i need to change some settings somewhere. I have MediaWiki 1.17.0 installed at this moment and i have no plans to upgrade (interal wiki).

Regards, Marek 195.80.111.234 (talk) 08:05, 15 May 2013 (UTC)

Page history is kept forever, and there's no configuration in core to remove old history entries. Even if you delete a page, you can restore it entirely. Ciencia Al Poder (talk) 09:33, 15 May 2013 (UTC)

Deletion is deletion Poder. The achive table (where "deleted" pages go) may not get backed up and there is at least one maintenance script that can be used to delete pages from the database. – Allen4names (IPv6 contributions) 06:34, 16 May 2013 (UTC)

4names, I perceived 195.80 question as a worry about losing page history and the response was directed to that concern.

Of course, there are maintenance scripts for deleting pages from the entire database, but the default behavior of MediaWiki is to keep all data. Also, page deletion is backed up since it's stored in the database, and backups should be done on the entire database. The XML dumps doesn't count as a "complete" backup, hence you can't rely on them to restore all the contents. Ciencia Al Poder (talk) 09:38, 16 May 2013 (UTC)

Hide Blocks/Deletions From Recent Changes

Is there any way to hide blocks/deletions from recent changes so they can't be seen? I don't like them clogging up the recent changes page after I had to block some spam multi accounts for a personal site I made. I tried Help:RevisionDelete but it only grays out/strikes through the log entries instead of removing them altogether from Recent Changes. Also, it doesn't seem to let me undo the graying out of RevisionDelete, as such log entries no longer seem to be editable afterwards, so that RevisionDelete is not only useless but makes the problem worse. Jzyehoshua (talk) 15:31, 15 May 2013 (UTC)

[RESOLVED] MW 1.21.0

Hi what time is Mediawiki 1.21.0 coming out today Paladox2014 (talk) 18:30, 15 May 2013 (UTC)

Despite the my intention to release 1.21 today, I have to delay it until

May 18. Yesterday someone pointed out a blocker to me.

While we have a work-around for this, I don't have time to integrate it

right now, so the release needs to be delayed until Saturday.

http://www.gossamer-threads.com/lists/wiki/wikitech/358697 31.19.128.18 20:41, 15 May 2013 (UTC)

Oh ok Paladox2014 (talk) 20:50, 15 May 2013 (UTC)

Is Mediawiki 1.21.0 coming out today if it is what time would it be coming out today 5.66.149.62 10:17, 18 May 2013 (UTC)

I had given a time for making the release today, but I'm running into a problem of logistics. It will probably have to wait until Monday. ☠MarkAHershberger☢(talk)☣ 14:08, 18 May 2013 (UTC)

Okay :( 93.208.69.189 15:56, 18 May 2013 (UTC)

On what time will it come out today? :) 217.249.41.37 11:00, 20 May 2013 (UTC)

what time is mediawiki 1.21.0 coming out today 86.168.53.89 19:18, 20 May 2013 (UTC)

is mediawiki 1.21.0 coming out today if it is what time is it coming out 86.168.53.89 20:09, 20 May 2013 (UTC)

I'm not ready to make any announcements yet. I will update here when I am. ☠MarkAHershberger☢(talk)☣ 20:10, 20 May 2013 (UTC)

ok 86.168.53.89 20:11, 20 May 2013 (UTC)

Is it coming out today or tomaor 90.209.78.127 16:06, 21 May 2013 (UTC)

As stated on MediaWiki 1.21, you could also checkout and follow the REL1_21 branch in Git as it stabilizes. TK-999 (talk) 18:17, 21 May 2013 (UTC)

Ok thanks but when will it be avalible to download through the main page on Mediawiki 86.168.53.89 18:44, 21 May 2013 (UTC)

Asking more often does not make it come out faster! The more you molest those, who should get it ready, the longer it will take!

It will come out, when it comes out! That's all. 88.130.97.22 19:59, 21 May 2013 (UTC)

Ok 86.168.53.89 20:20, 21 May 2013 (UTC)

Add new link to user bar?

Is it possible to add a new link to the bar which the user preferences link, user page link, and log in link are? If so, how do I do it? Shuvuuia (talk) 01:07, 16 May 2013 (UTC)

Alternative Parser::setFunctionHook Callback

renderArrayMap( &$parser, $value = '', $delimiter = ',', $var = 'x', $formula = 'x', $new_delimiter = ', ' ) 

renderArrayMapObj( &$parser, $frame, $args )

making use of: Template:Navbar

Hi,

I have a new install and attempted to use the Template:Navbar

The problem is that the list is always vertical, not horizontal.

http://computing.ccib.rutgers.edu/wiki/index.php/Template:Navbar/doc

Wikipedia usage:

https://en.wikipedia.org/wiki/Template:Navbar

What exactly could cause this?

Thanks for any suggestions. 198.151.130.142 (talk) 02:55, 16 May 2013 (UTC)

You need the css styling for those elements. This can be found on enwiki in MediaWiki:Common.css. ☠MarkAHershberger☢(talk)☣ 18:25, 2 June 2013 (UTC)

text - format for module code

Hi,

I have

http://computing.ccib.rutgers.edu/wiki/index.php/Module:HtmlBuilder

The page should be transcluded in the above but it is not.

http://computing.ccib.rutgers.edu/wiki/index.php/Module:HtmlBuilder/doc

The result should be like this:

http://computing.ccib.rutgers.edu/wiki/index.php/Module:HtmlBuilder

What am I missing? Versions listed here.

http://computing.ccib.rutgers.edu/wiki/index.php/Special:Version 198.151.130.142 (talk) 03:02, 16 May 2013 (UTC)

You're missing adding {{:Module:HtmlBuilder/doc}} to the Module:HtmlBuilder page. That would transclude its contents.

You may also want to wrap your code inside <pre></pre> so it's displayed with all the spaces and line breaks you put in your code. Ciencia Al Poder (talk) 09:53, 16 May 2013 (UTC)

How to Create New Tab, Click on It and Create a New Page ???

Hi there! I was able of creating a new Tab using this code:

<?php
if( !defined( 'MEDIAWIKI' ) ){
        die( "This is not a valid access point.\n" );
}
$wgHooks['SkinTemplateNavigation'][] = 'replaceTabs';
function replaceTabs( $skin, &$links) {  
        $maintitle = Title::newFromText( wfMsgForContent( 'mainpage' ) );// nuevo
        $links['namespaces']['name_of_tab'] = array(
                'class' => false or 'selected', // if the tab should be highlighted
                'text' => 'Documentacion Tecnica', // what the tab says
                'href' => _, // where it links to
                'context' => 'main',
        );
        return true;
        
}

I found that code in this website: http://stackoverflow.com/questions/12192641/how-to-add-custom-tab-button-with-external-link

But I also need that when I click in this new tab, a new page can be created in that specific tab(I don't want it to go to a new page in a different section after clicking on it), and that after the first time of clicking there, I can click on that tab and see the info it has been already entered.

Could you please help me?? I've tried several different options published in this website and others but haven't found anything that can help me. Thanks in advance!

My installation basic info is: MediaWiki: 1.20.2 PHP: 5.3.6 (cgi-fcgi) MySQL: 5.1.30 Vivihodal (talk) 03:11, 16 May 2013 (UTC)

Welcome to MediaWiki Support Desk!

But, there are things before you can help you.

Your MediaWiki and PHP version is too old. Older version of MediaWiki/PHP contains bugs and security flaws. PHP 5.3 is old and unsupported by PHP Group. Your current MediaWiki version is unsupported.

Since your PHP version won't support newer version of MediaWiki, before getting help, you be better off to ask your web host to upgrade PHP to version 7.2 and then upgrade MediaWiki version.

You can wait someone else to help, but sorry about that. 2A02:C7F:963F:BA00:6978:E68F:A981:8B0D (talk) 15:50, 11 April 2018 (UTC)

Keine Verwaisten Seiten in selbst erstellten Namensräumen

Hallo zusammen

Wir erstellen auf unserem Wiki Seiten, die nirgends verlinkt sind, damit wir sie zu einem späteren Zeitpunkt im passenden Dokument verlinken können.

Ich habe in den Spezialseiten die Übersicht "Verwaiste Seiten" gefunden. Komischerweise werden die neu erstellten Dokumente dort nicht angezeigt. Zuerst habe ich das darauf zurückgeführt, das dies ein zeitkritisches Problem sein muss. Später habe ich dann aber herausgefunden, dass Dokumente, die im Main-Namensraum erstellt werden sofort in dieser Übersicht erscheinen.

Wir jedoch legen die Dokumente in selbst erstellten Namensräumen an. Kann es sein, dass solche Namensräume auf der Seite Spezial:Verwaiste_Seiten (Special:Lonelypages) gar nicht berücksichtigt werden? Wenn ja, kann man dagegen etwas tun?

Grüsse und vielen Dank

Hampa

MediaWiki: 1.16.2 Hampa~mediawikiwiki (talk) 07:25, 16 May 2013 (UTC)

Siehe https://bugzilla.wikimedia.org/show_bug.cgi?id=2348 und https://bugzilla.wikimedia.org/show_bug.cgi?id=4204 AKlapper (WMF) (talk) 12:45, 16 May 2013 (UTC)

Hallo

Vielen Dank für Deine Antwort. Ich wollte jedoch etwas Anderes hören. ;o)

Aber da kann man nichts machen. Ausser abwarten und Tee trinken.

Gruss und nochmals vielen Dank

Hampa Hampa (talk) 14:58, 16 May 2013 (UTC)

Vector: Don't expand first submenu

Stefahn (talk) 09:31, 16 May 2013 (UTC)

How to enable email notifications for comments

Hi.

A few days ago I've been searching how to get notified whenever people comment on my pages.

I will be very greatful if somebody could help me.

Regards. 190.250.168.17 (talk) 11:18, 16 May 2013 (UTC)

Not sure if "Preferences>Notifications>Email settings" is what you mean, if not please elaborate. AKlapper (WMF) (talk) 12:32, 16 May 2013 (UTC)

My goal is: When I have a Mistake or something like that I want other users can do a feedback and mediawiki automatically sends me an e-mail notification, making possible a faster adjustment. 201.232.2.115 13:24, 16 May 2013 (UTC)

Set extention config variable before or after call require_once

Sorry for my bad English.

On page http://www.mediawiki.org/wiki/Manual:Developing_extensions "If you want to make your extension user configurable, you need to define and document some configuration parameters and your users setup should look something like this:

require_once( "$IP/extensions/MyExtension/MyExtension.php" );
$wgMyExtensionConfigThis = 1;
$wgMyExtensionConfigThat = false;"

Some extention may use configuration parameters in setup time (ie be used in "$IP/extensions/MyExtension/MyExtension.php") and therefore extention configs must be defined before including MyExtension.php:

$wgMyExtensionConfigThis = 1;
$wgMyExtensionConfigThat = false;
require_once( "$IP/extensions/MyExtension/MyExtension.php" );

Or I'm wrong? Likemusic (talk) 18:50, 16 May 2013 (UTC)

In general, extensions don't use those configuration variables at setup time, but when they should do actions (for example, on page rendering, page save, log action, etc). In such cases, the extension uses a Hook, so those variables are already defined when needed. Ciencia Al Poder (talk) 09:29, 17 May 2013 (UTC)

Thanx for answer.

I understand it. But extension could set or not set some hooks according values of config variables. Currenty call wfRunHooks() for some hooks is idle. Therefore I think, that set extention variable values before require_once() would be logical. Why not? Likemusic (talk) 17:04, 17 May 2013 (UTC)

extension could set or not set some hooks according values of config variables

You should set those hooks anyway, and the function that runs on those hooks should then read the value of the configuration variables to decide if it should perform an action inside the hook or not.

If you think your extension needs a variable set before the require_once(), specify that in the installation instructions, but this seems a bad practice, and I haven't seen any example where this is needed. Ciencia Al Poder (talk) 08:16, 20 May 2013 (UTC)

«specify that in the installation instructions»

Is't a good option. Thanx for answers. Likemusic (talk) 14:38, 20 May 2013 (UTC)

The placement of configuration variables shouldn't matter in general for an extension. Several that I've seen do depend on the configuration variables being specified after the require_once() is executed, though. If your users need to specify them before the require_once() is loaded, though, that is unusual, so make sure your installation instructions make that clear. ☠MarkAHershberger☢(talk)☣ 15:23, 20 May 2013 (UTC)

The following conventions:

• Extensions must not change behaviour from the global scope, instead they should use hooks and callbacks.
• Extensions should provide the default values for their configurations from the global scope in the main php file.

Are there for good reasons.

• The placement of configuration variables is in fact quite important, because if they are set before, it is likely the values will be overridden by the defaults.
• Extensions should use hoooks because that ensures all configurations have applied first: DefaultSettings, the remainder of LocalSettings and Setup.php. Especially Setup is important for some variables are dynamically constructed. This also ensures they don't make wrong assumptions about the configuration. For example, a variable might change before the setup has completed, the extension would be acting on the wrong value.
• This also ensures extensions follow the proper procedure and not invent custom mechanisms (since pretty much all supported ways of providing functionality from an extension use a hook or callback that does not run in the global scope during setup).

The only way for LocalSettings to set a variable is after the extension file is loaded (otherwise they'd be reverted immediately by the extension file).

Though some extensions have done it otherwise in the past, to my knowledge this has never lead to anything good nor did it improve anything. I'd highly recommend any developer to follow this convention. If you believe there is a very good reason not to, I'd recommend you ask a fellow MediaWiki developer for confirmation that this indeed a necessity for your extension. Krinkle (talk) 17:27, 22 May 2013 (UTC)

Short URL with Host Gator

I've been trying to set-up short urls with a wiki hosted at Host Gator, but I keep getting 404 Page Not Found errors. I already have WordPress installed in the root directory, and MediaWiki is installed at /w as suggested, and I want it to have the "default" short URL sequence of /wiki/Article_Title. I've followed the guide at Manual:Short_URL as well as the linked RedWerks auto-generated code, but I couldn't get the .htaccess to work properly. When going to /w it did "redirect" to /wiki/Main_Page, but it gave a 404 error there. Here's part of my .htaccess before I add anything:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/?wiki/(.*)$ /w/index.php/$1 [L,QSA]
</IfModule>
# Google Analytics Integration - Added by cPanel.
<IfModule mod_substitute.c>
AddOutputFilterByType SUBSTITUTE text/html
Substitute "s|(<script src='/google_analytics_auto.js'></script>)?</head>|<script src='/google_analytics_auto.js'></script></head>|i"
</IfModule>
# END Google Analytics Integration

Again, I tried exactly what was given in the Manual and at RedWerks, but I couldn't get it to work. From searching, I've read that Host Gator's set up is a little differently, and I found some codes that include a set-up more similar to what's used for my WordPress, with the "Rewrite Base/" and a little bit different "RewriteRule". This is what I've tried to cobble together from different help topics:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/?wiki/(.*)$ /w/index.php/$1 [L,QSA]
</IfModule>

Unfortunately, that's just giving me a 404 error as well, but I assume it's because I just haven't set it up right. Help would be appreciated. Lakster (talk) 18:54, 16 May 2013 (UTC)

I have the same problem. No solution yet. 198.84.221.20 19:34, 5 August 2013 (UTC)

Are you trying to install beside wordpress, too? ☠MarkAHershberger☢(talk)☣ 17:18, 16 August 2013 (UTC)

I have the same problem. :-(

From Brazil! ;-) 177.9.179.37 18:58, 21 August 2013 (UTC)

Are you trying to install MW and WordPress, too? ☠MarkAHershberger☢(talk)☣ 19:19, 21 August 2013 (UTC)

Try this. This is some sort of a brain wrecking hack. But it should work. (Tested on Hostgator)

1. Install Mediawiki in public_html/wiki
2. In public_html, create a .htaccess and add this content

==Goes into root htaccess==

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www.)?Yoursite.com$
RewriteRule ^(/)?$ wiki [L]
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^wiki/(.*)$ ./wiki/index.php?title=$1 [PT,L,QSA]

==Goes to localsetting==

$wgScriptPath = "/wiki";
$wgArticlePath = "$wgScriptPath/$1";

So the first block of htaccess code makes main site redirect to a sub-folder in that site so if you enter yourdomain.com, the link will read yourdomain.com/wiki

then, next block of code actually does the url shortening

the localsetting part is what everyone know to do. Abhinav4848 (talk) 21:05, 21 June 2014 (UTC)

Estou com mesmo problema, em um site que eu desenvolvi... deve ser algo que a hostgator adiciona nos arquivos pra ver estatísticas... vou investigar 138.94.183.114 (talk) 19:37, 8 May 2020 (UTC)

RESOLVED: mediawiki hangs

Hi all,

I'm afraid I have little more information than "it doesn't work." More precisely, it hangs. There is no error in the Apache logs. Other web applications on the server seem to be operating normally.

This is mediawiki 1.20.5, PHP 5.4.15, MariaDB 5.5.30. The site is at https://disunitedstates.org/wiki. Another mediawiki site on the same system, using the same environment, just a different domain, and a different IP address, is running just fine at https://parts-unknown.org/wiki.

I am sometimes able to load one page if I know the URL. If I try to load another page, Firefox just hangs, and Chromium replies that the page is not available: "Error 7 (net::ERR_TIMED_OUT): The operation timed out."

I tried running rebuildall.php--mostly in desperation:

munich% php rebuildall.php   
** Rebuilding fulltext search index (if you abort this will break searching; run this script again to fix):
Dropping index...
Rebuilding index fields for 1036 pages...
500
1000

Rebuild the index...
Done.


** Rebuilding recentchanges table:
Loading from page and revision tables...
$wgRCMaxAge=7862400 (91 days)
Updating links and size differences...
Loading from user, page, and logging tables...
Flagging bot account edits...
Flagging auto-patrolled edits...
Deleting feed timestamps.
Done.


** Rebuilding links tables -- this can take a long time. It should be safe to abort via ctrl+C if you get bored.
Refreshing redirects table.
Starting from page_id 1 of 1036.
100
200
300
400
500
600
700
800
900
1000
Refreshing links table.
Starting from page_id 1 of 1036.
100

That has hung there.

I'm sure this is basically zero information and I haven't told you enough. What else should I do?

Thanks! Benfell (talk) 03:46, 17 May 2013 (UTC)

It turns out I'm wrong about the wiki at https://parts-unknown.org/wiki. It seems to be similarly afflicted. Benfell (talk) 03:56, 17 May 2013 (UTC)

I think I've identified the problem. I was trying to import a page I had exported from wikimedia.org: African_American_boy_selling_The_Washington_Daily_News.png

Somehow this tied mysql (actually mariadb) in knots. Restarting the database server seems to have ended the hangs. I don't know what all that page needs that's weird. But retrying the import generated all sorts of errors:

[Thu May 16 21:43:35 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=16897 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:35 2013] [error] [client 208.167.230.35] PHP Warning: Error while sending QUERY packet. PID=9759 in /big/www/parts-unknown/org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:35 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=7677 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:35 2013] [error] [client 67.169.2.178] PHP Warning: Error while sending QUERY packet. PID=7460 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:35 2013] [error] [client 141.8.147.11] PHP Warning: Error while sending QUERY packet. PID=18160 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 208.167.230.35] PHP Fatal error: Method Message::__toString() must not throw an exception in /big/www/parts-unknown/org/mediawiki-1.20.5/includes/Html.php on line 0

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=11045 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 66.249.78.46] PHP Warning: Error while sending QUERY packet. PID=20869 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Error while sending QUERY packet. PID=23529 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Error while sending QUERY packet. PID=11938 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=13965 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 141.8.147.11] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=7388 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=24213 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Error while sending QUERY packet. PID=8085 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 173.199.116.195] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:36 2013] [error] [client 67.169.2.178] PHP Warning: Error while sending QUERY packet. PID=11836 in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/db/DatabaseMysql.php on line 46

[Thu May 16 21:43:36 2013] [error] [client 67.169.2.178] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 269

[Thu May 16 21:43:36 2013] [error] [client 67.169.2.178] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 270

[Thu May 16 21:43:36 2013] [error] [client 67.169.2.178] PHP Warning: Cannot modify header information - headers already sent by (output started at /big/www/disunitedstates.org/mediawiki-1.20.5/includes/OutputPage.php:1997) in /big/www/disunitedstates.org/mediawiki-1.20.5/includes/Exception.php on line 229

[Thu May 16 21:43:48 2013] [error] [client 66.249.76.125] PHP Fatal error: Call to undefined method Ai1ec_Calendar_Controller::get_month%7Cexact_date:1078128000_view() in /big/www/disunitedstates.org/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php on line 74

[Thu May 16 21:45:35 2013] [error] [client 66.249.78.46] PHP Fatal error: Call to undefined method Ai1ec_Calendar_Controller::get_agenda%7Ctime_limit:1021878000_view() in /big/www/disunitedstates.org/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php on line 74

[Thu May 16 21:45:45 2013] [error] [client 66.249.78.46] PHP Fatal error: Call to undefined method Ai1ec_Calendar_Controller::get_oneday%7Cexact_date:1241420400_view() in /big/www/disunitedstates.org/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php on line 74

[Thu May 16 21:45:52 2013] [error] [client 67.169.2.178] File does not exist: /big/www/disunitedstates.org/wiki/skins/common/images/anarchy_6-135.png, referer: https://disunitedstates.org/wiki/index.php/Special:RecentChanges

[Thu May 16 21:45:56 2013] [error] [client 66.249.78.46] PHP Fatal error: Call to undefined method Ai1ec_Calendar_Controller::get_agenda%7Ctime_limit:1119769200_view() in /big/www/disunitedstates.org/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php on line 74

I'm going back to an earlier version of the database and abandoning the attempt to import this page. Benfell (talk) 04:58, 17 May 2013 (UTC)

Automatically mark all pages as visited

I want to receive e-mail notifications about talk pages whenever possible. That's why is very uncomfortable having to press the "Mark all pages visited" all the time with the goal I can receive those notifications. How can I automate the process?

Thanks a lot. 190.250.168.17 (talk) 11:01, 17 May 2013 (UTC)

Seems like something you could write some javascript for. ☠MarkAHershberger☢(talk)☣ 17:39, 20 May 2013 (UTC)

Translate

Hi is there a template on Mediawiki which you can put on pages to ask for that page to be translated 5.66.149.62 (talk) 12:02, 18 May 2013 (UTC)

Not by default, but you can create one the way you need it. :-) 88.130.88.216 21:31, 19 May 2013 (UTC)

Ok 86.168.53.89 06:39, 20 May 2013 (UTC)

[RESOLVED] Pagetitle encoding problems when upgrading a wiki

• MediaWiki : 1.16.2 () -> 1.20.3
• PHP : 5.3.3-7+squeeze15 (cgi-fcgi)
• Database : MySQL 5.1.66-0+squeeze1

Hi,

I'm working on the upgrade of es.vikida.org and I have some problems. The DB (here is a screen of phpmyadmin) as some encoding "problems" but it's working with MW:1.16.2. When upgradding to MW:1.20.3 all the pagetitle with special characters aren't accessible File:Index es before migration.png - File:Index es after migration.png. Anyone as an idea to correct the problem ? Vivi-1 (talk) 13:31, 18 May 2013 (UTC)

Hi!

I have once fixed that kind of error; it is a tidysome work. :-(

The result, which you must have in the end is: Your database uses UTF-8 or binary encoding and the data in your database is (in any case) UTF-8-encoded.

First you need to know what kind of encoding your system uses:

• What is the encoding of the database, of the different tables and of all columns, which have an encoding (that means of columns holding "text" and so on as opposed to "integers")?
  • Are all these encodings identical?
  • They should all be either "utf8_general_ci" or "binary" - and all the same.
• What you see in the screenshot is that the data in the column, which you posted, does in fact not use the encoding, which you provide as "encoding declaration" for that column.
  • So what you need to do is: If the column's content in fact is already UTF-8 encoded, then convert the encoding declaration for that column (not the content in it!) to UTF-8. That worked in some way by temporarily making the column a BLOB, then converting it (MySQL does not change the content of blobs when you convert the charset) and then set the column back to the type it had before.
  • If the content in the column in fact is not UTF-8-encoded, you need to convert the encoding of the content to UTF-8. I think that worked same as above, but without changing the affected columns to blob before.

I know there also are some scripts around 88.130.104.212 14:41, 18 May 2013 (UTC)

Hello,

So, I'm not on my main computer, so, can't test it on my test instalation :(

Interclassments are on utf8_bin or utf8_general_ci or ... latin1_swedish_ci, latin1_bin

I (or maybe another dev who can try it faster than me) will try your solution. (I can try tomorrow only ^^) Vivi-1 (talk) 15:08, 18 May 2013 (UTC)

Hi,

I have try this :

ALTER TABLE `archive` CHANGE `ar_title` `ar_title` BLOB;

ALTER TABLE `archive` CHANGE `ar_title` `ar_title` TEXT CHARACTER SET utf8 COLLATE utf8_bin;

And MySQL respond:

#1170 - BLOB/TEXT column 'ar_title' used in key specification without a key length

( Vivi-1 (talk) 18:08, 19 May 2013 (UTC)

Hi,

I am not really a MySQL expert, but maybe the script here helps you. It shows you the logic, which you have to go through. That should be a help to understand, what is needed. The script is written for a database, which is used by TYPO3; this explains the first few lines, in which the script tries to get the MySQL credentials. These first lines cannot be transferred 1:1 to your situation, but for your needs, you could try setting the variables in the script directly. Maybe it then even works for you without the need of doing much additional manual work. :-) 88.130.88.216 21:27, 19 May 2013 (UTC)

echo utf8_decode($data);</pre>
I feel stupid.
I'm making a script to correct all the affected collumns in the DB.
If you have any problem, have a look to : https://github.com/neitanod/forceutf8 [[User:Vivi-1|Vivi-1]] ([[User talk:Vivi-1|talk]]) 15:18, 20 May 2013 (UTC)
::::correcting (the test) DB doesn't seem to be a good idea :|
::::I'm lost. And I have no idea why There is problem.
::::When accessing DB with PHP, the data are show without error. But MW as a problem with the title name in pages. [[User:Vivi-1|Vivi-1]] ([[User talk:Vivi-1|talk]]) 18:15, 20 May 2013 (UTC)
:::::AANNNDDDD : SOLVED :D
:::::<syntaxhighlight lang='text'><?php
namespace ForceUTF8;
error_reporting( -1 );
ini_set( 'display_errors', 1 );
ini_set('default_charset', 'utf-8');
require_once('Encoding.php');
$handle = opendir('./sql/');
$dirIgnore = array ('.','..');
while ($file = readdir($handle)) {
    if (!in_array($file, $dirIgnore)) {
        echo 'Encoding '. $file ."\n";
        file_put_contents('./sql_utf8/'. $file, Encoding::fixUTF8(file_get_contents('./sql/'. $file)));
    }
}
?>

You need : https://github.com/neitanod/forceutf8

The source .sql files should be in ./sql/ and the encoded files in ./sql_utf8/

I reccomand to use one file per table.

Please, note that this is MY solution, it's not the most powerfull ... it can kill cats, burn your computer ... Vivi-1 (talk) 20:34, 23 May 2013 (UTC)

Captcha isn't functional

Despite selecting the all requested cats I am unable to submit an addition. 69.250.231.156 (talk) 15:55, 18 May 2013 (UTC)

Could you clarify where you are having this problem? More details would also be good. ☠MarkAHershberger☢(talk)☣ 15:41, 20 May 2013 (UTC)

Where to ask improvement for a gadget ?

Where to ask improvement for a specific gadget ?

• https://bugzilla.wikimedia.org do not have topic for this.
• talk page of the gadget script do not seems to be the place for a quick response.  ◄ David L • discuter ► 10:25, 19 May 2013 (UTC)

Interesting. I use that gadget on enwiki but not here. Reading your comments, I wonder if decreasing the size of the timeout as you suggest would cause problems. I'm willing to make the changes you request if I can get someone with more JS knowledge than me to say they're ok. ☠MarkAHershberger☢(talk)☣ 15:34, 20 May 2013 (UTC)

Gadgets are maintained on the wiki, including the source code itself. The appropriate place to report issues is therefor on the wiki. Within the wiki, I believe authors most commonly expect feedback to be placed on the talk page of the gadget script page. Krinkle (talk) 19:26, 20 May 2013 (UTC)

Krinkle has updated the gadget here. Does it work better now? ☠MarkAHershberger☢(talk)☣ 19:40, 20 May 2013 (UTC)

Template

The wiki handles not correctly templates, it shows system characters. See example here http://www.antifahahaha.com/fawiki/index.php?title=Jean-Pierre_Demol Lunablues (talk) 01:43, 20 May 2013 (UTC)

Enable Extension:ParserFunctions Ciencia Al Poder (talk) 08:28, 20 May 2013 (UTC)

[RESOLVED] user authorisations

i dont find out to limit modification, creation only for users registred. I have many spams Lunablues (talk) 01:44, 20 May 2013 (UTC)

See Manual:Preventing access and Manual:Combating spam Ciencia Al Poder (talk) 08:29, 20 May 2013 (UTC)

For your initial question (although you should read the page given by Ciencia Al Poder): add in your LocalSettings.php file:

$wgGroupPermissions['*']['edit'] = false; ~ Seb35 11:45, 20 May 2013 (UTC)

I'll try, thanks Lunablues (talk) 18:58, 21 May 2013 (UTC)

okay, thank you very much Lunablues (talk) 11:10, 26 May 2013 (UTC)

[RESOLVED] [detailed]no respond to any clicks/actions.

I just realized my previous post includes little to no information for people to help. so I am re-posting with details. . I am using MediaWIKI 1.20.5. PHP version: 5.3.25 MYSQL version: 5.2.0 . I tried to setup WIKI manually for about 2 times. although the installation was successfully, my WIKI site does not respond to any clicks or actions. . you can try it your self if you want. . here is my WIKI site: . http://mabi.thelongnight.net/ .

(its Chinese, but the point is. it does not respond to any click/actions)

. after using different browser I get error message regarding to the file: includes\objectcache\SqlBagOStuff.php . I am out of ideas now. . any help will be appreciated. . 123.3.241.68 (talk) 06:25, 20 May 2013 (UTC)

Update, the site often cancels the loading automatically for no reason.

.

I really need help on this... 123.3.241.68 10:37, 20 May 2013 (UTC)

I seriously have no idea about how and why.

PHP Notice: unserialize(): Error at offset 1209 of 2469 bytes in E:\Inetpub\MabiWIKI\includes\objectcache\SqlBagOStuff.php on line 430 PHP Notice: unserialize(): Error at offset 1749 of 1767 bytes in E:\Inetpub\MabiWIKI\includes\objectcache\SqlBagOStuff.php on line 430

.

.

.

my other forum site which is on the same server worked totally fine. 123.3.241.68 11:36, 20 May 2013 (UTC)

I do not see a PHP error. When you call a wiki page, e.g. the main page at http://mabi.thelongnight.net/index.php?title=Main_Page, you get a server error 500. Check the server logs to see what's happening! 88.130.123.15 12:16, 20 May 2013 (UTC)

the server log only said a person visited this site, nothing else...

if you turn off the "Show friendly HTTP error messages" in your internet options, you will see the actual error by then. 123.3.241.68 13:11, 20 May 2013 (UTC)

We are excited... 88.130.123.15 13:53, 20 May 2013 (UTC)

...what do you mean?...

well, the error message appeared to be:

.

PHP Notice: unserialize(): Error at offset 0 of 738 bytes in E:\Inetpub\MabiWIKI\includes\objectcache\SqlBagOStuff.php on line 430 123.3.241.68 14:29, 20 May 2013 (UTC)

All I see is a white page. You might also look at Manual:How to debug for some settings to put in your php.ini. ☠MarkAHershberger☢(talk)☣ 14:26, 20 May 2013 (UTC)

Facinating. Content-Length is sent, but no Content-Type, so Firefox doesn't show the content? Chrome does, though. Bug reported. ☠MarkAHershberger☢(talk)☣ 14:56, 20 May 2013 (UTC)

After reinstalling for about 10 times, I noticed an interesting phenomenon.

.

every time after installation, the wiki displays the correct main page.

.

however, the second after I click an internal link on the main page(e.g: click login / register)

.

The whole site becomes not accessible(e.g: display error or simply display a blank page).

.

Please do let me know if anything else can be done. 123.3.241.68 15:33, 20 May 2013 (UTC)

Could you enable the debug log after you install it but before you hit the main page for the first time?

That is, when you save the LocalSettings.php file, add

$wgDebugLogFile = "C:/temp/{$wgSitename}-debug_log.txt";

to the end of the file before you load the wiki for the first time.

Then reproduce the error and post the log file here or file a bug with the log file attached. ☠MarkAHershberger☢(talk)☣ 17:45, 20 May 2013 (UTC)

For some reason such file was not created, I made sure by reinstalling the WIKI for another 10 times.

.

However, I think I have found the cause/trigger of this error.

.

Everything works fine when English is selected(When creating the Local Setting file), error starts to display when Chinese is selected(When creating the Local Setting file).

.

I am almost certain that this error is triggered by the selection of "Chinese Language" during creation of the Local Setting file.

.

Hope that is enough for a bug report.

.

PS: this have taken me 24 hours to diagnose. 123.3.241.68 19:39, 20 May 2013 (UTC)

I think it is enough for a bug report, but you should note that you are using Windows IIS as a server -- that may be important. Please do file a report and link to it here. ☠MarkAHershberger☢(talk)☣ 20:01, 20 May 2013 (UTC)

bug reported:

https://bugzilla.wikimedia.org/show_bug.cgi?id=48659

Thanks for the help.

I will wait for the bug fix. 123.3.241.68 20:41, 20 May 2013 (UTC)

AFTER 3 DAYS, PROBLEM RESOLVED!

cause:

forgot to change MYSQL default setting to UTF8

it was latin1, thus when Chinese char is used, it fails. 123.3.241.68 20:56, 21 May 2013 (UTC)

Excellent! Thanks for letting us know. ☠MarkAHershberger☢(talk)☣ 12:04, 22 May 2013 (UTC)

Is there a way to disable localization cache?

Sorry for my bad English.

The page http://www.mediawiki.org/wiki/Manual:Developing_extensions contains this note info:

"While developing, you may want to disable caching by setting $wgMainCacheType = CACHE_NONE and $wgCacheDirectory = false, otherwise system message and other changes may not show up."

Localization cache still enabled in Database, or not? I think that this will not affect on Localization cache because in "includes/DefaultSettings.php(1844)":

/**
 * Localisation cache configuration. Associative array with keys:
 * class:       The class to use. May be overridden by extensions.
 *
 * store:       The location to store cache data. May be 'files', 'db' or
 *              'detect'. If set to "files", data will be in CDB files. If set
 *              to "db", data will be stored to the database. If set to
 *              "detect", files will be used if $wgCacheDirectory is set,
 *              otherwise the database will be used.
 *
 * storeClass:  The class name for the underlying storage. If set to a class
 *              name, it overrides the "store" setting.
 *
 * storeDirectory:  If the store class puts its data in files, this is the
 *                  directory it will use. If this is false, $wgCacheDirectory
 *                  will be used.
 *
 * manualRecache:   Set this to true to disable cache updates on web requests.
 *                  Use maintenance/rebuildLocalisationCache.php instead.
 */
$wgLocalisationCacheConf = array(
	'class' => 'LocalisationCache',
	'store' => 'detect',
	'storeClass' => false,
	'storeDirectory' => false,
	'manualRecache' => false,
);

We can see that also on $wgLocalisationCacheConf page.

As I understand it, initially Localization cache store only in file system, and $wgCacheDirectory used as trigger for disable/enable Localization cache. But than by adding future for storing localization cache in database and by mistake continue use $wgCacheDirectory as trigger. Therefore currently with parameters $wgMainCacheType = CACHE_NONE and $wgCacheDirectory = false Localisation Cache is still enebled and use datebase.

Currently is no way to disable localization cache? Am I right?

Is it a bug of mediawiki?

But in $wgCacheDirectory "Set this to false to not use any local caches." - Its mistake, because in this case localization cache still enabled and use datebase as storage?

And in Localization caching "After finding out that a large number of the cached objects above were interface messages, the bits of text that are not content, an advanced localisation cache was introduced. Set $wgCacheDirectory in LocalSettings.php to a valid path to use." - Its mistake too?

If I'm right, this may confuse extensions developers. (Its confuse me when I set hook $wgHooks['MessagesPreLoad'][] that not work, thanx debugging i find table with cache and modify expire column, for row with cached messages). I think its necessary to add in Developing extensions a note about it, somthing like this: "For rebuild Localization cache, you also should to set 'manualRecache' to true in $wgLocalisationCacheConf" and use "maintenance/rebuildLocalisationCache.php." Likemusic (talk) 16:20, 20 May 2013 (UTC)

MediaWiki has lots of caches. I think that you are confusing the two separate caches for translations:

1. Nowdays, the localisation cache caches messages from core and extension i18n php files. It can store the cache on the disk or in the database. It is managed via $wgLocalisationCacheConf.
2. The second cache is called message cache, it caches messages defined in MediaWiki namespace inside the wiki itself. It can store the cache on memcached, apc, on the database etc. This cache is managed via $wgMessageCacheType. Nikerabbit (talk) 06:00, 21 May 2013 (UTC)

As I now understand it, MessageCache has nothing to do with LocalisationCache.

I pointed out the contradictions in the documentation. I think it's a mistake that should be corrected. But I'm still not quite sure whether I am right in my judgment. And I do not know where to go next.

Maybe I should write this message to Bugzilla, and then one of developers who well versed in the architecture of the caches reply to this post? Likemusic (talk) 12:05, 9 June 2013 (UTC)

[RESOLVED] My Preferences page issue

My details: User Name: Rsmn

User id: 5877 on ta.wikipedia.org

MediaWiki 1.22wmf3 (c773203)

PHP 5.3.10-1ubuntu3.6+wmf1 (apache2handler)

MySQL 5.5.30-MariaDB-mariadb1~precise-log

LuaSandbox 1.6-1

Lua 5.1.4

For the last few days there was no edit option for leading paragraphs for me. When I browsed my preferences page, I found on my user profile, Member of group was mutilated as well as on gadjets tab, there were nothing against Appearance. Hence my option of add edit link to the leading paragraphs was not working. I dont know why my Preferences page got mutilated and I seek your help in setting things right. From the discussions on this page I undrstand this problem exists for other users also.

This issue seems to be resolved in my wiki by Rsmn (talk) 04:59, 21 May 2013 (UTC)

[RESOLVED] Intermittent "No file by this name exists, but you can upload it." problems

Hi, I have a mediawiki install and I'm getting this problem fairly frequently. A user uploads a file, but the resulting page says "No file by this name exists, but you can upload it." at the top, even though there's an entry for the file in the database and the file exists under the image directories like the others. I've tried deleting the page, deleting the file, re-uploading, but nothing works. Any suggestions? Here's an example of the problem: http://php.med.unsw.edu.au/cellbiology/index.php?title=File:CYK4_in_Central_Spindle_Formation.jpg

Thanks! Evilhayama (talk) 05:50, 21 May 2013 (UTC)

Looking at http://php.med.unsw.edu.au/cellbiology/index.php?title=Special:ListFiles, it looks like the "missing" files are not thumbnailed correctly, either.

Trying to run ImageMagick's convert on the file from http://php.med.unsw.edu.au/cellbiology/images/e/e7/Nuclear_reprogramming_03.jpg shows the following error:

$ convert -scale 50x50 Nuclear_reprogramming_03.jpg

convert.im6: no images defined `Nuclear_reprogramming_03.jpg' @ error/convert.c/ConvertImageCommand/3044. ☠MarkAHershberger☢(talk)☣ 15:10, 21 May 2013 (UTC)

reported upstream ☠MarkAHershberger☢(talk)☣ 15:18, 21 May 2013 (UTC)

Ok, so that was me being an idiot. The invocation I gave is wrong. ☠MarkAHershberger☢(talk)☣ 01:11, 22 May 2013 (UTC)

The problem looks fixed now, what'd you do? ☠MarkAHershberger☢(talk)☣ 01:36, 22 May 2013 (UTC)

Unfortunately I did nothing. Overnight it seems to have resolved itself, I believe it was when the web service restarted. I'm not sure what that could be, something broken with IIS or PHP that works again when it restarts? I'll look into it on my end, might not be a mediawiki issue. thanks for your help. Evilhayama (talk) 01:58, 22 May 2013 (UTC)

[Resolved] using https

Dear all I have tried looking for this and am surprised by my lack of luck/competence finding anything :-) We have a mediawiki

Product Version

MediaWiki 1.20.5

PHP 5.4.14 (apache2handler)

MySQL 5.5.31

The server can use https but if I try to use https the style sheet seems to be missing as everything is in a single column. The line below shows why.

<link rel="stylesheet" href="http://wiki.humanities.manchester.ac.uk/ECLR/load.php?

Clicking on load unsafe script displays the site fine but with the https icon crossed out. You can see this at:

https://wiki.humanities.manchester.ac.uk/ECLR/index.php/RobInf

How can I force the site to use https, I know about the performance hit but that can take a back seat to "security".

Cheers Paul Mcasspj (talk) 08:49, 21 May 2013 (UTC)

Configure $wgServer as protocol-relative, or with https:// instead of http:// Ciencia Al Poder (talk) 09:43, 21 May 2013 (UTC)

Magic thanks very much! Mcasspj (talk) 10:00, 21 May 2013 (UTC)

Most basic thing- don't know what my URL is.

I just made a MediaWiki site a few minutes ago, I have no idea what I am doing and I have no idea what the actual URL of the site is. I can access it via localhost, but I don't know what the URL is for other users. Sorry for the stupid question. 82.81.67.68 (talk) 17:19, 21 May 2013 (UTC)

It sounds like you are trying to run your wiki on your local computer. Unless it is on all the time and accessible from the Internet, this probably isn't what you want. ☠MarkAHershberger☢(talk)☣ 17:25, 21 May 2013 (UTC)

Need help regarding the wiki accesscontroll

Hello:

We are sys-admins working for a Europen corporation We currently need a accesscontroll extension options from mediawiki

To be shortly, our request regarding to like: Certain pages are fobidden for some user, and capable to view for some other users

We having been trying to get some extensions from Mediawiki website, but still can't make it work

And, anyone would provide some help?

/John

thanks 219.236.246.147 (talk) 10:46, 22 May 2013 (UTC)

If you have groups of pages that you want to apply these access controls to, you should look at Extension:Lockdown. If you've already looked at it, what did you try that it could not do? ☠MarkAHershberger☢(talk)☣ 12:01, 22 May 2013 (UTC)

Is it Possible to edit a page title in Mediawiki

I am trying to edit a page title that has already been created 216.59.124.162 (talk) 13:48, 22 May 2013 (UTC)

Not directly. However you may change the title by moving the the page to the new desired title. This requires the move permission. [[kgh]] (talk) 13:53, 22 May 2013 (UTC)

Thanks so much for the reply.

However, how do you do that? 216.59.124.162 18:10, 22 May 2013 (UTC)

Well the "move" tab is next to the "edit" and "history" tab at the top of the page. Obviously it is not there for you on the wiki. You should ask an admin on your wiki for assistance to move the page. [[kgh]] (talk) 07:25, 23 May 2013 (UTC)

Help:Moving a page Qgil (talk) 17:42, 23 May 2013 (UTC)

[Resolved] Toolbox Question and YES i did google and research my question via this site!

Greetings!

I run a mediawiki installtion 1.17 for my Help Desk department.

I recently installed a MultipleFile uploader. After i installed it, it automatically appeared in the Toolbox section. Upload files also appears as that is the default. I know i can modify the toolbox and what appears there in the skin we're using (vector), but how do i change capitalization and placement? I could just remove the original Upload file link, but i would want to move the Upload multiple files up in placement, and capitalize it. It does not appear in the vector skin.

Any help would be GREATLY appreciated!

BTW, the uploader works fine w/ no errors. Derek7467 (talk) 14:45, 22 May 2013 (UTC)

Looking at Extension:MultiUpload, it looks like it tells you to modify your MediaWiki:Sidebar to add the link for this. Can't you "move it up" in that page? That page also talks about editing the MediaWiki:Multipleupload message as you would need to to change the appearance of the message. ☠MarkAHershberger☢(talk)☣ 15:19, 22 May 2013 (UTC)

Stupid me, i didnt even think about checking the php code for the extension itself. THANKS! that did the trick! Derek7467 (talk) 15:25, 22 May 2013 (UTC)

Actually, question, how could i specify to include that MultipleUploader on Special Pages? I see that it drops off of all special pages and the original Upload file is there. Derek7467 (talk) 15:52, 22 May 2013 (UTC)

I think you'll find that problem will go away if you upgrade. ☠MarkAHershberger☢(talk)☣ 18:13, 2 June 2013 (UTC)

How to add more fields to the edit page

I am trying to add more fields to the edit page, how do you do that. I want to create an additional field to the Wiki Editor 216.59.124.162 (talk) 18:12, 22 May 2013 (UTC)

You should ask an admin on your wiki if this is possible to do that. [[kgh]] (talk) 07:30, 23 May 2013 (UTC)

 19:41, 27 January 2014 (UTC)

How to disable permission for switching skins?

I want to disable the permissions for allowing my users to switch skins, but I can't find it anywhere. My MediaWiki version is 1.20.4. My PHP version is 5.3.23, and my MySQL version is 5.5.23-55. 74.190.244.196 (talk) 18:57, 22 May 2013 (UTC)

Set $wgSkipSkins in LocalSettings.php, e.g. $wgSkipSkins = array("chick", "cologneblue", "nostalgia", "simple", "standard", "monobook");.

See also Manual:Skin_configuration. 88.130.127.141 19:31, 22 May 2013 (UTC)

That would be good to disable some skins, while keep other skin options available.

To turn off completely that preference option, use this:

$wgHiddenPrefs[] = 'skin'; Ciencia Al Poder (talk) 09:17, 23 May 2013 (UTC)

How to know which extensions are used ?

Hi

I think that a lot of extensions on my wiki are just installed and never used.

I'm trying to know which extensions are really used but I don't know how ?

Someone can help me ?

Thanks in advance Lutch 2904 (talk) 07:31, 23 May 2013 (UTC)

Heiya, have a look at WikiAPIary. This wiki collects all sorts of useful information on wikis running MediaWiki including extensions and their usage. Also, when looking at the extension's pages on this wiki you will see a little info at the bottom of the box displaying infos on the extension which says "Check usage and version matrix". Just click on it and it will bring you where some music is. :) Cheers [[kgh]] (talk) 14:34, 23 May 2013 (UTC)

Ouch, I think I did not get your question right in the first place. Well in case an extension provides a parser function or a tag you can look for their usage on pages. Other extensions provide logging which indicate their usage. It really depends on the extension. [[kgh]] (talk) 14:47, 23 May 2013 (UTC)

I don't think there is a good way how to do that. However, you can find articles that use a syntax with this SQL statement

SELECT page_title as "Seite",

Concat('<YOUR_WIKI_URL>/index.php?title=', page_title) AS "Link"

FROM page

LEFT JOIN revision AS R

ON page_latest = R.rev_id

LEFT JOIN text AS T

ON rev_text_id = T.old_id

WHERE Lower(T.old_text) LIKE '%<YOUR_QUERY>%';

That way you can search for raw content in pages. 2001:780:0:B:3099:2B9B:69D1:D4F2 (talk) 13:54, 4 August 2015 (UTC)

Title-Tag in Thumbnails

Hallo Community, ich habe einen [[File:...|thumb|...]]-Tag und möchte das HTML-TITLE-Attribut setzen (für "fancyBox"). Hat jemand 'ne Idee? Viele Grüße. 87.152.47.252 (talk) 08:03, 23 May 2013 (UTC)

You should always write in English here, otherwise only a few will be able to help you. The help page on images contains everything available about images. [[kgh]] (talk) 14:40, 23 May 2013 (UTC)

How to switch off saving of every version of page

By default, MediaWiki saves a full copy of every version of every page on the wiki. Is it possible to switch off saves every version. I need only last version of page? This will let me avoid DB size growth.

It there is no oportunity to switch it off. Is there posibility to remove (not compress) old versions of pages? Thanks in advance.

YS 93.182.23.86 (talk) 09:44, 23 May 2013 (UTC)

Hi!

It is not possible to stop MediaWiki from saving a complete copy of each page each time when saving the page. But what you can do is use the maintenance script DeleteOldRevisions.php, possibly as a cron job, to remove all old revisions. 88.130.100.151 13:08, 23 May 2013 (UTC)

Supppper! It should be good enought for me.

Thanks. 93.182.23.86 14:51, 23 May 2013 (UTC)

You're welcome! :-) 88.130.100.151 17:32, 23 May 2013 (UTC)

Extention:EmailToWiki. Emails didn't appear in wiki

We inslalled extention EmailToWiki. We are beginners. We followed instruction on extention page. But emails didn't appear in wiki. Сontents of EmailToWiki.conf file are next:

# Name of the wiki which the emails will populate (must be running on the same host)
$::wiki = "https://192.***.2.7/";

# The wiki template to wrap the email paramaters in
$::template = "Email";

# Extract just the email address portion of the FROM and TO fields
$::emailonly = 1;

# Don't import emails into the wiki if the From address isn't registered in the wiki
$::fromfilter = 0;

# If there's HTML formatting in the email don't also add <pre> sections for non-HTML versions of the content
$::html_only = 0;

# Details of the POP or IMAP server to check for messages
$::type = "IMAP";
$::host = "192.***.2.210";
$::user = "mediawiki@navi*****.com";
$::pass = "mwnavis2013";

# Delete messages after processing them
$::remove = 0;

# Maximum amount of message to download
$::limit = 20000000;

# Format of the title for the corresponding article in the wiki
$::format = "Email:\$id (\$subject)";

# The user the webserver runs as
$::owner = "www-data";

1; We created template Template:Email which contains: {| style="background-color:#eee;border: solid 1px black; padding: 5px" |- !align=left|From: |{{{from}}} |- !align=left|To: |{{{to}}} |- !align=left|Date: |{{{date}}} |- !align=left|Subject: |{{{subject}}} |} Could anybody help us?

Kate 23.05.2013 84.204.22.130 (talk) 12:03, 23 May 2013 (UTC)

Hi Kate, I think I heard somewhere that this extension is broken. However, do not quote me on this one. You should direct your question to its talk page, or contact the developer. Cheers [[kgh]] (talk) 14:43, 23 May 2013 (UTC)

[RESOLVED] SQL statements that are taking 10,000 to 26,000 milliseconds

Product Versions

MediaWiki 1.21alpha (35f559d)

PHP 5.3.17 (apache2handler)

MySQL 5.1.50-MariaDB-log

Wiki: elinux.org

Occasionally, I see a massive slow down of my wiki due to SQL queries such as:

3049.511 s Time:26,600 ms Call count:1379

SELECT /­* Job­Queue­DB­:­:claim­Random Wmat */­ * FROM `job` WHERE job_­cmd = ? AND job_­token = ? AND ­(job_­random >= ?­)­ ORDER BY job_­random ASC LIMIT ?

3468.882 s Time:10,100 ms Call count:618

UPDATE /­* Job­Queue­DB­:­:claim­Random Wmat */­ `job` SET job_­token = ?,­ job_­token_­timestamp = ?,­ job_­attempts = job_­attempts+? WHERE job_­cmd = ? AND job_­id = ? AND job_­token = ?

I can't seem to find any references to this anywhere. Any thoughts on how to fix this?

Thanks Bill Wmat (talk) 20:57, 23 May 2013 (UTC)

bugzilla:42614? Ciencia Al Poder (talk) 09:31, 24 May 2013 (UTC)

Thanks you kindly, apparently my search-fu is poor. Wmat (talk) 13:56, 24 May 2013 (UTC)

[RESOLVED] How can I list all pages, which contain a certain text?

[RESOLVED] Install editor error

Hi guys!

I upgrade mediawiki 1.17 to 1.20.5 and all articles and pictures works fine, but editors don't work. I tried to upgrade and install last versions of: - FCKEditor - CKEditor - VisualEditor - Wysiwyg Any work. Sometimes don't editor doesn't work and other I can't see my wiki.

I can't see any error in logs files. What could be the problem? Any idea ?

Thanks Infopsm (talk) 08:39, 24 May 2013 (UTC)

These editors are not supported anymore. What you could try is WikiEditor, but it is not a real WYSIWYG editor.... 88.130.125.119 15:38, 24 May 2013 (UTC)

Hi,

I install last version of wikieditor and works fine, but i need write in wiki format. With the others editors (FCKEditor, CKEditor...) I can write and then itself change automaticaly to wiki text format.

Can I find any editor that can do it?

I will finish more quickly to edit articles.

Thanks. Infopsm (talk) 09:48, 27 May 2013 (UTC)

Currently there is a gap.

WYSIWYG extension is unfortunately not picked up by someone.

you can get it to work by spending 2 days of trying some patches, or by installing an older MW.

I think it is dying at the moment for the following reason:

A new (very cool) editor VE is in development. The disadvantage is that it is not ready yet, and you need to install parsoid. So you need install (apt-get) rights on your server.

They promised a solution for that in a couple of month (from july 2013) but i think the team is somewhat overloaded at the moment, so it might be a bit optimistic. My guess is also that it will be pushed forward, as they have mainly wikipedia in mind.

I would go for VE if possible, else install mw 1.17. and use Extension:WYSIWYG 213.224.16.158 08:45, 19 July 2013 (UTC)

How to use Nuke DPL for deleting based on a date?

I want to delete all information posted before the 1th of Januari 2011 on a wiki site. In the standard criteria of Nuke DPL I don't find the possibility to select on date. In the DPL manual I find the possibility to select for instance 'Last revisions before....) That would help me if it would work.. but it does not. The standard criteria which are in the page tool field do work well. Can somebody help me out? Thanks, Akke

Some information about the wiki version we use: - Product Version MediaWiki 1.22wmf4 (646544a) PHP 5.3.10-1ubuntu3.6+wmf1 (apache2handler) MySQL 5.5.30-MariaDB-mariadb1~precise-log LuaSandbox 1.6-1 Lua 5.1.4 LG47FB (talk) 12:20, 24 May 2013 (UTC)

[RESOLVED] Short urls makes my wiki inaccessible

I can't access my wiki after applying the changes needed for short urls. In my .htaccess file, I added:

RewriteEngine On
RewriteRule ^/?guides(/.*)?$ %{DOCUMENT_ROOT}/guides/index.php [L]

RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?guides/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/guides/thumb.php?f=$1&width=$2 [L,QSA,B]

RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?guides/images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/guides/thumb.php?f=$1&width=$2&archived=1 [L,QSA,B]

and in my LocalSettings.php file, I added this code:

$wgArticlePath = "{$wgScriptPath}/$1";
$wgUsePathInfo = true;

Here's the link to my wiki: http://kingdomhearts7.com/guides/Kingdom_Hearts_7. My MediaWiki version is 1.20.4. My PHP version is 5.3.23, and my MySQL version is 5.5.23-55. 74.190.238.179 (talk) 13:39, 24 May 2013 (UTC)

Could this be a problem with my host? I'm hosted with HostGator. Please, can anyone help me? 74.190.246.147 13:36, 25 May 2013 (UTC)

Never mind. I figured out what the problem was. 74.190.246.147 16:43, 25 May 2013 (UTC)

Unable to edit sections/ edit window is very small

Our wiki has two problems that seem to have come up at the same time. The first: The edit button is visible at the top of the page, but not above any of the page titles. We have a specific page that everyone is trained to just click the edit above the title.

The other issue is that if you do manage to get into the edit view for a page, the windows is only a couple lines tall.

I can't provide a link to it as it's an internal, company specific wiki. Here's the wiki info though.

    MediaWiki: 1.11.0
   PHP: 5.2.6-3ubuntu4.6 (apache2handler)
   MySQL: 5.1.63-log 50.39.144.98 (talk) 16:14, 24 May 2013 (UTC)

We actually figured out that this was an error in our database, causing a couple errors including these two. We're restoring to before and that should fix it. 50.39.144.98 16:35, 24 May 2013 (UTC)

[RESOLVED] Possibility of changing links in the upper navigation?

Hey there, is there a possibility of changing the "Create Account" link in the upper navigation? I don't want to change the text, I only want to change the link. Regards, Abrafix Abrafix (talk) 12:59, 25 May 2013 (UTC)

You can change the User Links through the PersonalUrls Hook. Abrafix (talk) 10:11, 26 May 2013 (UTC)

How to insert image from other web resources?

I use this code to insert an image which was uploaded to my wiki

[[File:file.jpg|200px|thumb|left|Description]]

But how can I make additional option to use direct url to the image insted of "File:file.jpg"??? Fokebox (talk) 16:08, 25 May 2013 (UTC)

There's a configuration setting for allowing any image to be added by adding the URL, however, this creates security issues. Depending on the popularity of your wiki and the extent to which pages are edited by multiple users, it could by exploited by an attacker to get the IP addresses of users.

I recommend using this method: Using an image gallery with MediaWiki

You can modify it for use with an existing image host. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 07:43, 27 May 2013 (UTC)

Now I mean how to make an extension which has the same principle like:

[[http://urltoimage.com/image.jpg|200px|thumb|left|Description]]

Fokebox (talk) 20:03, 29 May 2013 (UTC)

I'm not sure if an extension can do that, but the method I described on that page does the same thing. It's better than the example there because you only want people to be able to add images from approved websites because otherwise it's possible for an attacker to gather information on users. Plus if your website is popular, the admin of an unpopular website could use embedding images on your website as a way of dishonestly generating page views. As for the security risk, it's very severe. If you don't have a lot of users and most of them edit the same pages, it's especially severe. An attacker could plant images on your website from his server to gather the IP addresses and computer information of specific users. You also might not know that the pages had images planted on them, because it doesn't need to be an image you can see; the attacker could plant a 1x1 pixel image the same color as the background, and it would still function to gather data. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 04:48, 2 June 2013 (UTC)

HTML code appears in pages

I'm having a problem where pages show up a HTML code. When editing pages, they are showing fine. wgRawHtml doesn't do anything. Any ideas what could be the problem?

http://i.imgur.com/ePF5GBa.png 86.60.219.97 (talk) 22:27, 25 May 2013 (UTC)

Seems like I can't edit, don't know why. The problem started when we moved to another server. We just copied files over and imported sql. 86.60.219.97 00:54, 26 May 2013 (UTC)

Try running refreshLinks.php for the files.  Hazard-SJ  ±  03:23, 26 May 2013 (UTC)

Thanks for your response. I got following error:

# php refreshLinks.php

PHP Warning: Module 'geoip' already loaded in Unknown on line 0

Refreshing redirects table.

Starting from page_id 1 of 260.

100

200

Refreshing links table.

Starting from page_id 1 of 260.

PHP Fatal error: Call to a member function getNamespace() on a non-object in /var/www/03_tim_wiki/extensions/TinyMCE_MW/TinyMCE_MW.php on line 75

Fatal error: Call to a member function getNamespace() on a non-object in /var/www/03_tim_wiki/extensions/TinyMCE_MW/TinyMCE_MW.php on line 75

Problem is this line:

$ns = $wgTitle->getNamespace();

It appears in two places. I don't know PHP so I tried commenting it. Script ran then:

PHP Warning: Module 'geoip' already loaded in Unknown on line 0

Refreshing redirects table.

Starting from page_id 1 of 260.

100

200

Refreshing links table.

Starting from page_id 1 of 260.

100

200

Retrieving illegal entries from pagelinks... 0..0

Retrieving illegal entries from imagelinks... 0..0

Retrieving illegal entries from categorylinks... 0..0

Retrieving illegal entries from templatelinks... 0..0

Retrieving illegal entries from externallinks... 0..0

Retrieving illegal entries from iwlinks... 0..0

Retrieving illegal entries from langlinks... 0..0

Retrieving illegal entries from redirect... 0..0

Retrieving illegal entries from page_props... 0..0

As far as I can see, nothing has changed. 86.60.219.97 09:04, 26 May 2013 (UTC)

Interwiki categories?

Is that at all possible? If not, would it be possible to restrict reading of individual pages like can be done with whole wikis? (Or... users seeing pages depending on rights?) 31.54.196.149 (talk) 01:52, 26 May 2013 (UTC)

Paid Subscriptions to Join and Edit a MediaWiki Wiki?

Paid Subscriptions to Join and Edit a MediaWiki Wiki? Is there a way/extension to create a membership website out of MediaWiki so that someone has to pay to join and either is charged once or on a recurring basis? Thanks. EarnMoney (talk) 03:35, 26 May 2013 (UTC)

You could use ConfirmAccount to restrict account creation to paid users and use Widgets to embed PayPal buttons. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 07:31, 27 May 2013 (UTC)

Edit toolbar's gone missing

I just installed MediaWiki and I enabled the editing toolbar as well as the Advanced Editor. After editing my wiki for several hours, the toolbar just magically disappeared and I have no idea why! Now it's just a plain text-box.

I miss my editing functions, do you know what might have gone wrong?

Config details

• MediaWiki 1.19.7
• PHP 5.2.17 (apache2handler)
• MySQL 5.1.57 Deathgleaner (talk) 04:46, 26 May 2013 (UTC)

I just put a question here and saw your issue.

I have this issue, too, here and then.

I am on OSX and I think it has to do with javascript. For some reason it seems to crash now and then.

In my opinion it happens more often when using Chrome.

When that's the case I have no toolbar (as you mentioned) and other extensions using javascript won't work no more.

When I quit and restart the browser, it works again. 79.232.32.56 09:35, 26 May 2013 (UTC)

Look at the error console of your webbrowser for any Javascript error. Ciencia Al Poder (talk) 14:57, 26 May 2013 (UTC)

On Chrome all I get is

Uncaught SyntaxError: Unexpected token < </pre>
and Firefox I get:
<pre>Timestamp: 5/26/2013 7:00:00 PM
Error: SyntaxError: syntax error
Source File: http://wiki.phlemcraft.com/load.php?debug=false&lang=en&modules=startup&only=scripts&skin=vector&*
Line: 20
Source Code:
<script type="text/javascript" src="http://stats.hosting24.c

Timestamp: 5/26/2013 7:00:00 PM
Error: SyntaxError: syntax error
Source File: http://wiki.phlemcraft.com/load.php?debug=false&lang=en&modules=skins.vector&only=scripts&skin=vector&*
Line: 6
Source Code:
<script type="text/javascript" src="http://stats.hosting24.c

Deathgleaner (talk) 02:03, 27 May 2013 (UTC)

Look the source file which gives the error: . At the end of the file, your hosting is injecting HTML code that breaks the script. It's supposed to be a JavaScript file, no HTML is permitted there, hence the error.

Look if you can disable that in your host's control panel, or ask your host for support for removing that. It's common for free hosting service to inject codes so ads appear on pages. If that's the case you should move to another (paid) hosting. Ciencia Al Poder (talk) 09:13, 27 May 2013 (UTC)

The edit toolbar has never worked for me since it stopped working. Even if I restart my computer or switch browsers. Deathgleaner (talk) 01:52, 27 May 2013 (UTC)

please check your preferences. One of the options can be "Enable section editing via [edit] links" 162.38.184.116 08:01, 17 September 2013 (UTC)

[RESOLVED] Removing spam protection

Hi, I don't know how it's called and can't find anything in my searches. When somebody who is not logged in creates or edits a page he has to enter the result of a calculation.

This feature is not required in my case, my wiki is pure intranet where I know the IPs. And I want people to encourage to correct typos and false information.

Can somebody please tell me how to get rid of this calculation box?

Thanks in advance. 79.232.32.56 (talk) 09:28, 26 May 2013 (UTC)

Have you installed the ConfirmEdit Extension? Abrafix (talk) 10:14, 26 May 2013 (UTC)

Yes, that's it!

I don't why that was in my LocalSettings.php or why I put it in.

Thanks very much! 79.232.32.56 13:03, 26 May 2013 (UTC)

Extension:MaintenanceShell

hi how can I use Extension:MaintenanceShell because ive installed it and it keeps saying javascipt needs to be enable but it is enable if that extension dopesent work what other extension or how to run the maintanice scrpts 81.129.84.113 (talk) 19:17, 26 May 2013 (UTC)

Well, the recommended way to run the maintenance scripts is from the shell. 88.130.115.84 19:39, 26 May 2013 (UTC)

how can I run shell which programs or extensions can I use for shell 81.129.84.113 20:19, 26 May 2013 (UTC)

Ähh, that depends on your plattform: If your local PC is using Linux, then you do not need a special programm; you already have it. If you are running on Windows, then you need one; I recommend "Putty". Then you can connect to your server using the SSH protocol (as opposed to FTP or HTTP). 88.130.115.84 20:33, 26 May 2013 (UTC)

oh but I use servers free which is a free web hosting and I have tried using putty but it doesent work for me 81.129.84.113 09:15, 27 May 2013 (UTC)

Free hosting often does not offer SSH access.

You can search for other MediaWiki extensions, which offer this functionality, but you might have other problems trying to run these extensions then: Free hosters often disable certain PHP functions (like exec for example). However, such functions often are needed to run the maintenance scripts.

What you could try as a last idea, is: Run the maintenance scripts from the webbrowser. They are not made for that and I don't know if it works, but it's worth a try.

You can get rid of all these problems easily: Go to a reasonable hoster. 88.130.69.102 12:57, 27 May 2013 (UTC)

So if I get go daddy will ssh work with that 81.156.238.248 15:16, 27 May 2013 (UTC)

Check what GoDaddy says: If they offer SSH, you will at least be able to execute these scripts. This does not mean that they are actually working. They can still disable certain functions so that in the end the scripts don't work. Apart from that I remember guys who had problems with the GoDaddy support.

What you generally can say is: You get what you pay for.

The cheaper your hoster is (or if it's even for free), the more problems you are going to have. 88.130.69.102 15:46, 27 May 2013 (UTC)

Recurring error on Bigotry Wiki

I frequently get this error when accessing particular pages on Bigotry Wiki, especially the Data category page.

Fatal error: Call to a member function setEditSectionTokens() on a non-object in /home/content/01/7537801/html/sashaweb.net/bigotwiki/includes/parser/ParserCache.php on line 187

Adding ?action=purge to the URL solves the problem.

It uses SQLite, if that could be the cause of it somehow. Lieutenant Aleksandr Reznov 07:26, 27 May 2013 (UTC)

Can you provide a way to reliably reproduce this? ☠MarkAHershberger☢(talk)☣ 03:49, 2 June 2013 (UTC)

You can go to http://bigotry.sashaweb.net/Category:Data I wish I could give better information on reproducing the error. That page seems to generate it the most. Creating an account might work, because I've noticed some errors occurred only while logged in. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 04:50, 2 June 2013 (UTC)

Do you get any output before the error happens? Meaning: Can you see, which pats of the page are given out correctly and where you suddenly only get the error? 88.130.80.241 11:54, 2 June 2013 (UTC)

That page consistently shows the error for me. Adding ?action=edit brings up the editing page, though. ☠MarkAHershberger☢(talk)☣ 18:00, 2 June 2013 (UTC)

Sorry, that should have been ?action=purge, not edit. ఠ_ఠ Inquisitor Sasha Ehrenstein des Sturmkrieg Sector (Talk) (Contr) 20:40, 2 June 2013 (UTC)

Sure, you said that. I was just saying how I got at the page content. This looks like a bug. Could you file one and CC me or put the bug number here? ☠MarkAHershberger☢(talk)☣ 21:15, 2 June 2013 (UTC)

Mediawiki for private and public use - search restrictions

I would like to restrict several mediawiki pages. I use the extension CategoryPermissions. But an anonymous user can search for a word and show pages that have that word, though he can not see the page, but knows that this word is in my wiki. I want to restrict the use of search only for some groups of users. And knowing that my content is protected. 193.152.196.212 (talk) 08:58, 27 May 2013 (UTC)

You should file a bug to request this feature. ☠MarkAHershberger☢(talk)☣ 15:37, 1 June 2013 (UTC)

URL format for mediawiki

Hi,

I can access the pages of my wiki using an URL format like this:

mydomain/wiki/index.php/Topic

However, I would like to eliminate the "index.php" from the URL, so that the URL format would be:

mydomain/wiki/Topic

I already tried it out but the pages are not found. How can I do that?

Thanks Magnus 188.174.134.254 (talk) 12:43, 27 May 2013 (UTC)

What webserver are you using? – Allen4names (IPv6 contributions) 18:28, 27 May 2013 (UTC)

I am using Apache 2 (Debian Squeeze). 188.174.134.254 02:02, 28 May 2013 (UTC)

Check to see if alias.conf and alias.load (files or links) can be found in /etc/apache2/mods-enabled. These will allow you to use Alias in your configuration file. For example...

Alias /wiki "/var/www/mediawiki-1.21.0/index.php"
Alias /w "/var/www/mediawiki1-1.21.0"

I hope this helps. – Allen4names (IPv6 contributions) 04:11, 28 May 2013 (UTC)

The properly way to do that is as described on the Manual:Short URL/Apache. Ciencia Al Poder (talk) 09:38, 28 May 2013 (UTC)

Unfortunately, both solutions do not work for me.

Note that my web server runs inside an Apache VirtualHost...

As specified somewhere in the installation instructions, I included /etc/mediawiki/apache.conf. This file contains an Alias rule:

Alias /wiki /var/lib/mediawiki

But in the same file there is a comment saying that this "does not work properly with virtual hosts".

However, I tried it with and without this Alias in combination with the Rewrite-Rule pointed to by Ciencia Al Poder:

RewriteEngine On

RewriteRule ^/?wiki(/.*)?$ %{DOCUMENT_ROOT}/w/index.php [L]

Whenever I want to access my wiki with the short URL (/wiki/Topic), the page is displayed without style. I assume that CSS files are not found. I also receive this error in the apache error log:

File does not exist: /var/lib/mediawiki/Topic

What else can I do?

Thank you

Magnus 195.200.70.53 11:13, 31 May 2013 (UTC)

Unfortunately, both solutions do not work for me.

Note that I use a virtual host.

/etc/mediawiki/apache.conf contains an Alias:

Alias /wiki /var/lib/mediawiki

I added the following Rewrite rules:

RewriteEngine On

RewriteRule ^/?wiki(/.*)?$ /var/lib/mediawiki/index.php [L]

But when I access /wiki/Topic, the page loads without styles (CSS).

What else can I do?

Thanks

Magnus 195.200.70.53 11:37, 31 May 2013 (UTC)

You shouldn't mix alias and rewrite for this.

If you're using virtual host, drop the alias and rewrite rules and just use this:

DocumentRoot /var/lib/mediawiki

RewriteEngine On

RewriteRule ^/?wiki(/.*)?$ %{DOCUMENT_ROOT}/index.php [L]

Be sure to include a <Directory "/var/lib/mediawiki"> definition inside the VirtualHost Ciencia Al Poder (talk) 16:12, 31 May 2013 (UTC)

If what you mean you want mydomain/wiki/Topic you go in to .htaccess file or create one then you add the following codes and change them to the current page where your wiki located

RewriteEngine on

RewriteRule ^wiki/(.*)$ /main/index.php?title=$1 [L,QSA]

And then in localsettings.php.php add

$wgArticlePath = "/wiki/$1";

And then when you edit you wiki it will show /wiki/index.php/title when you edit the wiki or when viewing it will show /wiki/title 176.26.166.20 17:03, 3 June 2013 (UTC)

This is already explained and documented in Manual:Short URL/Apache. The problem the user is having is mixing alias with rewrite. Ciencia Al Poder (talk) 19:02, 3 June 2013 (UTC)

Hello,

sorry for the delay.

I wanted to follow your recommendations, but I believe that these do not match my configuration:

You recommended the following directive:

DocumentRoot /var/lib/mediawiki

Well, this comes into conflict with my configuration:

I have a virtual host for mydomain:

<VirtualHost *:80>

...

DocumentRoot /home/www/mydomain

...

Include /home/www/wiki.cfg

</VirtualHost>

Then, wiki.cfg contains the directives for the wiki. If I include a DocumentRoot directive there, then it would be in conflict with the other one.

Remember, my goal is this:

mydomain:

access my web page as without the wiki

mydomain/wiki:

This should contain the wiki, and mydomain/wiki/Topic should be the URL for the topic "Topic".

What can I do?

Thanks

Magnus 195.200.70.52 06:21, 10 January 2014 (UTC)

DocumentRoot is not needed here nor mentioned in Manual:Short URL/Apache. Just follow the instructions there Ciencia Al Poder (talk) 15:27, 10 January 2014 (UTC)

Very slow Page Load on small Mediawiki Installation

Hi, I am running a small, closed Mediawiki installation. Page loading takes about 10-15 sec and about 2.5 sec per Request (Page, css, js).

The Versions and Extensions I use are: MediaWiki 1.19.2, PHP 5.3.8 (apache2handler),MySQL 5.0.77-community-nt Replace Text, User Merge and Delete, MsUpload, Add Article to Category, DynamicSidebar, Lockdown, WikiEditor

I went through the Mediawiki tuning documentation and tried several caching alternatives like memcache, filecache, apc, ... with no improvement in loading time.

The Profiling output with and without caching is available here: http://stackoverflow.com/questions/16719023/mediawiki-profiling-output-interpretation

Any suggestions on how to improve the performance of my Installation or what exactly the profiling output tells you would help a lot. Thanks in advance! 188.20.65.18 (talk) 13:24, 27 May 2013 (UTC)

How much memory (RAM) does your server have? If it is only a small amount, then your wiki will be slow. ☠MarkAHershberger☢(talk)☣ 15:35, 1 June 2013 (UTC)

How to make a blank page?

Hey, I need an blank page with one simple echo giving some output from an extension. For example: if I got to http://wiki.somenameoftheserver.com/w/index.php?title=Special:SomeSpecialPage&mode=blankpage I want to see a blank page with one line giving some specific output. How can I do that? Or how can I stop to view the rest of the MediaWiki page? Regards, tomabrafix Tomabrafix (talk) 13:52, 27 May 2013 (UTC)

Fatal exception of type MWException after install MW 1.21.0 (MySQL5, PHP5)

1) Sorry for my broken englisch :-/

2) If I enable $wgShowExceptionDetails in LocalSettings.php, the following errors are display on the screen:

No cache directory configured

Backtrace:

1. 0 /homepages/24/d450278213/htdocs/lumysearch/extensions/LocalisationUpdate/LocalisationUpdate.class.php(553): LocalisationUpdate::filename('de')
2. 1 /homepages/24/d450278213/htdocs/lumysearch/extensions/LocalisationUpdate/LocalisationUpdate.class.php(36): LocalisationUpdate::readFile('de')
3. 2 [internal function]: LocalisationUpdate::onRecache(Object(LocalisationCache), 'de', Array)
4. 3 /homepages/24/d450278213/htdocs/lumysearch/includes/Hooks.php(255): call_user_func_array('LocalisationUpd...', Array)
5. 4 /homepages/24/d450278213/htdocs/lumysearch/includes/GlobalFunctions.php(3883): Hooks::run('LocalisationCac...', Array)
6. 5 /homepages/24/d450278213/htdocs/lumysearch/includes/cache/LocalisationCache.php(796): wfRunHooks('LocalisationCac...', Array)
7. 6 /homepages/24/d450278213/htdocs/lumysearch/includes/cache/LocalisationCache.php(426): LocalisationCache->recache('de')
8. 7 /homepages/24/d450278213/htdocs/lumysearch/includes/cache/LocalisationCache.php(310): LocalisationCache->initLanguage('de')
9. 8 /homepages/24/d450278213/htdocs/lumysearch/includes/cache/LocalisationCache.php(245): LocalisationCache->loadItem('de', 'fallback')
10. 9 /homepages/24/d450278213/htdocs/lumysearch/languages/Language.php(3978): LocalisationCache->getItem('de', 'fallback')
11. 10 /homepages/24/d450278213/htdocs/lumysearch/languages/Language.php(230): Language::getFallbacksFor('de')
12. 11 /homepages/24/d450278213/htdocs/lumysearch/languages/Language.php(189): Language::newFromCode('de')
13. 12 /homepages/24/d450278213/htdocs/lumysearch/includes/Setup.php(497): Language::factory('de')
14. 13 /homepages/24/d450278213/htdocs/lumysearch/includes/WebStart.php(161): require_once('/homepages/24/d...')
15. 14 /homepages/24/d450278213/htdocs/lumysearch/index.php(55): require('/homepages/24/d...')
16. 15 {main}

what should i do now?

thank you for youre help :-) 77.117.246.1 (talk) 17:03, 27 May 2013 (UTC)

The problem seems to be Extension:LocalisationUpdate.

Did you download the extension that matches the 1.21 release? If not, please, upgrade the extension. Ciencia Al Poder (talk) 20:42, 27 May 2013 (UTC)

I've Just deleted that line and it seems to work fine 193.52.24.83 00:22, 17 November 2013 (UTC)

I hope you deleted the line that includes Extension:LocalisationUpdate and not a line inside of the extension's file, otherwise it can have a performance impact in your wiki. Ciencia Al Poder (talk) 09:49, 17 November 2013 (UTC)

There is a problem in that extension because I had 1.22 and it had a problem in that too and now I have 1.23 and it still has it I changed a setting then changed it back not sure if it had fixed it yet 2.124.130.208 11:55, 23 November 2013 (UTC)

This issue seems described here: Extension_talk:LocalisationUpdate#In_1.21.2_blocks_wiki Ciencia Al Poder (talk) 12:55, 23 November 2013 (UTC)

Spezial:Import fehlt

Ich habe gerade eben auf meinem Webspace MediaWiki installert. Da das Importiren via importDump.php aufgrund dem leider nicht abschaltbaren safeFTP nicht funktioniert, wollte ich die Seiten (es sind nicht so viele) per Spezial:Import importieren- aber diese Speziallseite gibt es nicht! Wieso nicht? 188.118.242.48 (talk) 19:06, 27 May 2013 (UTC)

pronblem gelöst. 188.118.242.48 19:37, 27 May 2013 (UTC)

Ich kann das Problem reproduzieren. Die Seite "Spezial:Import" gibt es nicht. Bei mir geht es, wenn ich stattdessen die Seite "Special:Import" (mit "c") aufrufe. 88.130.69.102 19:38, 27 May 2013 (UTC)

Very slow MW website, possibly due to database

Hello everyone,

My MediaWiki site is extremely slow and goes down due to congestion several times a day. I have tried almost all help that I could find on Internet but the site is still very very very slow. Please help! Here are the details:

I setup this site in 2006 using MW 1.14 (if I remember correctly)… I have changed three servers since then.

Total pages: 60,000 Charset: Unicode (Hindi Devanagari) Current config: MW 1.20.3 ; MySql 5.1.68; PHP 5.3.23 Server: it's a VPS on which I have complete access ; 1800 MB is available RAM Traffic: close to 1.5 million page views per month… 1,25,000 visits per month

I believe that it is the database that is causing problem because I have thousands of entries in slow-query-log but I don't know what to do with this information. Am I supposed to go into the core MW files and do tweaking with SQL queries?

When I try to OPTIMIZE TABLE through phpMyAdmin –it says that the table are not optimizable.

What database maintenance tasks I need to perform regularly to keep the database in good shape?

Please help. I shall be grateful. Lalit Kumar (talk) 09:04, 28 May 2013 (UTC)

Hi Lalit,

What do you have in the slow-query-log? Always the same few queries, which are slow? Or many many different queries, which are slow? And what is the average time they need?

Which table engines are you using in MySQL? InnoDB is recommended (only a few tables have to be MyISAM). However, both InnoDB and MyISAM should be optimizable. Maybe optimizing works better, when you do not use PHPMyadmin (which might run into a PHP timeout), but when you optimize the tables from the commandline with something like "mysqldump --opt". This is also something which I am doing regularly: Keeps the DB in good shape and gives me a backup. ;-)

Other ideas: When you say charset "Unicode" that is fine. Do you have the PECL extension for PHP installed? It might give you better performance with regards to UTF-8 conversions. Make sure that really everything in your wiki is UTF-8. DB server, DB setting, tables, columns, frontend output... Are you using an opcode cache? You might get better performance when you use one.

Generally MediaWiki should be working with your amount of page views. Wikipedia uses the release versions (with a few minimal changes) and they are running fine as well. So I would say that you do not have to modify the MW source code in order to get better results. 88.130.97.188 11:08, 28 May 2013 (UTC)

Thanks a bunch buddy!

1) slow-query-log shows a vast variety of queries. So, I guess it is not a particular query that is taking the whole site down.

2) In the same context, I have a curiosity. If there is a particular query that is taking forever -what would you have done? Would you have optimize it and change it in core MW files? I wonder, if that is the case, don't all the MW sites would face the problem due to that unoptimized query (for it is part of the core MW software)?

3) All tables are InnoDB except a few, which are MyISAM.

4) In last seven years of my site's running I have NEVER optimized tables because I always try to do so via phpMyAdmin and it says tables are not optimizable. That could be the reasons behind this mess. I will try to optimize tables from command line now. And will get back to you with the results.

5) I don't know if PHP has PECL extension. Will ask the host about it.

6) By opcode cache, do you meaning setting MW to use FileCache?

Thanks once again for your great support. I just hope optimization of tables work and make MW performance better. Lalit Kumar (talk) 10:08, 29 May 2013 (UTC)

Hi Lalit,

1) So MySQL is generally slow. There are plenty of different things you might want to check in order to make MySQL faster. There are a few tuning scripts around, e.g. "MySQLTuner.pl" or "Tuning-Primer.sh". They might give you first ideas of what to change. Note, however, that not everything, what these scripts propose, _must_ make sense in your case. For example adjusting "innodb_buffer_pool_size" might make sense. E.g. increase it to 80% of the memory of your dedicated host.

2) If a few single queries were slow, I would have run these queries with EXPLAIN <your query here>. MySQL will then return its query plan, which will show you, how MySQL would execute the query. That will show you, if indeces are used (and if so: which ones), or if a complete table scan would be done. That would show you where you can optimize the query or the DB. (And these optimizations then would also make sense to be integrated in the MediaWiki core software). However, I think their database layout and queries are quite fine. ;-)

3) InnoDB for most tables is good. Which ones are not InnoDB?

4) Maybe MySQL optimizes tables by itself from time to time, e.g. every week or when it crashed, but I am not sure about that. In a time when your server is not used much (e.g. in the night) you should make a DB backup with mysqldump --opt .... This will make sure that your tables are optimized afterwards and you will get a backup of your DB (just in case)...

6) MediaWiki's fil cache would render Wiki pages to HTML files. You could try that; see, if it helps. What I mean is a PHP accelerator. There are several around like APC or XCache. 88.130.120.224 12:36, 29 May 2013 (UTC)

Thanks for your continued support buddy!

1) While I was getting ready to use OPTIMIZE TABLE on database tables, I put MW in ReadOnly mode. And I noticed a thing. When I put database in ReadOnly mode -performance of my website increases many times.

2) When I used this command "OPTIMIZE TABLE page" ; I got the following results:

+-----------------+----------+----------+-------------------------------------------------------------------+
| Table           | Op       | Msg_type | Msg_text                                                          |
+-----------------+----------+----------+-------------------------------------------------------------------+
| db.page | optimize | note     | Table does not support optimize, doing recreate + analyze instead |
| db.page | optimize | status   | OK                                                                |
:+-----------------+----------+----------+-------------------------------------------------------------------+
2 rows in set (10.48 sec)

I get the same result in case of all the tables in database.

3) I asked my host to take backup of database using --opt option. But I guess they simple used cPanel to take backup. Could you please tell me the full command to take backup with --opt option?

4) Also, could you please explain what exactly this --opt option does? Does the use of this option optimizes database automatically?

5) I will request my host to install APC.

Thank you. With your help, I have already discovered that ReadOnly mode can increase performance. I am feeling that I am nearing the solution I need for this problem that has been nagging me for more than two years!

Lalit Lalit Kumar (talk) 16:45, 29 May 2013 (UTC)

1) So MySQL is in fact not generally slow, but slow when it writes to the database.

2) Looks good.

3) On the shell you can e.g. do shell> mysqldump --opt -u <username> -p<password> db_name > backup-file.sql with your username and your password (and really without space after the "-p"). Use of --opt is the same as specifying --add-drop-table, --add-locks, --create-options, --disable-keys, --extended-insert, --lock-tables, --quick, and --set-charset. All of the options that --opt stands for also are on by default because --opt is on by default.

4) All the different options are explained here: http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html

5) Should not hurt. But when you say that MySQL is slow, when someone writes to the DB, then a PHP accelerator won't change the main part of that problem. 88.130.120.224 18:26, 29 May 2013 (UTC)

Hi pal,

1) I am a bit confused. I wonder why you said "Looks good" on point no. 2 in my previous message? The output of "OPTIMIZE TABLE page" command says:

"Table does not support optimize, doing recreate + analyze instead"

Did the "OPTIMIZE TABLE page" command gave expected output? If the above is expected and output of success of command, should I go ahead and use the "OPTIMIZE TABLE" command on all the tables in database?

2) Thanks a ton for the mysqldump --opt command. I have a question about this command. I want to understand what exactly this command does:

i) does it apply all the said options (like --add-drop-table, --add-locks etc.) only on backup? OR

ii) does it apply all the said options first on the live database and then takes a backup?

iii) can application of all these options (like --add-drop-table, --add-locks etc.) on live database be helpful in solving the "slow while writing" problem?

3) Could you please share any other database maintenance stuff that you regularly do with your MW database? There are a few scripts in MW (like rebuildall) -do you run these scripts regularly?

Thank you! Lalit Kumar (talk) 05:11, 30 May 2013 (UTC)

Hi Lalit,

1) What output you get from OPTIMIZE ... depends on your table engine. For InnoDB it is normal that the table will be recreated. The command ran successfully.

2) That depends: Some only make sense in the backup file (like the DROP TABLE IF EXISTS command). But as far as I know, it applies optimization to the DB itself. Optimizing tables can help to defragment the table data and in so far make the DB a bit faster. But it surely will not make it 5 or even 10 seconds faster when writing things. So: No, this alone will not solve your writing slowness.

3) There are a few tuning scripts in the internet, e.g. called "MySQLTuner.pl" or "Tuning-Primer.sh". They might give you first ideas of what to change. Note, however, that not everything, what these scripts propose, _must_ make sense in your case. For example adjusting "innodb_buffer_pool_size" might make sense. E.g. increase it to 80% of the memory of your dedicated host. 88.130.67.109 12:03, 30 May 2013 (UTC)

Hi pal,

1) I have run OPTIMIZE TABLE command on all the tables present in MW database.

2) Also, I have increased "innodb_buffer_pool_size" from 16M to 500M. I have only 1800M physical memory available on my server. Do you think I can give even more memory to mysql considering that Apache also needs a lot of memory?

(Just to give you an idea of load on apache, my website gets about 70 simultaneous active users in peak time according to Google Analytics. And it serves about 50 pages per minute)

3) My MW database is 3200M large. I researched a bit on net and found that according to some calculations, in case of such a large database innodb_buffer_pool_size should be set to around 5000M ... that means I should have about 6000M memory to run both mysql and apache. In comparison, the present amount of memory is merely 1800M... so, apprently, it is lack of memory that is causing website to go down every half an hour. Lalit Kumar (talk) 13:53, 31 May 2013 (UTC)

Hi Lalit,

1) that's good.

2) I read instructions saying that you can set innodb_buffer_pool_size to 70-75% of the available RAM. The value of innodb_buffer_pool_size is definitely high enough, when the complete database (size of the database) fits into it. For example I have a machine on which I have 8GB RAM, so I could use about 6GB for innodb_buffer_pool_size. However, the DB on the machine is 1,3GB, so I actually set it to 2GB.

3) For you that means that seeing your DB you should set innodb_buffer_pool_size to more than 3,2GB. But 80% of your RAM are only 1,4GB (and you still have to take away the memory needed for Apache, if it's running on the same machine). If innodb_buffer_pool_size is too small (like it was way too small), it will cause swapping and poor performance. I think this gap is at least a big part of your problem.

3) Maybe you can try with 1GB and see if more is possible, depending on how much RAM is needed for other programs. However, I have not tested that. Might also be, that for what reason ever, performance might be worse after that (although I do not expect that). Apart from that more RAM would be better. Would always be better. ;-) 88.130.80.171 14:59, 31 May 2013 (UTC)

Hi pal,

Tweaking mysql config and giving innodb buffer pool more memory seemed to have done the trick. The site worked fairly good for a couple of days. But again, with no apparent reason, suddenly the website came back to its usual behaviour and now again it gets stuck after every 20 minutes or so.

Apache status shows that there are lots of "Sending reply" connections with code "W"... and eventually apache chokes and dies. I am using very plain Monobook Skin with minimum number of extensions (all extensions are common ones and stable). index.php is the culprit when I see the apache status. Most of the connections with "W" are stuck with index.php

But I wonder, why not all the MW websites get choked if there is something wrong with MW code? We all use the same code downloaded from MW website.

Anymore suggestions that you can spare in my quest to find a solution?

PS: I am upgrading my server and getting an extra GB of RAM Lalit Kumar (talk) 15:18, 3 June 2013 (UTC)

You should monitor the available free memory. Maybe the memory usage is increasing until it reaches a limit, when the server dies. Ciencia Al Poder (talk) 09:21, 4 June 2013 (UTC)

Hi Cecina,

Thanks for the reply. I will monitor the available free memory. However, the question remains, what could be causing index.php not to release connection. If connection will not be released; eventually, all the memory space will anyway choke. Lalit Kumar (talk) 13:54, 4 June 2013 (UTC)

Hi!

You say that the server was working for 4 days now. Not ideal yet, but definitely getting better. What about a cron job to restart apache once in the night? Not a solution, but a workaround until you found a solution.

Have you checked these tuning scripts, "MySQLTuner.pl" or "Tuning-Primer.sh"? They do not change anything on your server, they only read the server statistics and based on that make some proposals on what you might want to change. 88.130.98.228 12:50, 4 June 2013 (UTC)

Hi pal,

Yes, server is performing better now but it slows down to almost halt (and sometimes it actually halts) every half an hour or so. The lull remains for about 15-20 minutes. Then it picks speed and rises to the peak. This cycle goes on and on and on!

I have been thinking of using a cron to restart server. May be I should kill all apache processes every 30 minutes and restart apache as well as mysql. This could be a workaround.

Thanks for all your suggestions! Lalit Kumar (talk) 13:59, 4 June 2013 (UTC)

Hi,

why don't you try the tuning scripts? Do you not like them? 88.130.98.228 14:10, 4 June 2013 (UTC)

hey lalit,

this may not be related -- how are the job queue jobs running on your site?

i have a test environment setup using, 1.22alpha and noticed that the site was slow at times with just development work. what helped was setting the job queue rate to 0 in LocalSettings.php and running the maintenance/runJobs.php as a cronjob.

$wgJobRunRate is originally set in /core/includes/DefaultSettings.php with $wgJobRunRate = 1; in LocalSettings.php i have set it set as $wgJobRunRate = 0.

here is the manual for the job queue https://www.mediawiki.org/wiki/Manual:Job_queue. Dan-nl (talk) 15:00, 31 May 2013 (UTC)

Thanks for the suggestion Dan! But job queue does not seem to be the problem because there is very little writing to DB in my website. If fact, the website goes down even if I put it in read only mode! Lalit Kumar (talk) 15:19, 3 June 2013 (UTC)

data tables

Hello there,

I'm a new at mediawiki and I just started a few days ago my new wiki. I'd like to know how to create a table/box data. For instance, when you are creating a new page, called USA, you want a data table on top-right where to put basic details followed by one picture. I'd like to know how to do that with wiki syntax.

I've been reading about extensions, templates but there's no way I can do this

Hope you guys can help me out. Appreciate that. Victorius~mediawikiwiki (talk) 13:04, 28 May 2013 (UTC)

Those tables are created using Wiki Syntax, specially tables (see Help:Tables).

Instead of putting the code for that table on every page, you should normally put that on a template (see Help:Templates) and include that template on your pages, filling the necessary template parameters with the information that varies from page to page.

You can see Wikipedia templates for an example, although wikipedia ones are overkill, so you may want to check other wikis for simpler ones first ;) Ciencia Al Poder (talk) 09:37, 29 May 2013 (UTC)

403-Fehler beim Ausführen von importDump.php

Ich möchte in mein frisch installiertes Wiki einen xml-Dump des von mir geleiteten Wikia-Wikis importieren. Ich erhalte aber, wenn ich die importDump.php im Maintenance-Ordner ausführen will, einen 403-Fehler. Die Rechte für diese Datei stehen auf 777. Wieso kann ich diese KOmmandozeilendatei nicht ausführen? (PHP safe mode habe ich testweise deaktiviert) 91.186.158.136 (talk) 15:01, 28 May 2013 (UTC)

Wahrscheinlich, weil du sie nicht von der Kommandozeile ausführst?! 88.130.97.188 17:40, 28 May 2013 (UTC)

Welche KOmmandozeile? ich habe nur die möglichkeit, die Datei anzuklicken, nicht die Möglihckeit, irgendwelche Kommandos einzutippen? (außer der KOmmandozeile meines PCs, der aber nicht der Server ist). 91.186.158.136 17:45, 28 May 2013 (UTC)

Sag ich ja: Maintenance Scripte musst du von der Kommandozeile ausführen. Der des Servers, nicht deines PCs. 88.130.97.188 19:05, 28 May 2013 (UTC)

Und wo finde ich die Kommandozeile des Servers im Parallels Confixx? Ich habe alles abgesucht, aber keine Möglihkeit für KOmmandozeilen-KOmmandos gefunden. (Shared Hosting -> Kein Roootzugriff) 91.186.158.136 10:56, 29 May 2013 (UTC)

Ob du die in Parallels Confixx findest, musst du schauen. Vielleicht findest du die da gar nicht. Rootzugriff brauchst du nicht. Die Option, die du suchst könnte auch irgendwas mit "SSH" heißen. Wobei es bei Shared Hosting oft noch so ist, dass man keinen SSH-Zugang bekommt. 88.130.120.224 12:03, 29 May 2013 (UTC)

Wobei es bei Shared Hosting oft noch so ist, dass man keinen SSH-Zugang bekommt.

Dann kann ich das WIki ja gleich wieder runterschmeißen... Schon seltsam, dass man für einen DB-Import in MediaWiki Root-Zugriff bzw. Zugriff auf die KOmmandozeile braucht, und in einer Forensoftware eine DAtenbank mit wenigen Mausklicks direkt über die Administrationsoberfläche importieren und gleich ins richtige Format konvertieren kann... Waren da die Entwickler von Mediawiki faul? xD 91.186.158.136 20:03, 29 May 2013 (UTC)

Weder braucht man Root-Zugriff - das hatte ich ja schon gesagt. Noch Zugriff auf die Kommandozeile. Nur dann, wenn man ein Kommandozeilenscript benutzen will, braucht man die Kommandozeile. Sonst nicht. 88.130.120.224 20:34, 29 May 2013 (UTC)

Wie ist es denn ohne Root - und ohne KOmmandozeile möglich, eine xml-Datei zu importeiren? 188.118.242.174 14:34, 5 June 2013 (UTC)

 17:45, 28 May 2013 (UTC)

Extension:CentralAuth

hi can I create a MySQL databse for it by finding a free MySQL host and just use that databse for all your wikis 31.55.3.56 (talk) 16:59, 28 May 2013 (UTC)

I don't understand your question. Could you rephrase it? ☠MarkAHershberger☢(talk)☣ 15:31, 1 June 2013 (UTC)

what I mean is if I create one MySQL database which is used by my website using mediawiki will that woek or would I have to create 2 databases one for website and one for centralauth 109.157.103.6 13:33, 2 June 2013 (UTC)

You should be able to use the same database. How many wikis do you have that you want to organize with CentralAuth? ☠MarkAHershberger☢(talk)☣ 17:51, 2 June 2013 (UTC)

Well I currently have 10 + 176.26.166.20 16:52, 3 June 2013 (UTC)

Kurze URLs funktionieren nicht

Ich habe nun im kürzlich installierten MediaWiki versucht, die Kurzen URLs, also domain/wiki/Seitenname mithilfe von http://shorturls.redwerks.org/?fcgi_pass=127.0.0.1%3A9000&source=userdata&script=%2Fmariowiki%2Findex.php&articlepath=%2Fmariowiki%2Fwiki%2F%241&hashed_uploads=1&thumb_handler=1&url=http%3A%2F%2Fmario-forum.net%2Fmariowiki%2Findex.php%3Ftitle%3DHauptseite&server=apache&rdns_canon=116.hosttech.eu&rdns_addr=82.220.37.11&rdns_origin=mario-forum.net&submit_has_root_no=I+don%27t+have+root+access. einzurichten. Dazu habe ich wie angegeben die .htacces erstellt und hochgeladen und die entsprechenden stellen der LocalSettings.php ersetzt. Diese sieht zurzeit so aus:

<?php
# This file was automatically generated by the MediaWiki 1.20.5
# installer. If you make manual changes, please keep track in case you
# need to recreate them later.
#
# See includes/DefaultSettings.php for all configurable settings
# and their default values, but don't forget to make changes in _this_
# file, not there.
#
# Further documentation for configuration settings may be found at:
# http://www.mediawiki.org/wiki/Manual:Configuration_settings

# Protect against web entry
if ( !defined( 'MEDIAWIKI' ) ) {
	exit;
}

## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;

$wgSitename      = "MarioWiki";

## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs please see:
## http://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath = "/mariowiki";
$wgScriptExtension = ".php";
$wgArticlePath = "{$wgScriptPath}/wiki/$1";
$wgUsePathInfo = true;

## The protocol and server name to use in fully-qualified URLs
$wgServer           = "http://mario-forum.net";

## The relative URL path to the skins directory
$wgStylePath        = "$wgScriptPath/skins";

## The relative URL path to the logo.  Make sure you change this from the default,
## or else you'll overwrite your logo when you upgrade!
$wgLogo             = "$wgStylePath/common/images/mariowikilogo.png";

## UPO means: this is also a user preference option

$wgEnableEmail      = true;
$wgEnableUserEmail  = true; # UPO

$wgEmergencyContact = "administration@mario-forum.net";
$wgPasswordSender   = "administration@mario-forum.net";

$wgEnotifUserTalk      = true; # UPO
$wgEnotifWatchlist     = true; # UPO
$wgEmailAuthentication = true;

## Database settings
$wgDBtype           = "mysql";
$wgDBserver         = "localhost";
$wgDBname           = "usr_xxx";
$wgDBuser           = "xxx";
$wgDBpassword       = "123";

# MySQL specific settings
$wgDBprefix         = "";

# MySQL table options to use during installation or update
$wgDBTableOptions   = "ENGINE=InnoDB, DEFAULT CHARSET=binary";

# Experimental charset support for MySQL 5.0.
$wgDBmysql5 = false;

## Shared memory settings
$wgMainCacheType    = CACHE_NONE;
$wgMemCachedServers = array();

## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads  = true;
$wgGenerateThumbnailOnParse = false;

# InstantCommons allows wiki to use images from http://commons.wikimedia.org
$wgUseInstantCommons  = true;

## If you use ImageMagick (or any other shell command) on a
## Linux server, this will need to be set to the name of an
## available UTF-8 locale
$wgShellLocale = "en_US.utf8";

## If you want to use image uploads under safe mode,
## create the directories images/archive, images/thumb and
## images/temp, and make them all writable. Then uncomment
## this, if it's not already uncommented:
#$wgHashedUploadDirectory = false;

## Set $wgCacheDirectory to a writable directory on the web server
## to make your wiki go slightly faster. The directory should not
## be publically accessible from the web.
#$wgCacheDirectory = "$IP/cache";

# Site language code, should be one of the list in ./languages/Names.php
$wgLanguageCode = "de";

$wgSecretKey = "8077b17860097aab8681adeeb81260a35e6ef34b5433626e0eb2a53aada4f465";

# Site upgrade key. Must be set to a string (default provided) to turn on the
# web installer while LocalSettings.php is in place
$wgUpgradeKey = "92ee51a754548383";

## Default skin: you can change the default skin. Use the internal symbolic
## names, ie 'standard', 'nostalgia', 'cologneblue', 'monobook', 'vector':
$wgDefaultSkin = "vector";

## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsUrl  = "http://creativecommons.org/licenses/by-nc-sa/3.0/";
$wgRightsText = "Creative Commons „Namensnennung, nicht kommerziell, Weitergabe unter gleichen Bedingungen“";
$wgRightsIcon = "{$wgStylePath}/common/images/cc-by-nc-sa.png";

# Path to the GNU diff3 utility. Used for conflict resolution.
$wgDiff3 = "/usr/bin/diff3";

# Query string length limit for ResourceLoader. You should only set this if
# your web server has a query string length limit (then set it to that limit),
# or if you have suhosin.get.max_value_length set in php.ini (then set it to
# that value)
$wgResourceLoaderMaxQueryLength = 512;


# Enabled Extensions. Most extensions are enabled by including the base extension file here
# but check specific extension documentation for more details
# The following extensions were automatically enabled:
require_once( "$IP/extensions/ConfirmEdit/ConfirmEdit.php" );
require_once( "$IP/extensions/Gadgets/Gadgets.php" );
require_once( "$IP/extensions/Nuke/Nuke.php" );
require_once( "$IP/extensions/ParserFunctions/ParserFunctions.php" );
require_once( "$IP/extensions/Renameuser/Renameuser.php" );
require_once( "$IP/extensions/Vector/Vector.php" );
require_once( "$IP/extensions/WikiEditor/WikiEditor.php" );


# End of automatically generated settings.
# Add more configuration options below.

Die neue htacces verursacht aber einen 403er beim Aufruf des Wikis!! Vorher hatte ich sie irrtümlihc als ".htacces" benannt, da merkte man gar nichts von kurzen URLs. Als ich sie dann in .htaccessumbenannte, bekam ich plötzlich 403er; also habe ich sie wieder gelöscht, jetzt werde ich aber, wenn ich das Wiki aufrufe, auf eine 404-Fehlerseite geleitet, mit der URL http://mario-forum.net/mariowiki/wiki/Hauptseite. (Diese domain ist noch vorläufig, wenn das Wiki erstmal richtig funktioniert, werde ich mir eine eigene dafür registireren lassen). Was stimmt da nicht? Wieso werde ich jetzt plötzlich auf eine nicht existierende Seit weitergelitet, und nichtmehr auf die Hauptseite des Wikis? Und wie bekomme ich das zusätzliche /wiki/ weg? 91.186.158.136 (talk) 18:16, 28 May 2013 (UTC)

Probier es am Besten mal mit dieser Anleitung: Short URLs.

PS: Interessantes MySQL Passwort. ;-) 88.130.97.188 19:06, 28 May 2013 (UTC)

Das MySQL-Passwort stimmt natürlich nicht ;) Ich würde aber trotzdem gerne den Nutzernamen aus dem Beitrag entfernen, allerindgs funktioniert das Editieren in diesem seltsamen "FOrum" nicht. Wenn ich auf "Speichern" klicke, erscheint die LAdeanzeige, aber es egeht nix weiter.

In der genannten Anleitung finde ich leider, ußer der bereits probierten Möglichkeit, die 403er versucht, keine Möglichkeit für kurze URLs ohne Root-Zugriff. 91.186.158.136 11:07, 29 May 2013 (UTC)

Ich hab Nutzernamen und Passwort gerade entfernt. 88.130.120.224 12:01, 29 May 2013 (UTC)

[RESOLVED] Upload warning: Could not create directory

Hi there,

I get this warning trying to upload a PNG file.

- Upload warning - Could not create directory "mwstore://local-backend/local-public/3/3d".

I'm under a web hosting service. Hope you guys can help me out. Victorius~mediawikiwiki (talk) 21:32, 28 May 2013 (UTC)

lol me, I just couldn't edit file's attributes be cause I was not connect to the server. Lol me. Victorius (talk) 21:38, 28 May 2013 (UTC)

I'm assuming the issue is now solved. Marking as such. Ciencia Al Poder (talk) 09:30, 29 May 2013 (UTC)

Vector Sidebar

There are closable and openable section in the Sidebar. Is it possible to have this always open? 2003:5F:2707:7401:7134:A390:DAA9:8C89 (talk) 05:15, 29 May 2013 (UTC)

If you have the Vector extension installed, remove it. This should keep all side bar sections open. Arcane21 (talk) 06:57, 29 May 2013 (UTC)

Mmh, I was looking for another way. This is the feature of the extension:

$wgVectorFeatures['collapsiblenav']['global'] = false; 2003:5F:2707:7401:5430:BB23:1428:A9CD 17:28, 29 May 2013 (UTC)

Configuring Open AM with Mediawiki

Hello,

Versions Mediawiki- mediawiki-1.20.5 PHP - php-5.3.20-nts-Win32-VC9-x86 OpenAM - Philip Pedersens vei 1, 1366 Lysaker, Norway (Is this the same , I am not sure about this)

I have downloaded the extension (php_http.dll) and deployed in PHP framework. And added OpenAM.PHP and modified localsettings.php as suggested in the link http://www.mediawiki.org/wiki/Extension:OpenAM.

I am using SAML standard, and I am having one application developed in Asp.net MVC which I have configured with OpenAM using SAML standard and working fine. While configuring this I have included some XML files (sp.xml, sp-extended.xml, fedlet.cot, idp-extended.xml and idp.xml).

But in mediakwiki there nowhere mentioned about these files to configure, I am bit confused about this.

In localsettings I have given as bellow

1. OpenAM
2. More info: http://www.mediawiki.org/wiki/Extension:OpenAM

require_once( "$IP/extensions/OpenAM/OpenAM.php" ); // You MUST set the distAuth URL $wgAuth->setDistAuthUrl( 'http://lms.XXXXXXX.com:9090/openam/SSORedirect/metaAlias/idp/' ); // You MUST set the identity URL $wgAuth->setIdentityUrl( 'http://lms.XXXXXXX.com:9090/openam/' ); // Set this to the OpenSSO profile attribute that holds users' MediaWiki names $wgAuth->setUid( 'uid' ); // You will only need to change the cookie name if you have changed it on the OpenSSO server (recommended) $wgAuth->setCookie( 'iPlanetDirectoryPro' ); // new $wgAuth->setLdapGroups( 'ldap-groups' );

Can you please check this once.

And for service provider creation we need to give sp.xml for fedlet creation, I don’t know how to configure this for mediawiki.

Regards, Harinath Harinath1929 (talk) 09:18, 29 May 2013 (UTC)

TOC in left menu outside the artice area

Hello,

I want to display the TOC outside of the article itself, on left menu side. I tried to work thought the API, but all the methods did generate empty results. Maybe someone could guess a parameter it is missing?

// https://doc.wikimedia.org/mediawiki-core/master/php/html/classParserOutput.html#a7ed0b2a21f9eed4adce4aa7457f45b5f ParserOutput::getTOCHTML();

// https://doc.wikimedia.org/mediawiki-core/master/php/html/classParserOutput.html#a7fd87771bccecca0a63b146b01462748 //global $mTOCHTML; $mTOCHTML; //

ParserOutput::getSections(); // this results to empty return count(ParserOutput::getSections()); // returns 0

// https://doc.wikimedia.org/mediawiki-core/master/php/html/classLinker.html#ad5c07fe25c9b0840ee14a5f25c8175be // static Linker::generateTOC ( $ tree ) [static] Linker::generateTOC(ParserOutput::getSections()); // this generates an empty TOC

// https://doc.wikimedia.org/mediawiki-core/master/php/html/classLinker.html#a50be88a27322e8afc9479f2575460eb9 // static Linker::tocList ( $ toc,$ lang = false ) Linker::tocList("Test Entry"); // this generates a TOC with entry "Test Entry"

Greetings Oliver 85.180.159.159 (talk) 10:34, 29 May 2013 (UTC)

Issue with lua & scribuntu causing some pages to give massive error

I recently imported a few templates from wikipedia and the templates added some code to my infoboxes. With that addition, my wiki would just show the code on the page. {{#invoke:InfoboxImage|InfoboxImage|image=|size=|sizedefault=frameless|alt=|suppressplaceholder=yes}} the above was added to my infobox person page and it shows on the infoboxes now.

so I did a little research and found that I need to install an extension called scribuntu. in doin that, any page with that above code returns a long error

Lua error: Internal error: Error reading from pipe.

Backtrace:

1. 0 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php(368): ScribuntoEngineBase->newException('scribunto-luast...')
2. 1 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php(330): Scribunto_LuaStandaloneInterpreter->receiveMessage()
3. 2 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php(256): Scribunto_LuaStandaloneInterpreter->dispatch(Array)
4. 3 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaCommon/LuaCommon.php(115): Scribunto_LuaStandaloneInterpreter->registerLibrary('mw_interface', Array)
5. 4 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaCommon/LuaCommon.php(90): Scribunto_LuaEngine->registerInterface('mw.lua', Array, Array)
6. 5 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php(8): Scribunto_LuaEngine->load()
7. 6 /home/worldafr/public_html/wiki/extensions/Scribunto/engines/LuaStandalone/LuaStandaloneEngine.php(26): Scribunto_LuaStandaloneEngine->load()
8. 7 /home/worldafr/public_html/wiki/extensions/Scribunto/common/Hooks.php(185): Scribunto_LuaStandaloneEngine->getLimitReport()
9. 8 [internal function]: ScribuntoHooks::reportLimits(Object(Parser), 'NewPP limit rep...')
10. 9 /home/worldafr/public_html/wiki/includes/Hooks.php(216): call_user_func_array('ScribuntoHooks:...', Array)
11. 10 /home/worldafr/public_html/wiki/includes/GlobalFunctions.php(3823): Hooks::run('ParserLimitRepo...', Array)
12. 11 /home/worldafr/public_html/wiki/includes/parser/Parser.php(492): wfRunHooks('ParserLimitRepo...', Array)
13. 12 /home/worldafr/public_html/wiki/includes/WikiPage.php(3110): Parser->parse('{{Infobox dam?|...', Object(Title), Object(ParserOptions), true, true, 33592)
14. 13 /home/worldafr/public_html/wiki/includes/PoolCounter.php(209): PoolWorkArticleView->doWork()
15. 14 /home/worldafr/public_html/wiki/includes/Article.php(631): PoolCounterWork->execute()
16. 15 /home/worldafr/public_html/wiki/includes/actions/ViewAction.php(37): Article->view()
17. 16 /home/worldafr/public_html/wiki/includes/Wiki.php(427): ViewAction->show()
18. 17 /home/worldafr/public_html/wiki/includes/Wiki.php(304): MediaWiki->performAction(Object(Article))
19. 18 /home/worldafr/public_html/wiki/includes/Wiki.php(536): MediaWiki->performRequest()
20. 19 /home/worldafr/public_html/wiki/includes/Wiki.php(446): MediaWiki->main()
21. 20 /home/worldafr/public_html/wiki/index.php(59): MediaWiki->run()
22. 21 {main} Vapblack (talk) 10:51, 29 May 2013 (UTC)

Asking in http://www.mediawiki.org/wiki/Extension_talk:Scribunto might be a better place. AKlapper (WMF) (talk) 10:45, 30 May 2013 (UTC)

URL with «:» are not dispayed correctly

Good day.

I have copy of wiki on WAMP Win7 on my local PC.

After update from 1.16 to 1.21 I have issue. URL with colon sign are not displaed correctly.

Example: http://wiki.test.old/Служебная:Спецстраницы

Server responce: Forbidden You don't have permission to access /Служебная:Спецстраницы on this server.

Apach error log: [Wed May 29 15:38:40 2013] [error] [client 127.0.0.1] (20024)The given path is misformatted or contained invalid characters: Cannot map GET /%D0%A1%D0%BB%D1%83%D0%B6%D0%B5%D0%B1%D0%BD%D0%B0%D1%8F:%D0%A1%D0%BF%D0%B5%D1%86%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D1%8B HTTP/1.1 to file

Pages without «:» are OK.

Pls, advice what is the problem. Ektip (talk) 11:41, 29 May 2013 (UTC)

Are you running MediaWiki on IIS? If yes see if this helps: Ciencia Al Poder (talk) 09:18, 30 May 2013 (UTC)

No, I am using Apach and PHP+MySQL on Wamp server. OS is Win7 x64 Russian Edition Ektip (talk) 08:14, 6 June 2013 (UTC)

It's a problem with Apache on Windows: .

The thing is, MediaWiki on XAMPP seems to run without this issue, maybe they patched Apache to not have this problem. Maybe you should use XAMPP or IIS. Ciencia Al Poder (talk) 09:42, 6 June 2013 (UTC)

I have tried XAMPP as well. There is another error happened regarding Cyrillic symbols in filenames.

I think it is better to use Linux virtual machine to avoid such behaviour Ektip (talk) 12:02, 6 June 2013 (UTC)

Installation 1.21 - Fatal exception of type MWException

I got clear installation of MW 1.21 and get error when launching wiki «Fatal exception of type MWException».

What is the issue. Pls, advice. Ektip (talk) 12:21, 29 May 2013 (UTC)

Enable error display and see again. Set this in LocalSettings.php:

$wgShowSQLErrors = true;

$wgDebugDumpSql = true;

$wgShowDBErrorBacktrace = true;

More information are on page Manual:Errors_and_symptoms. 88.130.120.224 12:39, 29 May 2013 (UTC)

[RESOLVED] MediaWiki 1.5 to 1.21 upgrade

I have a MediaWiki 1.5 server that is broken, a lot of the features dont work - i think something got broken when it was migrated from a windows machine to a linux machine.

I need to move the whole thing from the current machine to a new one - whats the best way? I have built a new mediawiki install using 1.21 and then copied the DB over but the update.php fails.

any suggestions? 194.75.58.98 (talk) 12:51, 29 May 2013 (UTC)

I would tar the whole wiki directory (or use zip or which utility you have on the Windows machine), copy it to the new server (maybe with wget) and extract it there.

Then I would create a database dump (e.g. with mysqldump) and import that dump on the new server with "mysql". 88.130.120.224 12:56, 29 May 2013 (UTC)

i can access it via PSFTP and Putty (its a linux Box atm going to another linux box)

i also have phpmyadmin installed on both.

so remove the 1.21 mediawiki and just clone over the wiki again 194.75.58.98 13:01, 29 May 2013 (UTC)

If your old wiki continues to work properly on the new server depends: What PHP and MySQL versions does MediaWiki 1.5 support? And what versions do you have on the newest server?

Basically I would first copy it to the new server and then do an update just as usual. Upgrading instructions are available here Manual:Upgrade. 88.130.120.224 13:46, 29 May 2013 (UTC)

How does update.php fail? What error do you see? You should definitely upgrade to 1.21 or 1.19 (the LTS) because otherwise you're going to run into problems with newer versions of PHP. ☠MarkAHershberger☢(talk)☣ 15:27, 1 June 2013 (UTC)

i have all the newest versions on the new server (debian squeeze)

installed using these commands:

aptitude install apache2 php5 libapache2-mod-php5 php5-imap

aptitude install mysql-server mysql-client php5-mysql

aptitude install phpmyadmin

followed manual 1.21 install procedure

current version of mediawiki (working) is from here (OpenVZ appliance) - http://pve.proxmox.com/wiki/MediaWiki

(Debian Squeeze, MediaWiki 1.15, MySQL5.1, Postfix, Apache2, PHP5.3)

tried copying over the whole folder and DB - get a forbidden error on the new server

on the old server the mediawiki folder is in the /var/lib folder but when installing the 1.21 version the folder goes in /var/www?

any advice? 194.75.58.98 15:37, 3 June 2013 (UTC)

> followed manual 1.21 install procedure

> current version of mediawiki (working) is from here (OpenVZ appliance) MediaWiki 1.15

You should not use MediaWiki 1.15; it is outdated, contains known security vulnerabilities and is no longer supported. MediaWiki 1.21 is better.

Make sure that you first install the old version and then update it with the new version. 88.130.98.228 17:57, 3 June 2013 (UTC)

thats why i am trying to upgrade :)

should i install with aptitude install mediwiki and then upgrade that? 194.75.58.98 11:09, 4 June 2013 (UTC)

> thats why i am trying to upgrade :)

Cool. :-)

> should i install with aptitude install mediwiki and then upgrade that?

I am not really a Linux guy. You surely need Apachae, PHP and MySQL. ;-) If you mean if you should install MediaWiki that way: I would not. In the past these packages were often broken.

I would copy the old code and database to the place, where you now need it (on the _new_ server). After that just follow Manual:Upgrading and do an upgrade "as usual" - as your situation _is_ usual. 88.130.98.228 12:41, 4 June 2013 (UTC)

Ive redone it all again - reinstalled debian, installed apache/php5/mySQL/phpmyadmin, copied the mediawiki folder from the original server (tar) and extracted it into /lib/www/mediawiki on the new server, also copied the DB to the new server and created the wikiuser account with all rights to the DB.

all the files are in the /var/www folder on the new server, there is a symlink on the old box for /var/lib/mediawiki and /var/www/mediawiki (from where it was installed via packages)

i have recreated the alias in /etc/apache2/httpd.conf:

ALIAS /wiki "/var/www/mediawiki/index.php"

i now get a 403 Forbidden error - im guessing this is simply a chmod issue now? but im not sure how to fix it. once i have the 1.15 version working, i will do the upgrade to 1.21! 194.75.58.98 11:54, 5 June 2013 (UTC)

Hi,

I am not sure about that error, but this page has a number of possible reasons and the according solutions:

http://www.cyberciti.biz/faq/apache-403-forbidden-error-and-solution/

Number c) is not relevant for you. 88.130.71.169 13:40, 5 June 2013 (UTC)

I have rebuilt the server again (i tried a 1.21 upgrade but it broke again during the update.php script (forgot to grab the error!) 1.21 installs fine on its own so i assume its a permissions settings with the 1.15 version :S

The 403 errors on anything in the mediawiki or /wiki - apart from the /mediawiki/images folder.

At the moment i just want to get the 1.15 version working - i'll worry about the broken upgrade once ive got it moved servers. 194.75.58.98 15:53, 5 June 2013 (UTC)

Leave everything as is and try installing MediaWiki 1.15 from scratch. An empty new install just like you installed 1.21. When MW1.21 works that way, 1.15 should do as well. Then compare the differences between the working and the broken install. 88.130.71.169 16:06, 5 June 2013 (UTC)

found a part of the issue - looks like when mediawiki whas installed on the debian container it was split across different locations with symlinks combining them, when i tar'ed the mediawiki folder to go to the new one, it only gathered the files from the immediate folder (var/lib/mediawiki) and kept the shortcuts/symlinks (etc/mediawiki & usr/share/mediawiki) instead of combining them into the file - so the main error looks like i've not actaully copied the whole folder over.

i've also noticed that there is a missing adminsettings.php as a symlink file that i cant find on my existing server! (this probably explains some of the missing/broken features...)

2 questions now:

a) how can i create a tar file to create a file that has brought all the symlinks into one file - or am i going to have to do this manually?

b) i) where can i get the 1.15 mediawiki to install

ii) if i install a 1.15 version and then extract my files on top would this replace any missing files? 194.75.58.98 16:28, 5 June 2013 (UTC)

> the main error looks like i've not actaully copied the whole folder over.

Make sure you use no symlinks. Not a single one. Instead, copy over all(!) actual files.

To a): Yes, I think you should do that manually. MediaWiki can run fine without any symlink.

b) Here. No, just joking. Here: http://dumps.wikimedia.org/mediawiki/1.15/

c) Don't do that. It would replace missing files, but only as far as they are actually part of the main package. All other files will 'not be replaced. You won't come araound a manual run. 88.130.97.129 18:15, 5 June 2013 (UTC)

ok - combined the fies (removes symlinks and copies files instead) using:

tar -chf mediawiki.tar mediawiki

got all the files on the server and now allows me view the wiki data, although skins arent working and most of the links arent working either... it seems to be looking in the wrong place:

/var/www/skins - instead of /var/www/mediawiki/skins - what do i need to update here? (LocalSettings.php has correct install path) 194.75.58.98 09:09, 6 June 2013 (UTC)

> got all the files on the server and now allows me view the wiki data,

So your wiki is generally working now. That's already a good start.

> although skins arent working and most of the links arent working either... it seems to be looking in the wrong place:

You obviously have set a fixed path somewhere in LocalSettings.php. Search for something with "skins" or with "www" if that helps. 88.130.122.1 12:36, 6 June 2013 (UTC)

I've not yet geot htis working correctly although i have managed to upgrade the wiki to 1.21 sucessfully:

i had to run the sql command from /maintenance/archives/patch-rev_sha1.sql and rename the StartProfiler.php to StartProfiler.old and the wiki is in the same shape as before...

there is nothing in the LocalSettings.php that indicates that the files are in the wrong place - it seems more like an apache issue or something - the old server automatically redirects from 192.168.100.41 to 192.168.100.41/wiki/Main_page whereas the new install doesnt... 194.75.58.98 12:55, 6 June 2013 (UTC)

You should not run single sql files on their own. Instead, after each update you should run maintenance/update.php. It will take care to apply the right changes as needed - this mechanism might now be broken for you now, as you have manually applied some of the changes (without being sure that you really did everything, what is needed).

To make sure nothing is broken, you should go back to the state from before you ran this sql file and then run update.php instead. 88.130.122.1 15:52, 6 June 2013 (UTC)

Dont panic i ran the update.php afterwards anyway - the error iw as having is here: http://www.mediawiki.org/wiki/Project:Support_desk#upgrade_problems:_1.11_--.3E_1.21_28160

doing this allowed the update.php to run.

part of the issue was that i'd got short URLs configured on the old system and needed to set it up properly

I had the LocalSettings.php configured wrong $wgScryptPath = ""; instead of $wgScryptPath = "/mediawiki";

the other issue was that i was running gumax 4.0.1 on the box and its incompatible with 1.21 - causes an error.

The remaining issue is that i cannot get the server to automatically direct to 192.168.100.47/wiki when i enter 192.168.100.47 into a browser - the original wiki does this with no issues. 194.75.58.98 16:45, 6 June 2013 (UTC)

Yes, I know this behaviour. This can be configured in the Apache config or in .htaccess. E.g. with an .htaccess rule like the following. The rule belongs in an .htaccess file outside of the wiki/ folder.

RewriteRule ^$ wiki/ [L]

(without testing...) 88.130.122.1 17:22, 6 June 2013 (UTC)

i created a .htaccess file in /var/www/

## http://www.mediawiki.org/wiki/Manual:Short_URL/Apache

# Enable the rewrite engine

RewriteEngine On

# Short url for wiki pages

RewriteRule ^/?wiki(/.*)?$ %{DOCUMENT_ROOT}/mediawiki/index.php [L]

# Redirect / to Main Page

RewriteRule ^/*$ %{DOCUMENT_ROOT}/mediawiki/index.php [L]

this sorted it :)

Wiki is now fully updated and running as expected.

Thanks to all who helped. 194.75.58.98 16:30, 12 June 2013 (UTC)

Problem editing a section - section heading gets lost

Hi,

I try to edit a section of a page via api like that:

$api_addlink = new ApiMain(
   new DerivativeRequest(
       $wgRequest,
       array(
           'action'     => 'edit',
           'title'      => 'just a title',
           'section'    => '1',
           'text'       => 'some text',
           'notminor'   => true,
           'token'      => $token
       ),
       false // was posted?
   ),
   true // enable write?
);
$api_addlink->execute();

If I do it that way, the section heading gets lost. I found a Post saying "Yes, the heading is part of the section. So if you don't want to replace (or even delete) it, you will need to send it as a part of the text." here If I send the heading along with the text like "== Heading ==" it doesnt get recognized as a heading. What am I doing wrong?

Versions
MediaWiki: 1.20.3
PHP: 5.3.10
MySQL: 5.1.69 Michael MPI (talk) 15:02, 29 May 2013 (UTC)

Ungraded 1.10 to 1.19 ( and ported to new server ) - mediaWiki does not process etc

We have ported a mediaWiki site from one server to another. And we upgraded in the process from 1.10 to 1.19. Most everything seems to be working except that gets printed from a few of our templates, such as the Template:BackTo customization that worked working on the old server, and the infoBox template. The following is our customized template:BackTo code. The ideas is that if the next page does not exist, nothing is rendered to the browser, but otherwise, one gets an arrow image with the name of next page given as a hyperlink. Something is either wrong with the syntax or the parser. Any help is appreciated.

For example the following throws an error

{{#if:{{{page2|}}}|{{clickpic|{{{page2}}}|http://xxx.xxx.xx.xx/wiki/images/f/f8/Back.gif}}[[{{{page2|}}}|Back to {{{page2|}}}]]|}}

Product Version MediaWiki 1.19.7 PHP 5.3.3 (apache2handler) MySQL 5.1.69 Richiwalt (talk) 19:06, 29 May 2013 (UTC)

Throws an error? Or it just doesn't interpret properly the {{#if: }} syntax?

If it's the latter, you need to enable ParserFunctions. They're now bundled with MediaWiki, but you need to enable them. See Extension:ParserFunctions. Ciencia Al Poder (talk) 09:25, 30 May 2013 (UTC)

IN THIS FORUM IT IS NOT POSSIBLE TO EDIT AS AN IP!

I'm not able to edit my postings as an IP. After clicking the "Save"-Button, it loads and loads and doesn't come to an end. And after reloading, the edit is not saved. Please can you fix the bug? 91.186.158.136 (talk) 20:07, 29 May 2013 (UTC)

IN THIS FORUM IT IS NOT POSSIBLE TO EDIT AS AN IP! 88.130.120.224 20:29, 29 May 2013 (UTC)

Fatal PHP error when running update.php

Hi,

I'm testing an upgrade of a MediaWiki 1.15.1 to 1.21.0 on a locally installed virtual web server. I'm using Apache 2.2.22, PHP 5.3.17, and MySQL 5.5.30. After copying the new files over the old ones I run the maintenance/update.php from the command line. It gets part way through the update process then fails with the following error: ...batch conversion of user_options: PHP Fatal error: Unsupported operand types in /web/wiki/htdocs/languages/Language.php on line 495 Any idea what might be going wrong?

Thanks.

Erik Erikjsci (talk) 22:36, 29 May 2013 (UTC)

Hi Erik,

I just wanted to ask you what code you have in languages/Language.php on line 495, but I think I already know what your problem might be:

When you are on the shell, what PHP version do you have there? You wrote you would have version 5.3.17, but you might have a different (possibly way older) version on the shell. Use php -v to find out... 88.130.120.224 01:03, 30 May 2013 (UTC)

php -v also results in PHP 5.3.17. If it helps I can add that I'm running an Oracle VM virtual box with OpenSUSE 12.3 "Dartmouth" Kernel 3.7.10-1.1-desktop. Thanks.

Erik Erikjsci (talk) 18:00, 30 May 2013 (UTC)

This bit of code is in the public function getNamespaces()

495 $this->namespaceNames = $wgExtraNamespaces + $this->namespaceNames + $validNamespaces;

It's the fifth line inside the function.

Erik Erikjsci (talk) 18:17, 30 May 2013 (UTC)

So you get an error "unsupported operand types" when using "+" on variables... Maybe they / some of them do not have the type, which was expected (e.g. array vs. string)? 88.130.67.109 22:01, 30 May 2013 (UTC)

Probably so. Any suggestions for troubleshooting the problem?

Erik Erikjsci (talk) 20:47, 3 June 2013 (UTC)

This might indeed be a syntax error. Maybe it works when using array_merge() instead?

PS: Is this here the same error?

https://bugzilla.wikimedia.org/show_bug.cgi?id=36468 88.130.98.228 22:41, 3 June 2013 (UTC)

I changed the line to use array_merge() instead and tried it again. Now it reports a warning and moves on to another error:

...batch conversion of user_options: PHP Warning: array_merge(): Argument #1 is not an array in /web/wiki/htdocs/languages/Language.php on line 495

PHP Notice: Undefined offset: 5 in /web/wiki/htdocs/languages/Language.php on line 501

A database query syntax error has occurred.

The last attempted database query was:

"SELECT rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,page_namespace,page_title,page_id,page_latest,page_is_redirect,page_len,user_name FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) WHERE page_id = '8' AND rev_id = '32' LIMIT 1 "

from within function "Revision::fetchFromConds".

Database returned error "1054: Unknown column 'rev_sha1' in 'field list' (db1)" Erikjsci (talk) 00:02, 28 June 2013 (UTC)

I eventually found the offending bit of code on my own. I had the following directive in my LocalSettings.php:

$wgExtraNamespaces = NULL;

This did not cause a problem in the older version of MediaWiki, but was catastrophic for upgrading! All went well after removing it. Erikj36 (talk) 23:51, 21 August 2013 (UTC)

$wgExtraNamespaces = NULL;

was documented as default for that setting. But that is blatantly wrong! I have just fixed the wrong description. 88.130.97.34 01:21, 22 August 2013 (UTC)

I also had to manually add the missing rev_shaw table to the database with the following command: (note to substitute (prefix)_ with whatever if any table prefix you use.)

ALTER TABLE (prefix)_revision ADD rev_sha1 varbinary(32) NOT NULL default ; Erikj36 (talk) 23:55, 21 August 2013 (UTC)

Moving the sidebar up just under the logo

My Versions: MediaWiki 1.20.5 PHP 5.4.11 (cgi-fcgi) MySQL 5.1.56-log

My URL: http://rasikas.org/wiki/Main_Page

My issue: I have looked everywhere and can't find a way to move the sidebar up so that it shows just under the site logo, rather than way down the page leaving a large gap between the logo and the "navigation". Srkris (talk) 00:08, 30 May 2013 (UTC)

Works for me when I add

.p-navigation {

margin-top: -100px;

}

Another possibility would be to also move the logo a bit down; it somehow stands a bit too high there for my taste. 88.130.120.224 01:14, 30 May 2013 (UTC)

Perfect, thanks. Srkris (talk) 02:46, 30 May 2013 (UTC)

The new issue as a result of your suggestion is that the first 3 links under the "navigation" are not clickable, perhaps there is something else I've failed to do? Srkris 13:08, 30 May 2013 (UTC)

I hadn't checked clicking the links. ;-( You can not click those links, because your image is smaller than the default CSS rules assume; they assume it would all in all need a height of 160px. For #p-logo set the correct height; something around 60px should fit to the layout as you have it right now. 88.130.67.109 13:57, 30 May 2013 (UTC)

Thanks, my common.css already has the #p-logo height set to 60px as follows, which I assume would override the defaults?

1. p-logo a {display: block; height: 60px; width: 10em; margin-bottom: 5px;}
2. p-logo a:hover {display: block; height: 60px; width: 10em; margin-bottom: 5px;}

Can you clarify what else I should do? Thanks again. Srkris (talk) 19:55, 30 May 2013 (UTC)

> Thanks, my common.css already has the #p-logo height set to 60px as follows

No, that does not follow. ;-)

> which I assume would override the defaults?

Yes, it would (if you had set it).

What you have is #p-logo a {height: 60px;}

You are "only" reducing the height of the a-tag inside #p-logo, not the height of #p-logo itself.

What you should add is #p-logo {height: 60px;} 88.130.67.109 21:59, 30 May 2013 (UTC)

Ohh how stupid of me to have not noticed that. Thanks very much. :-) Srkris (talk) 18:29, 31 May 2013 (UTC)

Apache 2.4.4 + php-fpm + php 5.4.15 -- security question

Hello all,

I have a small personal wiki. It is hosted in a Centos 6.3 with Apache 2.4.4 + php-fpm + php 5.4.15. I'm worried about security... (specifically about arbitrary code execution)

I would like to know what security measures i need to use...

This is my Apache configuration

<VirtualHost *:80>
ServerName wiki.mydomain.tld
DocumentRoot /path/to/apache/2.4.4/htdocs/mediawiki
DirectoryIndex index.php
DeflateFilterNote ratio
<IfModule proxy_module>
  ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9002/path/to/apache/2.4.4/htdocs/mediawiki/$1
</IfModule>
</VirtualHost>

Thanks in advance.. -Vijay

PS: I hope this is the right place for this question... Vijayrajah (talk) 06:13, 30 May 2013 (UTC)

What sort of security are you worried about? We regularly release MediaWiki Security updates. If you keep installation on the latest supported version, you should be fine. ☠MarkAHershberger☢(talk)☣ 15:01, 1 June 2013 (UTC)

[RESOLVED] upgrade problems: 1.11 --> 1.21 (batch conversion of user_options: Unknown column 'rev_sha1')

I'm trying to upgrade from MW 1.11 to 1.21.0rc5, using PHP 5.3.13 and MySQL 5.0.96-log. I get the following error during the upgrade:

...batch conversion of user_options: A database query syntax error has occurred. The last attempted database query was: "SELECT rev_id,rev_page,rev_text_id,rev_timestamp,rev_comment,rev_user_text,rev_user,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,page_namespace,page_title,page_id,page_latest,page_is_redirect,page_len,user_name FROM `revision` INNER JOIN `page` ON ((page_id = rev_page)) LEFT JOIN `user` ON ((rev_user != 0) AND (user_id = rev_user)) WHERE page_id = '9' AND rev_id = '3494' LIMIT 1 " from within function "Revision::fetchFromConds". Database returned error "1054: Unknown column 'rev_sha1' in 'field list' (foobar.barfoo.com)"

The wiki in question is at: http://wikihawk.heggen.net

I am kinda stumped, so any help would be appreciated. Twisted86 (talk) 08:13, 30 May 2013 (UTC)

There are quite some results when I search for that error message with a search engine on the internet, e.g. http://www.mediawiki.org/wiki/Project%3ASupport%20desk/Flow/2013/03#h-%5BRESOLVED%5D_Database_error%3A_%221054%3A_Unknown_column_%27rev_sha1%27_in_%27field_list%27_%28loc-2013-03-22T02%3A30%3A00.000Z and https://bugzilla.wikimedia.org/show_bug.cgi?id=34310 AKlapper (WMF) (talk) 10:48, 30 May 2013 (UTC)

It looks like the error is happening running update.php. See also Project:Support desk/Flow/2013/05#h-Fatal_PHP_error_when_running_update.php-2013-05-29T22:36:00.000Z with the same problem.

AKlapper, could it be a issue with 1.21 upgrading from old versions? Ciencia Al Poder (talk) 13:18, 30 May 2013 (UTC)

My thanks to both of your for the replies.

I get the same error when I run upgrade.php from the command line, by the way.... —Twisted86 (talk) 17:59, 30 May 2013 (UTC)

I'm having the same problem. Jason1234h (talk) 19:44, 30 May 2013 (UTC)

Do you see the exact same error when running update.php? ☠MarkAHershberger☢(talk)☣ 01:39, 31 May 2013 (UTC)

Could you share your LocalSettings.php file with the passwords removed? Maybe put it on http://pastebin.com/ or the like?

Since people seem to be running into this problem, I'd like to make sure that I can reproduce it. ☠MarkAHershberger☢(talk)☣ 20:18, 30 May 2013 (UTC)

You bet! Here ya go.

Thanks, —Twisted86 (talk) 20:27, 30 May 2013 (UTC)

I just installed 1.11 and upgraded to 1.21 without a problem.

A couple of ideas:

• Did you get new versions for every extension?
• Try disabling all the extensions and then running the upgrade. ☠MarkAHershberger☢(talk)☣ 01:38, 31 May 2013 (UTC)

Good ideas, Mark.

I commented out all of the extensions, but I still get the same errors with update.php and mw-config.

Would you like for me to try updating all of the extensions, re-enabling them, and then trying the upgrade again, or is that a Bad Idea? —Twisted86 (talk) 03:46, 31 May 2013 (UTC)

It doesn't seem to be a problem of an extension. rev_sha1 field is missing from revision table. It was added on 1.19.

It's failing in the batch conversion of user_options process. We should identify if it's running that before creating the missing field and why it's trying to access to that field.

I'll try to investigate when I go home. Ciencia Al Poder (talk) 09:30, 31 May 2013 (UTC)

Thanks! —Twisted86 (talk) 17:10, 31 May 2013 (UTC)

Right. I asked him to disable the extensions because that is the sort of problem that extensions can cause.

It looks like the extensions weren't causing it, though, so carry on! ☠MarkAHershberger☢(talk)☣ 18:28, 31 May 2013 (UTC)

I think I've identified the bug. See bugzilla:49039

The solution may be upgradin to an intermediate version, and then to latest, but I'm not shure what version would fit for "intermediate". Ciencia Al Poder (talk) 12:52, 1 June 2013 (UTC)

or just add the missing rev_sha1 field manually executing ./maintenance/archives/patch-rev_sha1.sql:

ALTER TABLE /*$wgDBprefix*/revision

ADD rev_sha1 varbinary(32) NOT NULL default ; Ciencia Al Poder (talk) 18:54, 2 June 2013 (UTC)

Do you need to add that as a separate file? 208.89.206.26 20:54, 5 June 2013 (UTC)

No, you need to open a mysql command prompt and execute that statement on the database for the wiki.

Example:

user@host> mysql -u root -p

<type password>

mysql> use wikidb;

Database changed.

mysql> ALTER TABLE /*$wgDBprefix*/revision

> ADD rev_sha1 varbinary(32) NOT NULL default ;

If you're using phpMyAdmin you can also execute if from there. Ciencia Al Poder (talk) 09:35, 6 June 2013 (UTC)

Thank you very much, Ciencia and Mark!

I ran the SQL code above in phpMyAdmin and that solved the problem. Yay! —Twisted86 (talk) 19:22, 6 June 2013 (UTC)

The answer is correct but not complete

it should be

user@host> mysql -u root -p

<type password>

mysql> use wikidb;

Database changed.

mysql> ALTER TABLE /*$wgDBprefix*/revision

ADD rev_sha1 varbinary(32) NOT NULL default ''; <-- two ''

145.50.39.8 12:21, 26 June 2013 (UTC)

[RESOLVED] Cannot upload files with non-latin names. Upload error: This wiki does not support filenames with special characters.

I try to upload files with Cyrillic names but have error Upload error: This wiki does not support filenames with special characters.

What can be the problem? Ektip (talk) 09:19, 30 May 2013 (UTC)

Looks like a sanity check that does MediaWiki because your filesystem doesn't support UTF-8 (unicode) filenames Ciencia Al Poder (talk) 09:36, 31 May 2013 (UTC)

What operating system does your wiki run on? ☠MarkAHershberger☢(talk)☣ 14:57, 1 June 2013 (UTC)

It is Windows7 x64 Russian Edition on WAMP server Ektip (talk) 08:11, 6 June 2013 (UTC)

I believe this error occurs if you run on a Windows server. PHP on Windows can't use Unicode filenames, which is a very sad limitation, and it all kinda explodes.

If you run on a Linux or Mac OS X server you shouldn't encounter this problem. brion (talk) 21:51, 3 June 2013 (UTC)

OK. suppose to use virtual machine for this. Ektip (talk) 08:12, 6 June 2013 (UTC)

List of hidden special pages

Is there any list of hidden special pages, such as Special:MyPage hidden from Special:SpecialPages? Zhuyifei1999 (talk) 13:17, 30 May 2013 (UTC)

There is this list in SpecialPageFactory.php:

		// Unlisted / redirects
		'Blankpage'                 => 'SpecialBlankpage',
		'Blockme'                   => 'SpecialBlockme',
		'Emailuser'                 => 'SpecialEmailUser',
		'Movepage'                  => 'MovePageForm',
		'Mycontributions'           => 'SpecialMycontributions',
		'Mypage'                    => 'SpecialMypage',
		'Mytalk'                    => 'SpecialMytalk',
		'Myuploads'                 => 'SpecialMyuploads',
		'PermanentLink'             => 'SpecialPermanentLink',
		'Redirect'                  => 'SpecialRedirect',
		'Revisiondelete'            => 'SpecialRevisionDelete',
		'Specialpages'              => 'SpecialSpecialpages',
		'Userlogout'                => 'SpecialUserlogout',

☠MarkAHershberger☢(talk)☣ 15:06, 1 June 2013 (UTC)

Thanks. Zhuyifei1999 (talk) 00:15, 2 June 2013 (UTC)

You forgot Special:Mobile languages and Special:MyLanguage. 104.218.129.50 (talk) 20:39, 3 May 2024 (UTC)

Unable to get SyntaxHighlight GeSHi to work

Hello,
We have a Debian Squeeze server with PHP 5.4.11 and MediaWiki 1.20.5 installed. I am unable to get the SyntaxHighlight Geshi extension to work and am at a loss where to look next.

Product Version
MediaWiki 1.20.5
PHP 5.4.11 (cgi-fcgi)
MySQL 5.1.39-log

Installed extensions
Nuke (Version 1.1.7)
ParserFunctions (Version 1.4.1)
SyntaxHighlight (Version 1.0.8.4)(610d178)
ConfirmEdit (Version 1.1)
TinyMCE MW extension (Version 0.5.4)
Vector (Version 0.3.0)

The parser extension tag is showing on the Version page as well.

The MediaWiki was installed by grabbing the tarball, running through the install. It works fine. I installed the SyntaxHighlight Geshi extension by doing a git clone in the extensions directory. So, a copy of the Geshi project source is included. I've added the proper require_once line to my LocalSettings.php file to activate the extension. It appears to be activated as the Version page shows it listed.

When I go to add in source code with the "syntaxhighlight lang=" tag, I'm using the sample usage code at the top of the http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi page, the code is not properly formatted nor does it have color highlights.

Any suggestions where I should look next?
Thanks, Jay 64.207.233.106 (talk) 18:45, 30 May 2013 (UTC)

Turned out to be our editor. We were using TinMCE_MW. If I disable that and use the default editor, syntax highlighting works fine. Not sure yet why it would do that, but it does. With TinyMCE, I tried both the default mode, and the html mode, and it never would work.

I'll update again if I find out more.

Jay 64.207.233.106 19:31, 30 May 2013 (UTC)

broken resourceLoader response after update to 1.21

After an update from 1.19.6 to 1.21.0rc5 I temporary can't reach an JavaScript object defined in a resourceLoader module via inline script:

The object comes in with "ext.psladmincenter.top":

mw.loader.load(["mediawiki.page.startup","mediawiki.legacy.wikibits","ext.psladmincenterGlobal","ext.psladmincenter.top.effects","ext.psladmincenter.darkcg","ext.psladmincenter.jqgrid","ext.psladmincenter.top"]);

The error:

SCRIPT5007: Für die Eigenschaft "pslAcGridInit" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert

Curiously If I turn on "$wgResourceLoaderDebug" it works like before. What is the difference here?

It seems its a question of runtinme timing. What can I do? I need that inline script reference.

c u stevie Steviex2 (talk) 22:50, 30 May 2013 (UTC)

Given the name of the variable (pslAcGridInit) and the extensions it's loading (ext.psladmincenter.*) it looks like a problem with that extension.

If that extension wasn't created thinking of Resource Loader, you may need to adapt it following ResourceLoader/Migration guide for extension developers Ciencia Al Poder (talk) 09:44, 31 May 2013 (UTC)

The extension was developed by me with resourceLoader in mind and works in prior version without this bug since a long time. It seems that the top mdules are not fast enough loaded to reference objects initiated in such a top module with an inline "$(document).ready" - if I turn off resousourceLoaderDebug. The question is what makes the difference here.

Any ideas?

Thank you Steviex2 (talk) 16:32, 31 May 2013 (UTC)

Bringing User:Krinkle attention to this.

Turning on the debug makes each module to load each file in a separate request, so it may introduce a delay and causing the missing dependency to load before it's needed. Ciencia Al Poder (talk) 16:44, 31 May 2013 (UTC)

Ah okay Krinkle- that's an answer. What can I do to avoid the effect while running $wgResourceLoaderDebug in "off-mode"? Are there any tricks available? Can I influence the loading order and load my module before "mediawiki.page.startup" and "mediawiki.legacy.wikibits" as first module? Should I extend the scope of the object to window.*?

Thank you very mutch. Steviex2 (talk) 17:03, 31 May 2013 (UTC)

[RESOLVED] How do I fix "rsvg: not found convert"?

Hi guys,

I do not get thumbnails for SVGs. Instead of the thumbnail I only see Error creating thumbnail: sh: rsvg: not found convert: delegate failed `"rsvg" "%i" "%o"' @ error/delegate.c/InvokeDelegate/1061. convert: unable to open image `/tmp/magick-XXECMttE': gick-6.6.0/modules-Q16/coders/svg.la @ error/blob.c/OpenBlob/2489. convert: unable to load module `/usr/lib/ImageMagick-6.6.0/modules-Q16/coders/svg.la': file not found @ error/module.c/OpenModule/1229. convert: unable to open file `/tmp/magick-XXECMttE': es/8/8d/Logo.svg @ error/constitute.c/ReadImage/572. convert: missing an image filename `PNG:/tmp//transform_4d51a77323c2-1.png' @ error/convert.c/ConvertImageCommand/2940..

How can I fix that? 88.130.80.171 (talk) 01:58, 31 May 2013 (UTC)

Is ImageMagick installed? AKlapper (WMF) (talk) 07:52, 31 May 2013 (UTC)

Yes, it is in usr/bin. When I do "convert --version" on the shell I get the version number. 88.130.80.171 14:04, 31 May 2013 (UTC)

The package was not working properly; that was a debian bug. I could now fix it. After that creating a PNG out of the original SVG worked, but for the thumbnails I got the error "libgomp: Thread creation failed: Resource temporarily unavailable". I could fix that by setting $wgMaxShellMemory = 202400; in LocalSettings.php. 88.130.80.171 15:56, 31 May 2013 (UTC)

New to MediaWiki - could you please help me?

Hello everyone!

I am having trouble creating a infobox - I have inserted this code on the site:

{{Infobox
|title = Infobox Title
|header1 = Infobox Header
|label2 = Created by
|data2 = David
|label3 = External reference
|data3 = [http://trog.qgl.org trog.qgl.org]
}}

But it doesnt show anything! Could you help me?

Thanks in advance, Jan 178.157.206.142 (talk) 08:58, 31 May 2013 (UTC)

You need to create the page Template:Infobox on your wiki first for this to work. You can export a copy from wikipedia. ☠MarkAHershberger☢(talk)☣ 22:04, 31 May 2013 (UTC)

job queue : error handling recommendations

http://gwtoolset.wmflabs.org/index.php/GWToolset
MediaWiki 1.21alpha, PHP 5.3.10, MySQL 5.5.31

1. what are the recommended methods for handling errors when a job queue job runs?
2. when an error is encountered, what is the best method for reporting the error?
   1. use error_log?
   2. email notification?
   3. something else?
3. should all jobs return true no matter what happens?
   1. the assumption here is that if a job returns true no matter what happens, it will be removed from the job queue - is that correct?
   2. if jobs should not always return true, what is the process for handling those orphaned jobs that stay within the job queue? Dan-nl (talk) 11:23, 31 May 2013 (UTC)

restrict page editing to registered users?

Hi,

can I do that?

Thanks Magnus 195.200.70.53 (talk) 11:43, 31 May 2013 (UTC)

Hi Magnus,

set $wgGroupPermissions['*']['edit'] = false; in LocalSettings.php.

Cheers! 88.130.80.171 12:23, 31 May 2013 (UTC)

Media Wiki not showing correctly

hello, I just installed MediaWiki. I'm using IIS 7.5, Media Wiki 1.21.0, mysql-5.6.11-win32 and php-5.4.15-nts-Win32-VC9-x86. When I open it on my browser, the colors,images doesnt show. It just displays plain web site. Ergun~mediawikiwiki (talk) 13:37, 31 May 2013 (UTC)

Check Manual:Errors and symptoms#The wiki appears without styles applied and images are missing Ciencia Al Poder (talk) 16:31, 31 May 2013 (UTC)

There is no user by the name "foo". Check your spelling.

I've just set up a brand new site, initially with local users but now with users authenticated via ActiveDirectory. Somewhere along the way, one local user I had created for myself is now unmodifiable in the Special pages, e.g. if I try to set this user's preferences in Special:UserRights, I get There is no user by the name "foo". Check your spelling.

However, in MySQL, I can see this user in the user table, and all columns appear to be correct. I've checked and double-checked that the user_name in the table is the same one I'm entering on the site (while logged in as Admin).

What else can I check?

Using:

• MediaWiki 1.20.5
• PHP 5.3.3 (apache2handler)
• MySQL 5.1.67

Installed Extensions:

Special pages

• User Merge and Delete (Version 1.7)
• Realnames (Version 0.3.1)
• LDAP Authentication Plugin (Version 2.0c) 94.168.125.73 (talk) 13:52, 31 May 2013 (UTC)

[RESOLVED] Update to 1.21 broke some pages

I just updated a wiki from 1.20.3 to 1.21.1 >> http://www.subsurfwiki.org/ . Now I can read and edit pages, and image upload works. But some pages throw an HTTP 500 error, e.g. http://www.subsurfwiki.org/wiki/Wavenumber

The page exists and I can see the edit page: http://www.subsurfwiki.org/mediawiki/index.php?title=Wavenumber&action=edit (you have to be logged in to edit, but you can see the source at least). If I remove certain parts of the content, I can save the page and everything is OK again... but I can't tell what the problem is and have no idea how many pages are broken like this.

My upgrade method: unpack the new stack in parallel; copy over LocalSettings, extensions, etc.; go to read-only; switch the directories; run update.php; copy over images directory; go back to read-write. Everything in my installation is owned by the webserver user. All this has worked for me through previous upgrades since 1.18. This wiki is running on an up-to-date Amazon EC2 instance running Ubuntu, with a Bitnami LAMP/MediaWiki stack.

Any help appreciated. I am at a bit of a loss.

Cheers, Matt Kwinkunks (talk) 14:16, 31 May 2013 (UTC)

After giving up, my friend suggested checking all my extensions... and Success! It turned out to be the Cite extension. I grabbed the latest snapshot and now everything works.

Cheers, Matt Kwinkunks (talk) 15:23, 31 May 2013 (UTC)

Remember to upgrade your extensions whenever you upgrade MediaWiki! Ciencia Al Poder (talk) 16:32, 31 May 2013 (UTC)

[RESOLVED] common.css

hi how can I only allow common.css to work with the main page because I would like other pages on my wiki to look different so by doing that I would like to add codes to the page 90.215.249.160 (talk) 16:27, 31 May 2013 (UTC)

Each page has a identifiable class name applied to the "body" element, so you can target CSS style definitions to a specfic page by just using that class name as the selector.

The main page is special, and in addition to it's unique class name, it has the mainpage class.

So you can define your styles like this:

body.mainpage a { color: #ccc; } Ciencia Al Poder (talk) 16:36, 31 May 2013 (UTC)

do I put anything in the .common.css page to say only main page can use it 90.215.249.160 16:39, 31 May 2013 (UTC)

my website is located at http://random-wikisaur.tk 90.215.249.160 16:41, 31 May 2013 (UTC)

Yes, you should put that on the MediaWiki:Common.css page if you want this to be applied to all skins. See Manual:Interface/CSS. The CSS will be loaded for all pages, but the CSS selector will only match the main page and will only be applied there. Ciencia Al Poder (talk) 16:51, 31 May 2013 (UTC)

so that I can use for example mediawiki:common.css could bee used for main page and mediawiki:common.css/main page/sandbox could show differently 90.215.249.160 16:55, 31 May 2013 (UTC)

what do I put in mediawiki:common.css to say it is to only show on main page 90.215.249.160 16:56, 31 May 2013 (UTC)

Use the developer tools of your web browser and inspect the <body> element of your wiki. You'll see that it has some class names applied to it. One of them is "page-encoded_page_name" which matches the current page name, but encoded so it can be used as a class name. In addition, the main page has "mainpage" as a class name.

Since CSS rules are targetted to specific elements on a page, you should use the body.page-encoded_page_name selector before each selector you pant to apply to only that page. Ciencia Al Poder (talk) 17:16, 31 May 2013 (UTC)

Ok 90.215.249.160 17:47, 31 May 2013 (UTC)

how can I do that 90.215.249.160 17:58, 31 May 2013 (UTC)

I'm not going to teach you CSS since it has nothing to do with MediaWiki, so if you don't know how to write CSS to style your main page that's something you should ask on another forums or learn by yourself.

Once you know the basics about writting CSS rules, you'll understand this whole forum thread since I've already given you the key parts at my very first reply. Ciencia Al Poder (talk) 18:23, 31 May 2013 (UTC)

Getting slammed by bots - countermeasures?

I have a fairly no-frills Mediawiki installation on a server with several other domains - this week have been having problems with the entire server running out of RAM, MySQL crashing, etc. Just got off the phone with tech support & we narrowed much of the issue down to a substantial & sustained onslaught of spambots on my wiki.

I'm fairly new to the software, so am looking for the proper solutions to this. Right away I disabled new signups using the "$wgGroupPermissions['*']['createaccount'] = false;" line in Local Settings. Any other extensions or settings that can help with this?

Thanks in advance for any help. Rbsiv (talk) 17:50, 31 May 2013 (UTC)

I'd also be curious about any tools to bulk delete the countless accounts these bots have created. Rbsiv (talk) 17:52, 31 May 2013 (UTC)

You can use Extension:Nuke to disable (but not delete, AFAIK) the accounts. ☠MarkAHershberger☢(talk)☣ 21:54, 31 May 2013 (UTC)

Huh. I'm really baffled why the software doesn't have better functionality to manage users & specifically delete bot accounts & messages, especially when it's such a target for spam. My wiki was on a small site, no incoming links, and the project was on the backburner so I didn't check it for a couple months. Now I have thousands & thousands of fake accounts & posts (along with all their edits re-saved), and there doesn't appear to be any way to cull them in bulk.

Of course in hindsight I would have implemented some of the measures you linked to, but mitigating the damage that has been done would seem to be a very difficult task with the tools available. Kind of a drag. Rbsiv (talk) 17:55, 1 June 2013 (UTC)

There was a particularly good message about this on mediawiki-l the other day: "Our wiki has been spam-free for over a year now, despite anonymous editing being allowed..." ☠MarkAHershberger☢(talk)☣ 21:57, 31 May 2013 (UTC)

Wiki trashed by spam before big launch!

Could really use some help ASAP...

Before I corrected the permissions, my site (FoodForests.org) got hammered with hundreds of spam pages from just as many accounts.

It's a few days after my "big launch" in the local media, and still my site has yet to be listed by Google. This sucks!

None of the spam pages are currently linked from any public area of the site, as far as I'm aware. But I'm still really concerned that the abundant spam may have been spidered, and about the potential of spammy backlinks across the web (though I haven't found any yet).

How can I quickly hellban all the spam content and bots? And how I can show Google that I'm really an OK guy?

Thanks a ton! Andy, Sunspeck Labs (talk) 20:38, 31 May 2013 (UTC)

Check out Extension:Nuke to help delete the content. You may also be interested in this thread on mediawiki-l about fighting spam. I thought this email was especially helpful. ☠MarkAHershberger☢(talk)☣ 21:53, 31 May 2013 (UTC)

Add simple English to MediaWiki

hi could you add simple English to the mediawiki software please 90.211.217.98 (talk) 22:42, 31 May 2013 (UTC)

simple is included in the language preferences. ☠MarkAHershberger☢(talk)☣ 14:55, 1 June 2013 (UTC)

oh but when I created a new website and installed mediawiki and then setted it up there was no simple engish there there was only English and English british and Canadian english 109.157.103.6 13:35, 2 June 2013 (UTC)

Do you mean that the installer didn't allow you to choose simple? That is a bug, please report it and post the bug number here so I can follow it..

You can set the language to simple after installation. ☠MarkAHershberger☢(talk)☣ 17:49, 2 June 2013 (UTC)

filed a bug. ☠MarkAHershberger☢(talk)☣ 18:13, 10 June 2013 (UTC)

Thanks 5.66.159.208 07:20, 12 June 2013 (UTC)

Username lowercase

Hi.

Many posts but no real solution found so far.

1. Can I create a username which is completely lowercase? The first letter is always converted to uppercase.

2. Next ... can I rename a username "Abc" into "abc"?

Many thanks, Geohei (talk) 23:42, 31 May 2013 (UTC)

1. No, you cannot. You would have to modify the code in includes/User.php, newFromName() and the functions, which it calls. This code currently changes the first letter to uppercase. Although I do not know the exact reason for that, I well see that the other checks, which are performed to see, if a user is valid/usable/creatable, for a certain reason all do make sense. So I do not expect anything different here.

2. See 1. Maybe you actually can rename the username inside the database, table "user", but a) is going around the API that way not supported and b) would I expect funny errors to happen afterwards. 88.130.92.8 13:35, 1 June 2013 (UTC)

Thanks a lot for the answer. The reason I'd like to change this is purely "cosmetic". If I have to face potential DB corruption or weird behavior of WIKI later on, I won't touch it. However I do not see the reason why this case changes of usernames (and also of WIKI page titles) were implemented at a first place. Geohei (talk) 05:50, 2 June 2013 (UTC)

Sorry, I don't know either, but page titles actually really seem to be the main thing to look at: Also when a user is created, it is not only checked, if the username matches the conventions, but also, if the page can be created (which e.g. disallows usernames containing things like "../" as browsers would then no longer be able to open the user page).

If you are interested in that topic, you can read the sourcecode in includes/Titles.php. Maybe it contains a comment on why the first letter is uppercased. 88.130.80.241 11:51, 2 June 2013 (UTC)

Yes, will do so.

Thanks for the hint! Geohei (talk) 17:00, 6 June 2013 (UTC)

The relavent code to look at is actually in Namespace.php:

        /**
         * These namespaces should always be first-letter capitalized, now and
         * forevermore. Historically, they could've probably been lowercased too,
         * but some things are just too ingrained now. :)
         */
        private static $alwaysCapitalizedNamespaces = array( NS_SPECIAL, NS_USER, NS_MEDIAWIKI );

Other namespaces can be lowercased via $wgCapitalLinks. You can make the first letter of the username lowercase on the title of the userpage (only) via {{DISPLAYTITLE:...}}. Similarly you can use an alternative signature with a lowercase first letter. But at the end of the day, MediaWiki wants the first letter of usernames to start with a capital. Bawolff (talk) 23:38, 6 June 2013 (UTC)

I'm working on a patch to allow lower case usernames: allow lower-case user names ☠MarkAHershberger☢(talk)☣ 22:54, 18 June 2016 (UTC)