Hey, why the hell did you block [http://www.mediawikiwidgets.org/wiki/User_talk:Mlpearc] my account] ? I am a long time user in good standing, and I've never been blocked. Please review your actions and unblock me. Cheers, ~~~~
About this board
| Core: |
| Skins: |
| Extensions: |
| Misc: |
Some stroopwafels for you!
|Thank you for help and encouragement on various MW.org tweaks. :) Varnent 20:26, 16 December 2011 (UTC)|
A barnstar for you!
|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!
|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!
Thank you for cool edit on Extension:SpecialDeleteOldRevisions2 ! It is late and my head is of... It's good that you are on guard!
Why am I blocked ?
Hey, I actually deleted and blocked thousands of pages and accounts supported by the new Smite Spam extension. In the heat of the action I may have done "better" than required. As a matter of fact I blocked myself too. So there is no reason for why the hell I you are in good standing I suppose. Of course i can reinstate you. Thank you.
I understand, no problems. Thank you and have a great day :)
Yes, you blocked me (an admin) as well. Please correct. :)
Done. All should be fluffy now. :)
Extension:ContactPage "No email address"
I am having HUGE troubles getting your ContactPage extension to work with my wiki.
I'm getting the following error message on Special:Contact DESPITE specifying a valid email in LocalSettings.php
"No email address
This user has not specified a valid email address."
I'm using MW 1.25.2 with the master branch of ContactPage, (although the 1.25 stable ContactPage does the same thing).
The syntax I'm using is: 'SenderEmail' => 'email@example.com',
NOTE: This *is* also the default $wgPasswordSender which also works for sending/receiving emails, just not with this extension.
Can you please assist me with getting it to work?
Kind regards, -- User:BradLeeBH
Hi BradleeBH, well this is not an extension I developed and as a matter of fact I am not even a programmer. However, I answered on the extension's help page. Cheers
Sorry, I saw you had replied on some of the threads and mistook you for one of the extension developers.
No worries. I use this one too and the docu was pretty bad back when. So I helped answer questions as good as I can.
Question for you at CollapsibleVector
Oops, I was not notified, neither of this message nor the one at the extension's talk page. I just saw this by accident. Replied there. Thanks for the note and cheers
[[Requests for comment/Password requirements]]
Hi, Requests for comment/Password requirements is being considered as one of the RFCs to be discussed at the RFC review on 2013-11-06 via IRC. You are receiving this notification because you edited or discussed this RFC. We hope to see you there.
thank you for the notification.
Well, it was not exactly me adding this request. Just been the last one to touch the page thereafter. Thanks for looking at it. I just added some more stuff to the page and reviewed it. Cheers
out-comment of AYAH instructions on [[Extension:ConfirmEdit]]
Hmm, that advice seems a bit unusual. However we indeed have source and version history for this page. The reviewers for your change are pretty smart people according to my experince, thus I am sure they will figure it out. :) There is also still the option of Nemo reverting my edit. Cheers
I respond to your question on my user talk pages. I do it. Version of AccessControl 2.5 is actively using in our school wiki https://support.dce.felk.cvut.cz is based on MediaWiki 1.20.5 (375d04b) and my wiki https://www.thewoodcraft.org is based on MediaWiki 1.25alpha (b19eec3)
Unfortunately my communication skills in English are not great, thats why I was not able to discuss what one is doing wrong.
Heiya Want, thank you for your reply. I was asking since multiple breaking issues for the code were reported for this extension during the past year. I am puzzled why the extension is working for you. I just spent 2 hours to get it working without success. I have no idea how to interpret the instructions. Perhaps you have a friend with better English skills who could write the instructions. Anyway thanks for your effort creating this extension. Cheers
I don't know, what is wrong for you. I am doing clone of mediawiki core from git, and extension is installed by Manual:Extensions. See important lines from my
$wgGroupPermissions['*']['createpage'] = false; $wgGroupPermissions['*']['edit'] = false; require_once( "$IP/extensions/AccessControl/AccessControl.php" ); $wgAccessControlRedirect = true;
These settings were ok. I now successfully got it to work by applying the following patch to "AccessControl.php" on line 151 as described at this spot:
$gt = $Title->makeTitle( 0, $group );
$gt = $Title->makeTitle( 9998, $group );
I replaced the 0 for the main namespace by the 9998 for the custom access control namespace.
Now things are up and running. Still wondering why it works for you.
The explanation is simple. Extension:AccessControl of the principle does not require custom namespace as somebody wrote in step 2. In older versions of MediaWiki was other detection of namespaces than today. On the talk page is a patch that will allow it but I do not have time do tests that would determine whether if application of it being disruption of functionality or not.
Ah now I get it. So basically the definition of the user groups should happen in the main namespace. Well doing it in a separate one has some appeal but yeah it is the misleading instructions which cause confusion. Thanks as always for your fast reply and thanks a bunch for this extension!
I'm not entirely sure, but I think that the visitor which hasn't access to the namespace where is page with list of members, he not have access to content of page which is protected over extension, although he was on this lists, because his access to page in protected namespace may be denied.
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. :-)
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
Hi, I did accidentally slip up over robots.txt in WikiApriary back in the days when we were beta and that was the same time when someone was stealing my friend's photos on Flickr, and I am sorry for that.
NSindex is a lot better now and my fury is now more towards Google over privacy. I probably want to manually maintain my website's entry, but I lost the account since I shut down the email associated with it! Oh well, it was a Google email anyway...
No worries. Luckily there are alternatives for e-mail around. I just re-activated data collection and if you like you could re-register and fluff up the entry a bit. Cheers
Thanks: if WikiApiary accidentally hits another filter then please get in touch with me over the filter that's causing the problem and I will override it. I am planning to work on a spider trap for bad crawlers like what Wikipedia does, but this is nothing to do with you.
Starting conversion of LiquidThreads to Flow at mediawiki.org
Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on mediawiki.org over the last 360 days, and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at mediawiki.org. 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.
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.
Extensions which host their code in-wiki
You reverted my addition of Extension:Cumulus to this category. Am I using that category wrong?
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.
oooooooooohhhhh. I totally missed that. :)
No worries. :)