User talk:Kghbln

(Redirected from User:Kghbln)
Jump to: navigation, search
MediaWiki-sysadmins-icon.svg This user is a proud MediaWiki third-party wiki system administrator.

exdi | kghblngit | fab | Core: Git Diffusion | Extensions: Gerrit / Git / GitHub / SVN | Wikia WikiaWiki | WikiHow | OD | Misc: - NSA
My Highest contribution rank on this wiki: #3 on 2014-08-31
My wikilove. :) Lovely, indeed. :)

Some stroopwafels for you!

Gaufre biscuit.jpg Thank you for help and encouragement on various tweaks.  :) Varnent 20:26, 16 December 2011 (UTC)

A barnstar for you!

Tireless Contributor Barnstar Hires.gif The Tireless Contributor Barnstar
For your truly awesome work on many wikis, in particular the Semantic MediaWiki one :) Jeroen De Dauw (talk) 15:02, 18 March 2012 (UTC)

A beer for you!

Export hell seidel steiner.png Thank you for your help though the program does confuse me quite a bit I appreciate you kindness in helping me if only you participated in adopting people then I would want you as a mentor have a beer in my kind offering to you. Kiki-kk (talk) 21:26, 16 July 2012 (UTC)

A kitten for you!

Kitten (06) by Ron.jpg

Thank you for cool edit on Extension:SpecialDeleteOldRevisions2‎ ! It is late and my head is of... It's good that you are on guard!

Jehy (talk) 20:53, 17 September 2012 (UTC)

Start a new discussion


Thread titleRepliesLast modified
Starting conversion of LiquidThreads to Flow at mediawiki.org111:53, 28 March 2015
Extensions which host their code in-wiki316:01, 24 March 2015
NSindex121:35, 13 March 2015
Review request Extension:Math416:51, 12 January 2015
Extension:ConfirmEdit319:45, 6 October 2014
Extension:ConfirmEdit118:31, 6 October 2014
No aliases308:09, 3 October 2014
If you get a second621:10, 29 June 2014
A barnstar for you!116:16, 23 June 2014
Thanks616:07, 16 June 2014
Manual:Pre-commit checklist106:54, 7 May 2014
Struggling to add the entire core to Git for the MediaInclu fork308:28, 5 May 2014
User Mediass4u312:59, 11 April 2014
Vandalism116:31, 18 March 2014
Display Languages Sidebar (Interwiki)116:53, 17 March 2014
iSC Dev BP Wiki - problem: picture215:27, 13 March 2014
Extension:MobileFrontend216:55, 27 February 2014
Thank you for your help with Extension:Surl114:42, 15 February 2014
Help to resolve dispute please312:34, 1 February 2014
Comments extension109:37, 10 January 2014
First page
First page
Previous page
Previous page
Last page
Last page

Starting conversion of LiquidThreads to Flow at

Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on over the last 360 days,[1] and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at There are links in the topic-summary at the top, for other discussions (wikitech-l and Project:Current_issues), and a link to the planned process and timeline (scheduled to begin April 6, with smaller conversions at first). Please do test Flow out at Talk:Sandbox if you haven't tried it recently, and give any feedback/suggestions/requests at that main discussion location. Much thanks.

Quiddity (WMF) (talk)23:43, 27 March 2015

Thank you Quiddity for notifying me about this. Much appreciated. Wow, I would not have guessed that I ended up in third place in this. Obviously I very much like LQT but I am also happy about the prospect of having a new way of talking about things. I already added infos about two of the three issues I currently have with Flow.

[[kgh]] (talk)08:06, 28 March 2015

Extensions which host their code in-wiki

You reverted my addition of Extension:Cumulus to this category. Am I using that category wrong?

Ckoerner (talk)15:14, 24 March 2015

No, basically you did not. However my follow up edit to the revert not only provides an informative info box but also the mentioned category via transclusion.

[[kgh]] (talk)15:21, 24 March 2015

oooooooooohhhhh. I totally missed that. :)

Ckoerner (talk)15:57, 24 March 2015

No worries. :)

[[kgh]] (talk)16:01, 24 March 2015

In September 2013, you removed one of my wikis, NSindex, because it "should not be publicised according to the webmaster". It was actually true back then because it was unfinished, but since then it is now workable because it has its own domain name. How do I make it publicisable now, while keeping out the bad robots (e.g. SEO)? Thanks in advance. :-)

Marianian (talk)17:30, 13 March 2015

