User talk:Skizzerz
Please start a new thread by clicking the link below. If you leave a message here, I will respond here (unless you state that I should answer on your talk page).
Archives
Your extensions [edit]
Hello, one extension written by you (or more) is listed on Git/Conversion/Extensions still in svn. The SVN repository will be closed in the future, and localisation support on translatewiki.net has already been dropped: please help update the list so that we know which extensions are still of interest and should therefore be moved to Git, and if possible volunteer to continue maintaining some requesting migration, or find someone else who can do so. Thanks, Nemo 14:58, 12 October 2012 (UTC)
- [History↑]
Contents
 First page |
 Previous page |
 Next page |
 Last page |
Hi Skizzerz. I noticed a few open rename requests, see Project:Requests#Requests for renames (the last four, from Avocato until Ghouston). As you're one of the active crats, could you please perform the renames/reject the requests/ask for more information if necessary? Thanks in advance for your help! Kind regards, Trijnstel (talk) 14:10, 31 July 2012 (UTC)
I have mediawiki 1.8.1 installed and I was trying your important extension. I installed it (I think) according to all the instructions (version 2.11). It gives me this error:
The metadata.ini file is either corrupted or missing. Please re-download the Maintenance extenson
I have installed it a couple of times but it does not work. It seems that there is some error on metadata.ini on line 69 Maintenance_body.php on line 51 Here is the text: Error parsing /hermes/bosweb/web117/b1170/ipw.insulaco/public_html/enciclopedialeopardiana/extensions/Maintenance/metadata.ini on line 69 in /hermes/bosweb/web117/b1170/ipw.insulaco/public_html/enciclopedialeopardiana/extensions/Maintenance/Maintenance_body.php on line 51 I do not understand. Could you help me? Thank you Emilio
Hello, Skizzerz I have a question/request about Extension:AuthorProtect, I have a four wiki farm and AuthorProtect installed on three, I have some userspace page headers that I would like to use Cascading protection with and as you probably know on the protection page when set to edit=author & move=author the cascading check box is there but does not accept input/change, is this a bug in my wiki or is it set this way in the extension and if so can this be changed ? Also I could not find a system message page like "MediaWiki:Authorprotectedpagewarning" is there some way I can create such a page or can this be added to the extension ? Just for FYI here is a link to a system message similar to what I would like MediaWiki:Semiprotectedpagewarning and MediaWiki:Semiprotectedpagemovewarning Just curious, these few items would seem to be a good addition to the extension. Thank you,
Cascading protection is not supported in AuthorProtect, as it would be simply impossible to manage correctly. The author of one page is not necessarily the author of another included in that page, meaning either users would either get locked out of pages they originally authored or they would get access to more pages than they are supposed to -- either way it is not a good situation. This is also not a design choice on my part, despite being a design philosophy I agree with, because MediaWiki is hardcoded such that the "sysop" level of protection is the only level of protection with cascading enabled on the protection UI. So, cascading protection will not be part of this extension.
As for the system message, unless MediaWiki provides one (attach uselang=qqx to the request headers to see if it does), it will also not be added as I believe MediaWiki already provides a warning of sorts that it is protected for authors, and you can simply edit that message instead. Coupled with other extensions that let you grab the protection level of a page via parser functions, you could make a dynamic message which changes content to what level the page is protected by.
Is it possible to use alternative in regex extension? I have a problem with this, since | is used between parameters. http://www.mediawiki.org/wiki/Extension_talk:RegexFunctions#Alternative_in_regex
The use of http:// is causing a warning when viewing <https://www.mediawiki.org/wiki/Manual:$wgAllowExternalImages>. Will protocol-relative syntax work there?
And the manual page itself should note the exception, honestly. I got confused why such an example was working on mediawiki.org. I briefly thought en.wikipedia.org had been set an external image source ($wgAllowExternalImagesFrom).
Doesn't appear that the parser handles protocol-relative URLs when used as bare links, so I just changed it to use https instead (as using an https resource on an http page doesn't cause any issues). I attempted to make a note but feel free to revise it and/or completely remove the whitelist entry if you feel the example shouldn't work for clarity's sake (this is a wiki, after all).
Why delete Template:Unblock?
Why delete this template? A user account could be unblocked.
It was deleted for the reason listed, in that it was a Spam/Junk page. Just because something is in the Template namespace doesn't mean that it is an actual template.
What did Template:Unblock actually contain? Please answer me to verify it is not Spam/Junk and then recreate the page.
The only revision of the page contained the following text:
{{unblock|Hello. I'd like to continue using this page so that I may better inform the bands supporters of the origins of our music. Thanks}}
If that isn't a junk page, then I do not know what is. In the future, I suggest you trust the judgment of the sysops here, as believe it or not we do actually know what we are doing. If we delete something, there is a 100% chance that the deletion was for a good reason, and the reason was clearly indicated in the summary.
HTFFanBrandon04 has a new signature and great potential to contribute to this project - so what did Template:Unblock do, contain, and what else?
It didn't contain an actual unblock template, it was something that didn't belong here.
Maintenance extension (trunk version 2.0.0) throws parser errors in MW 1.17.0 - no scripts shown in Special:Maintenance
Hello, could you look at Extension talk:Maintenance#MW 1.17 gives several parser errors please? Thanks, --Erkan Yilmaz 13:38, 11 August 2011 (UTC)
i had the same problem on mediawiki 1.18 any updates or instruction on how to make this extension work?
Fixed
Just wondering if any new information on the Error fixes Thanx.
Hi
I just upgraded from 1.15 to 1.17, so AuthorProtect doesn't work any more. I don't use a vector-based skin - in fact, my Skin doesn't work with 1.18/1.19 (otherwise I would have jumped to that). Do you maybe have one of those non-Vector compatible versions lying around somewhere?
Did you know about the Doc Camp this October? You should apply to go!
"Individuals with a passion for free documentation about free software may apply to attend by filling out the application form and submitting before 5 August, 2011. Those wishing to attend do not need to be from a GSoC project. Accommodation and food will be covered by the GSoC Doc Camp. Part or complete travel costs can also be applied for as part of the application process."
I'm going to send a proposal to get MediaWiki into the Doc Camp and to have us do a Quick Sprint to improve our documentation. Can I put you down as a possible participant?
best, Sumanah 16:37, 22 July 2011 (UTC)
Sorry, but can't miss out on school.
Hope you'll consider the New Orleans Hackathon 2011 then. We're getting together folks like you -- template, script, tool, extension, and gadget writers -- to participate, give feedback, test, and hack together. Sumanah 23:52, 24 August 2011 (UTC)
oeps.... need the authorprotect right of course.. forget it, sorry
There indeed seems to be a problem with the vector skin, any plans for a fix? --84.196.112.226
Per a recent update, AuthorProtect only works with MediaWiki versions 1.18 and above, where the protect link shows up properly in Vector. Modifying the extension to be compatible with Vector in 1.17 would require too much work to be practical. You will either need to download 1.18 from Subversion or wait for it to be released in beta/release candidate/stable stages.
shoutwiki have crashed a long time
I do not know when it will re-enable the wiki farm it?Msnhinet8jp 09:19, 24 July 2011 (UTC)
Hi, the #rreplace function of the latest version of Extension:RegexFunctions-1.4.1 stop working with MW-1.16.1+. See the report by User:Michael Allan at the discussion page of the extension.
Hi there Skizzerz. Jack Phoenix pointed me to your talkpage. Do you have any news on the server repairs on shoutwiki? Are you guys going to have to re-install the operating system? Thank you
Hi, I want to change the default link prefixes on a per-namespace basis in much the same way as it's done in wikidata's namespace manager. I don't need a manager page, just want to hack the php. Since you had made merging this functionality in a 'pet project' can you give me any pointers as to where to start with this? There are so many differences between wikidata and mediawiki 1.16 that I can't be sure what's important and what's not and want to make sure I've covered all relevant parts.
Thanks mike at meph dot net
My project is really only taking the ideas from wikidata, I'm not copying any of the code. That said, you'd be able to do this entirely in Linker.php if you don't mind hardcoding the prefixes in LocalSettings, or add stuff to the parser code to provide a new parser function for changing the prefix (although if you do this, you'll have to maintain another member variable of the parser most likely)
Hello. May I know why my request has been rejected ?
Thanks by advance.
This is a wiki about documentation of the MediaWiki software, the only pages that utilize FlaggedRevs (and thus have use for the reviewer group) are documentation pages for the software, and none of your edits show any sort of knowledge of the MediaWiki software. As such, giving you reviewer rights seems like a dumb idea since the entire purpose of the group is so that people who know about the software can validate pages as accurate or whatnot.
First page |
Previous page |
Next page |
Last page |
