Fatal error: Call to a member function addWikiMsg() on a non-object in /home/username/public_html/wiki/includes/specials/SpecialLinkSearch.php on line 82

Have you edited it before?
Check any code errors on LocalSettings.php.

Jeffwang‎

Hi , I did not change any thing in localsettings.php. This is a new installation. please see my localsettings.php here

http://paste.ubuntu.com/805960/

Can't it be because of my server tight security?

Ibro‎

Hmm... well it isn't LocalSettings? Are you sure you did not change anything? Sometimes notepad will add BOMs.

Jeffw • (talk)‎

Note, BOM's cause a different type of error. (headers already sent error)

This type of error would be caused if the relavent OutputPage wasn't being returned properly from the SpecialPage's context. I have no idea how that can happen (and furthermore, no idea how that could happen without many other massive errors popping up everywhere on your wiki) [This is probably a bug in MediaWiki]

Could you test temporarily disabling all extensions (just comment out the require_once lines near the bottom of LocalSettings.php) just to check if its being caused by one of those extensions (seems unlikely, but good to check).

p.s. You may want to change the value of $wgSecretKey and $wgUpgradeKey afterwards since they were left in your LocalSettings.php

Bawolff‎

You said " You may want to change the value of $wgSecretKey and $wgUpgradeKey afterwards since they were left in your LocalSettings.php

How to do it? for test I just addes abc at the end of $wgSecretKey and $wgUpgradeKey but got the same error. What can I do now? Amy body can help?

Ibro‎

I mean you publically posted them. It doesn't really matter what they are, but they should be secret (think of them like a password) or else people can do evil things to your wiki. You should be able to change them directly in your LocalSettings.php

Bawolff‎

Bawolff I have not made public my wiki url so what danger is there if $wgSecretKey and $wgUpgradeKey is public?

Ibro‎

There isn't a whole lot of danger then. Its still not exactly a great idea from a paranoia perspective, but probably not something to worry about if no one knows where your wiki is located.

Bawolff‎

Thanks just curious what if my wiki IS public but it is completely private , Directory password protected and more over it is restricted with an htaccess to an IP address? If still some body knows $wgSecretKey and $wgUpgradeKey can there be any danger?

Jafarda‎

Well first of all, that depends if the people who are allowed access are trustworthy (I suppose that goes without saying). If no one evil can access your wiki, then they can't really do evil things to it.

Leaking $wgUpgradeKey would allow someone to run the installer. Off the top of my head I think that only allows someone to basically update db tables (Which could perhaps open you up to a DOS attack i suppose maybe, not sure if any evil could really be done here. but its definitly not something i'd want randoms to have access).

$wgSecretKey is related to how tokens for user authentication are generated (aka the stuff we stick in cookies to make sure a user stays logged in). If an attacker knows this, it would make it quite a bit easier for them to spoof a cookie, and gain control of another account (Still would be quite a bit of work, just a lot less than wthout $wgSecretKey)

[This is mostly off the top of my head, there's definitely the possibility i missed something here]

Bawolff‎

OK Jeff not sure, Is there any original file I can replace it with what I have? but when I try to add the data base info in there what should I do? what is the right way or editor to make the changes?