Well, never seen a finished wiki yet. Perhaps this one will be the first but I doubt it. An own domain is a good starting point though. To my experience it takes a some time to get visible in the internet. Good content is the best one can do. To additionally help this you will probably like to have a look at this category (you will need to dig into meta tags for this) if you want to improve things on wiki. This setting $wgAllowMicrodataAttributes (you will need to dig into microdata for this) may be of interest too as well as this script GenerateSitemap.php (then you can register your sitemap e.g. with Google. A good robots.txt is a must too though the bad thing about bad bots is that they do not care about this. :( Still it's worth the effort for good bots. I wish you the best of success. Cheers

[[kgh]] (talk)21:35, 13 March 2015

Hi, can you review the changes in the page Extension:Math? Thanks.

Schubi87 (talk)12:58, 3 June 2013

Done. :)

[[kgh]] (talk)20:10, 3 June 2013

Thank you very much.

Schubi87 (talk)21:58, 3 June 2013

Sorry for spamming... Just wanted to reproduce


Schubi87 (talk)15:20, 10 January 2015

No problem. :)

[[kgh]] (talk)16:51, 12 January 2015

Hi there. I reverted your edit as the edit summary led me to believe it was vandalism. Given that you are just reverting everyone else, it's hard to understand why you made the edit in question. Maybe a more thought out edit summary would be appropriate? Thanks,

Tiptoety (talk)18:24, 6 October 2014

I am trying to reinstate the reverts of Nemo bis which I believe are vandal edits.

[[kgh]] (talk)18:26, 6 October 2014

Asirra is unsupported so I removed the documentation about how to install Asirra for ConfirmEdit. Nemo bis believes that this is vandalism as long as the dead code is still in the repo. I fail to subscribe to this. Instead of using the talk page he reverted twice. So this seems to be best practice now.

[[kgh]] (talk)18:29, 6 October 2014

The best practice is discussing the edit on the page's talk page. Anyways, thanks for explanation.

Tiptoety (talk)19:45, 6 October 2014


Sorry, I just realized that I was wrong reversing. Greetings.

Syum90 (talk)18:25, 6 October 2014

No worries. This was a terrible mess in the start. Probably I should have done without as many "!" in my comment.

[[kgh]] (talk)18:31, 6 October 2014

No aliases

Yeah, I'm running into the same problem you describe here with my older extensions too (and the new ones I'm creating with code borrowed from those). I guess when the solution is found, we can add it to Manual:Error messages.

Leucosticte (talk)13:44, 30 September 2014

Heiya, actually I found the solution to it. Since I was able to fix it I assume it is a easy one. :) The issue is that the extension defines a special page but does not provide a php-file containing the localised aliases for it. So this is basically a I18n issue. I think that I e-mailed a fix to Nad, however he has not moved it into the code afaik. Currently I am not home, so next week earliest I will be able to show how this may be avoided. Stay tuned... Cheers

[[kgh]] (talk)08:04, 2 October 2014

Yeah, I noted the solution in the Manual page.

Leucosticte (talk)15:50, 2 October 2014

Cool! :) I should have done this back then. :(

[[kgh]] (talk)08:09, 3 October 2014

If you get a second

Sorry to ask, I know I keep putting on you, but I don't have anyone else to ask :(

Have just create a new contact form extension that runs through a specialpage, is still in the developement process at the moment so excuse the look, still a few bits to tidy up as yet. The reason I ask if you can have a look is that I'm concerned there might be a security isue with it? Not sure how mediawiki works in that respect or hackers for that matter, you'll find the page here.

Cheers, Lee

SwiftSys (talk)12:25, 27 June 2014

Heiya Lee,

no worries and you should not be sorry for asking. As much as I would like to help you with this one: I simply cannot since I am not a developer and basically have not clue what PHP is all about. Even small changes I try to do usually end up in disaster. :( I just take the position of an sysadmin here.

Probably the best is to ask for you own WMF repo (see here) and invite other developers for a review of the code you submitted. Usually you get great responses and heaps of tipps.


[[kgh]] (talk)19:58, 28 June 2014

A barnstar for you!

Editors Barnstar Hires.png The Editor's Barnstar
Many thanks always appreciate your help and speedy revisions :) SwiftSys (talk) 16:08, 23 June 2014 (UTC)
SwiftSys (talk)16:08, 23 June 2014

Thank you, this is very kind of you! Always trying to be of help. :)

[[kgh]] (talk)16:16, 23 June 2014
Edited by 2 users.
Last edit: 16:07, 16 June 2014

Thank you for modifying my extension page, was a bit unsure how to add the content as this is my first extension, looks much better now :)

(talk) 06:43, 1 May 2014 (UTC)

SwiftSys (talk)06:43, 1 May 2014

Your welcome! Well, it is not easy to know about this when starting out on this wiki. Apart from that: It's a wiki, so you cannot do anything wrong. :) It is great that you are sharing your extension with others. Cheers

