Help
Add this page to your book
Show book (0 pages)
Suggest pagesUser 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
Contents
 First page |
 Previous page |
 Next page |
 Last page |
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.
As the seemingly active 'crat around here, when you've got a chance I've filled a request to change a users' name. Thanks
Agreed, it is far from finished as I still need to finish the command list and figure out how I am going to deal with the pchart class. It's that way because I have been using nano for the entire initial building process. I'll be going over my code and adjusting it to the specifications once I am finished testing. Should I remove the code section until it is in a more complete status? I really just wanted to make the placeholder, I figured I should put some content in there, albeit partial. Endofzero 02:24, 25 August 2010 (UTC)
No, you can keep the code there. Just let me know when it's in a more readable state (even if it is still unfinished) if you'd like me to check it over.
Hi there, I was wondering if you could take a look at my extension request. I'm sure it shouldn't be so hard for an accomplised extension dev, such as yourself. Thanks.
Hello, I want know How put a bar in Wiki, see this Wiki http://www.wiki.srb2.org, I whether know,the bar MAIN PAGE how put it ? 201.95.189.62 16:38, 21 August 2010 (UTC)
Hey Folks,
I've got a little problem in using AuthorProtect. I get this error: Fatal error: Call to protected method Article::flattenrestrictions() from context ...AuthorProtect/AuthorProtect.php on line 208
Has someone a hint?
Thanks in advance!
Upgrade to version 1.2 of AuthorProtect (which was released June 2009 so there really isn't any reason why you don't already have that version)
First page |
Previous page |
Next page |
Last page |
