Team Fortress Wiki talk:Technical requests
Contents
Jeff
Jeff should know this page exists now. -- Pilk (talk) 21:33, 6 August 2010 (UTC)
EmbedVideo
I'm under the impression that we're already using this extension, but also, I believe Jeff said he won't upgrade to the latest version because it has security issues or something. We should look into this and find a better Extension. This one is quite annoying. -- Smashman... (t • s) 23:33, 6 August 2010 (UTC)
Special:RandomPage
Is there any way that we can make Special:RandomPage not redirect to subpages? Obviously the primary language of the wiki is English, and there's really no point presenting the majority of people with a Russian page who then might click again to get a German page. -- Pilk (talk) 09:45, 21 August 2010 (UTC)
- WindPower has created an extension for use. It's quite brilliant! He's made it so that if you're on an English page, then random page returns only English pages, if you on a localized page then it will only return pages of the same language. Pretty fancy! -- Smashman... (t • s) 10:37, 22 August 2010 (UTC)
- Source to WindPower's extenstion. – Smashman (talk) 20:24, 29 August 2010 (UTC)
- The extension requires the SpecialRandomGetRandomTitle hook that was added in 1.16.0. I have successfully installed it on the Alien Swarm Wiki, which also runs on 1.15.4, by simply overwriting 1.15.4's SpecialRandompage.php with the version from 1.16.0, and it seems to work fine. So either an upgrade to 1.16.0 or simply overwriting this file would work. Thanks~ — Wind 20:27, 29 August 2010 (UTC)
- Source to WindPower's extenstion. – Smashman (talk) 20:24, 29 August 2010 (UTC)
Update to MediaWiki version 1.16.0
Could we update to MediaWiki version 1.16.0, please? It contains a number of fixes and also, the new Vector skin which should help with usability. Thanks. -- Smashman... (t • s) 10:43, 22 August 2010 (UTC)
- Valve are most likely keeping to legacy releases at the moment (1.15.*). Vector would be cool, but I assume they have security and compatibility issues to keep in mind. seb26 [talk] 11:06, 22 August 2010 (UTC)
- Why would they do that? 1.15.4 was the latest version when this wiki was released and if Wikipedia are using it, then it won't have security concerns. Believe me, Wikipedia are more likely to be worried about security, and if they're good with it, then it'll be more than secure enough for our requirements. -- Smashman... (t • s) 11:31, 22 August 2010 (UTC)
If you look at the patch-notes, the only changes we could really benefit from are a couple of new interface strings (such as ones that appear below talk page editnotices) and the Vector skin. This needs to be weighed up with the possible issues that could arise with the style sheets or other things, and the fact it would delay the other requests for real things like extensions because upgrading is not a simple process. -- Pilk (talk) 11:28, 30 August 2010 (UTC)
I'm going to chime in here and also request that Valve is pressured into upgrading the wiki to the 1.16 branch, as I believe given the number of edits these days, that getting the "grouping" functionality of edits to the same page on the Recent Changes list, and in the Watchlists is almost essential at this stage. TheChrisD Rants•Edits 01:39, 25 January 2011 (UTC)
Move?
Why, oh, why did you do that? I sent an email to Jeff YESTERDAY to take a look at these. Put them Goddamn back. – Smashman (talk) 10:13, 30 August 2010 (UTC)
- Smashman seb doesn't need your attitude, seriously. If you want it back you should do it. Discussion on the usefulness of a particular request should be on the talk page itself though. Jeff shouldn't have to go through the discussion to determine what we came to the conclusion of. At the moment this upgrade is contentious anyway. It shouldn't be up til we agree on it. -- Pilk (talk) 10:50, 30 August 2010 (UTC)
- Well I can't do it, hence my asking to do it. I didn't wish it to be a discussion, it was meant to be a request, but seb decided to have a discussion. I do not see a reason why we wouldn't wish to upgrade. And the RandomPage thing was your request that Wind fulfilled and it merely needs an upload. – Smashman (talk) 11:02, 30 August 2010 (UTC)
- I want 1.16 too, but it's unlikely to happen at all. It's clear that Valve are sticking to legacy releases, and that they have their own reasons for it, and are unlikely to listen to our opinions on it, regardless of how big a site Wikipedia is or whatever. And Wind's random page thing says it needs an updated .php file or something, so that seems even more unlikely to be done. seb26 [talk] 11:08, 30 August 2010 (UTC)
- Well we might as well request on this page. Valve don't seem to be using legacy releases at all. The version we have here was the most current version at the time of our set up, so I don't see why they wouldn't update. Jeff was also telling me about the next update having the Vector skin, and this meaning that the current Valve skin will need fixing. This definately seems like he had updating in mind. Could we merely request it and see Jeff's opinion? Thanks. – Smashman (talk) 11:26, 30 August 2010 (UTC)
Believe me seb, I would if I could. Mobile IRC program anyone? – Smashman (talk) 11:37, 30 August 2010 (UTC)
Moved requests off the page
Why did you remove requests of the page? I maybe understand why rejected requests were moved, but the accepted requests were here so Jeff/anyone can view them. Did Jeff acknowledge that he had these on his own todo list? -- Pilk (talk) 20:04, 31 August 2010 (UTC)
- I doubt Jeff would want to see them again. As he's already reviewed them. If he wants, he can click the tick at the top. – Smashman (talk) 21:20, 31 August 2010 (UTC)
Extra file formats
SVG images won't happen. For starters, they have to be rendered into PNG by a separate plugin. It's not something the software can do by itself. When you consider the difficulty involved in getting a smaller extension added, and you couple that with the fact that there isn't anything special SVG images can do (that scaling down a high res PNG can't do), then it just won't happen. A video format is also out of the question too. Hosting video files means additional unnecessary bandwidth for Valve: why the bother when you can just use YouTube? As for .cfg files, I don't particularly understand. Not too long ago we deleted all of the class scripting pages, and one of the justifications was that "we shouldn't be competing with modding sites like fpsbanana". If we were to bring them back, then hosting .cfg files will only complicate maintenance further, as you must download the file to see what's in it (and none of the scripts we could host wouldn't be very long anyway).
As for the other file formats (mp3, ogg & compression formats), they seem like reasonable suggestions, I'll re-add them to the page. seb26 [talk] 20:19, 13 October 2010 (UTC)
- SVG should be supported for scaling. SiPlus 07:31, 13 July 2011 (PDT)
Auto-Translate?
Hi, there! Should a auto-translate (for all languages) be helpful? (Then with a added "help with translating" tag.) [] /shadow/sShaD'OhsS 11:30, 16 October 2010 (UTC)
- By 'auto-translate', I hope you don't mean Google Translator. This was discussed at length somewhere else, but put simply, there isn't any way that a computer can translate into another language better than a native speaker can. seb26 [talk] 11:39, 16 October 2010 (UTC)
- i agree with seb here i was myself going to do the auto translate (google translate) as a tester i translated somthing into swahili and back to eglish again and didnt get the right results --Iaindude 10:21, 17 November 2010 (UTC)
Not sure if this belongs here, but it's worth pointing out.
So I'm not sure if this is my broswer's (Google Chrome) problem. When I zoom in on the page, the header is white, as normal. Although, when I zoom out, it glitches and turns to a dark grey. Any ideas? - MLGM 14:45, 17 May 2012 (PDT)