[[kgh]] (talk)07:29, 1 May 2014


thank you for kind words and support :)

Sorry for asking but I was wondering, the extension has been downloaded a few times, but users aren't commenting, so I can't be certain if there are any problems. How long should I wait until making the extension stable? Or does someone else decide that?

SwiftSys (talk)11:37, 2 May 2014


there are no problems with your questions. :) It is entirely up to you to assess if the extension is e.g. beta or stable. If you believe that it is up to its job and you received no error reports, then you may very well change the status. Usually one only gets feedback in case of problems, so hearing nothing it a good thing. :)


[[kgh]] (talk)07:09, 3 May 2014

Awesome thanks a lot :)

SwiftSys (talk)06:03, 22 May 2014

Thanks a lot for the speedy authorising edit :)

SwiftSys (talk)15:29, 22 May 2014


[[kgh]] (talk)15:30, 22 May 2014

Special:Diff/997083: Wait, why? I just checked my copy of mediawiki/core and there is no file or folder called "maintenance/languages/". There is only /core/languages which has the MessagesEn.php/MessagesQqq.php files or maintenance/language/

TeleComNasSprVen (talk)23:02, 6 May 2014

Oops, I was to fast here. Thought that both folders were consistently named. I just reverted my edit. Thank you for the pointer!

[[kgh]] (talk)06:54, 7 May 2014

Struggling to add the entire core to Git for the MediaInclu fork

Hey Karsten, I've been trying to add the latest development version of the entire MediaWiki core to Git for the MediaInclu fork. However, it doesn't want to add the entire thing. I clone MediaWiki, then clone MediaInclu, then recursively copy the MediaWiki core folder into MediaInclu, then do git add ., or git add --all, or git add *, and then git commit --all, and it only commits the empty core folder. I tried changing directory to core, and got:

nathan@nathan-Inspiron-518:~/MediaInclu/core$ git add .
git: pathspec.c:317: prefix_pathspec: Assertion `item->nowildcard_len <= item->len && item->prefix <= item->len' failed.
Aborted (core dumped)

Google wasn't a very good friend to me when I asked him about that error message; he pretty much blew me off without giving me a very helpful answer. Then again, sometimes it's best for a friend to honestly say "I don't know" if that's the truth. What do you think is going on? Thanks.

Leucosticte (talk)00:08, 4 May 2014

Heiya Nathan, well I am not really an expert on Git frankly written a novice. By what you are writing I think that Git is not able to identify the changes you made just by copying new files over old ones. Perhaps it is better to run an patch from MediaInclu over the cloned MediaWiki rather than recursively copying over the whole lot. However, this is just a guess. Apart from that I am stuck at a "I do not know" either. :( Cheers

[[kgh]] (talk)09:35, 4 May 2014

Actually, I hadn't even tried to commit any changes to the codebase; I was still stuck on the initial step of trying to commit the original codebase (see Hack_MediaWiki_core#Methods). But I got it now; I needed to get rid of .git and the other hidden files (.gitignore, etc.)

Leucosticte (talk)17:13, 4 May 2014

Oops, I obviously misunderstood your question. Great that it worked out after all. These nasty little details, I tell you.

[[kgh]] (talk)08:28, 5 May 2014

User Mediass4u

Hello. There where some Edits by Mediass4u the last few days. It seems that Mediass4u was blocked on Wikipedia, not sure why. Regards,

Felipe (talk)08:36, 11 April 2014

Heiya, well this user is not quite ready for editing I guess. If is is as bad as on this wiki. Yeah, let the admins decide on this. Cheers

[[kgh]] (talk)08:40, 11 April 2014

Is there a page on the MediaWiki wiki where you can report these kind of edits to a admin?

Felipe (talk)08:43, 11 April 2014

Frankly written, I have no idea. I not aware of such a page. Perhaps try to connect to one via IRC. Cheers

[[kgh]] (talk)12:59, 11 April 2014

Have you ever dealt with people whose interest was not just to spam but to vandalize? I've decided, maybe the best thing is to just put in place a really annoying CAPTCHA like Asirra that everyone has to deal with for every edit, till I manually put them in the Editor group. I used to only require the CAPTCHA for edits that add external links, but the vandals don't care about that; they're fine with just deleting or adding a bunch of text. Plus of course it's important to deprive all but trusted users of the reupload right, I found out the hard way. I'm working on blocking the open proxies too, although I have mixed feelings about that because I think some good users, especially of controversial wikis whose content borders on illegal, use proxies to avoid government surveillance.

I might create some sort of automated mass revert tool; I started work on it but it's hard to stay motivated. If you have other ideas, you can put them at countervandalism development. Thanks.

Leucosticte (talk)01:54, 16 March 2014

Yes, vandalism is quite common and it is very time consuming to clean up the mess vandals made. So tools to speed up and improve this process should be very welcome by site and wiki administrators.

I also think that requireing CAPTCHAs all the time until a user has been put into a trusworthy group is the best approach. This is what I ususally recommend doing. It is not as dismissive as the ConfirmAccount and surely the reason why this extension is not spreading.

You are right about proxy blocking, so in cases of valid proxies a whitelist may be the better approach.

I have commented and brainstormed on the countervandalism talk page.

[[kgh]] (talk)16:30, 18 March 2014

Display Languages Sidebar (Interwiki)

How can I display the interwiki languages wikis in my sidebar?

Example, like this:

English Wikipedia - Languages Sidebar.png
Suriyaa Kudo (talk)14:42, 14 March 2014

You should have a look at Interlanguage links as a starting point.

[[kgh]] (talk)16:53, 17 March 2014

iSC Dev BP Wiki - problem: picture

Hi kghbln,

I have a problem with showing pictures in my new wiki: iSC Dev BP Wiki. It is looking like this.

Suriyaa Kudo (talk)16:41, 12 March 2014

Ouch, never had this before. That's strange since there seems to be read and write access to the "image" directory but not to the subdirectory "thumb". It is a problem with the read and write access anyway. Perhaps $wgThumbnailScriptPath is a way out. You could always give it a shot at Manual:Errors and symptoms and the support desk.

[[kgh]] (talk)08:21, 13 March 2014


Suriyaa Kudo (talk)15:27, 13 March 2014


Hi Kghbln,

I want to ask why you delete the template?

Suriyaa Kudo (talk)16:51, 27 February 2014

Heiya Suriyaa, well I did not delete the template, I just removed it. See your talk for the reason. Cheers

[[kgh]] (talk)16:54, 27 February 2014

Ok thanks.

Suriyaa Kudo (talk)16:55, 27 February 2014

Thank you for your help with Extension:Surl

It's our 1st extension and we don't know how to add it correctly! Edlira is installing and configuring GIT now so we can add a link to it. We might have a few more questions! The extensions helps a lot to run WikiTranslate, so someone else might benefit from it too!

Natkabrown (talk)14:09, 15 February 2014

No problem at all. Nobody is an expert from start. An easier way might be to use GitHub like many more projects here. This would also allow for easier code changes by others. I will have a look at the extensions page in a couple of days and do some edits if necessary. Great wiki by the way. :) Cheers

[[kgh]] (talk)14:42, 15 February 2014

Help to resolve dispute please

Hello Kghbln,

Please could you help resolve a dispute at Manual:Upgrading? I've included the path to the logo image that people change on their own Mediawiki installs. After unpacking the tar ball they will need to replace the image file again. An anonymous editor keeps removing this info, saying "Is already in the linked page. You should not change stuff inside the folders that come with the tarball. Changes will be reverted by an upgrade making things unnecessarily complicated. Advising to do". Even after I made a separate section Manual:Upgrading#Other_files about what to do after extracting the tarball.

Rob Kam (talk)15:19, 31 January 2014

Heiya Rob, well I have had this page on the sighting list a couple of times recently. I did not dig into this deeper though. Admittedly I do tend to opt for the IP, however I can also live with the path being shown on Manual:Upgrading, too. Actually this particular sentence should be rephrased a bit. Cheers

[[kgh]] (talk)22:17, 31 January 2014

Thank you for your help and the tweak :-)

Rob Kam (talk)22:35, 31 January 2014

No problem. Hope that this did the trick. Cheers

[[kgh]] (talk)12:34, 1 February 2014

Comments extension

This edit on the Comments extension page changed the included file from "comment.php" to "comments.php" in the installation instructions. The name of the file in the extension actually is "comment.php".

Truth is, the name of that file should probably be changed to "comments.php" to comply with convention, in a way that maintains backward compatibility. What do you think?

Ike @ WikiWorks23:22, 9 January 2014

Ouch, this was indeed a bad change I made. The naming of the file is however a bit unexpected since it appears that comments is used in nearly all the other context of the extension. I am guessing that this is an old inheritance from the early days of this extension which was never changed along the way. Changing from "Comment.php" to "Comments.php" is a good idea but not imperative. Perhaps "Comment.php" could just include a call like include 'Comments.php';. Still I will revert this change to make the page correspond with reality again. Thanks for the pointer!

[[kgh]] (talk)09:37, 10 January 2014
First page
First page
Previous page
Previous page
Last page
Last page