User talk:CzechOut7708

 Welcome to The Vault! Hello, CzechOut, and welcome to The Vault, the Fallout wiki! Thank you for your contributions, and we hope you'll stay with us and make many more.

Some links you may find useful:
 * Recent changes lets you see what other people are editing currently and where you can help. You can also check our community portal for things to do.
 * If you haven't already, create a user page about yourself. If you do, we'll be able to know you better as a member of our community.
 * If you are new to wikis, the help pages can help you learn how to edit and how use the wiki tools. For test edits, feel free to create a personal sandbox.
 * The Vault's policies and guidelines describe how we do things around here and can help you make even better contributions.

If you have questions, you can ask in our forums, join the live chat in our IRC channel or post a message on my talk page. We hope you enjoy editing here and look forward to working with you!

-- Veryblackraven (Talk) 01:17, May 21, 2011

Help with Archive Tool
In Oasis, the "archive" button is added to the edit button options on talk pages (i.e. the pulldown menu with "leave message" etc). It works fine here on this wiki, so I don't think it's been rendered non-functional by some sort of Wikia changes.

You also have to keep in mind that you should always do a "hard refresh" (CTRL-SHIFT-R in Firefox) after you've tinkered with the JavaScript/CSS pages to make sure your browser doesn't have an old version of the pages cached.

The only further advice I can give you is to either import the script from dev or copy the content of wikia:dev:ArchiveTool/code.js to your wiki; our version here is slightly modified and tied into our other scripts (the whole "vaultScriptLoader" thing) and causes errors if you don't have the same scripts installed.

Hope this helps somewhat ;) -- Porter21 (talk) 09:19, May 21, 2011 (UTC)


 * Well, after your changes it works fine for me both on this wiki and yours in the Windows versions of Internet Explorer, Firefox, Opera, Safari and Chrome. The only thing which is out of order is that I'm getting two "Archive" buttons on your wiki, but that's because you're importing Common.js in Wikia.js, effectively running the script twice - unlike Common.css, Common.js is loaded by the Wikia skin, so importing it in Wikia.js isn't really necessary.
 * The redlinked "templates" don't really do any harm; that kind of stuff happens if there is wiki-like syntax on a JS page, which is then interpreted by the MediaWiki software like on any other page. You can easily fix it by inserting  at the very start of the JS page and   at its end.
 * Otherwise, I'm a bit at a loss. I don't really know whether we have Mac-using editors here, and since I'm getting no errors of any kind it'd be hard to troubleshoot it for me. Could you check whether there are any errors displayed in the Firefox error console ("Tools -> error console"; hit "delete", reload a page and see whether anything with a red symbol pops up)? Pretty much the only chance. -- Porter21 (talk) 13:50, May 21, 2011 (UTC)
 * That's indeed useful - I have an idea what the error might be caused by (the ArchiveTool one). I'll take a look at it tomorrow. Just double-checked that page and I'm not getting any of those error messages in the Firefox or Firebug console, so it indeed seems to be a platform-specific thing. -- Porter21 (talk) 22:19, May 21, 2011 (UTC)
 * I've made some changes - could you check whether something has changed on your end? -- Porter21 (talk) 08:15, May 22, 2011 (UTC)
 * That's interesting because I just noticed I fixed the wrong script (DisableArchiveEdit rather than ArchiveTool) :P Could you try again now that I've actually changed the ArchiveTool script? -- Porter21 (talk) 09:49, May 22, 2011 (UTC)
 * Sorry to hear it's still not working. The Monobook error looks unrelated, and without any error messages to go on my ability to try and address this problem is very limited without being able to reproduce the problem myself (which I can't because I don't have a Mac). There isn't even much of a difference in the ArchiveTool code for Monobook and Oasis; the only difference is the name of the page elements where the button is inserted and the HTML for said button - both of which can't really be the cause of this problem, otherwise it wouldn't work in Windows browsers. Long story short, I'm out of ideas. -- Porter21 (talk) 15:16, May 22, 2011 (UTC)

The EditIntroButton code to insert the button option is virtually identical with the one used by ArchiveTool and there really is no difference syntactically between the Monobook and Wikia code bits.

After looking into it some more, I'm actually pretty sure that the script is not at fault at all but rather the Wikia skin. The red error you were getting ("error: d is undefined") originates from that skin's JS (oasis_shared_js), and it's possible that this error halts the execution of other JavaScripts on the page - which would explain why there's no problem in Monobook. Seeing as I don't get that error with Firefox on Windows, it seems like the most likely cause of the issue. -- Porter21 (talk) 07:42, May 23, 2011 (UTC)


 * Well, you just said it made "the error" go away so I assumed you were talking about the warning. Oh well, so much for the theory - but as I said before, I can only make guesses as long as I can't reproduce the problem myself, especially without anything to go on. -- Porter21 (talk) 17:12, May 23, 2011 (UTC)


 * The reasoning behind assuming the Wikia skin's JS (or something on the computers of the users experiencing the problem) interferes with ArchiveTool is as follows:
 * If there was an error in the script's code, it wouldn't work in any browser.
 * If the script was using syntax your browser can't interpret, it wouldn't work with the Monobook skin (the Wikia-skin-specific bits contain only very basic code, and I've checked them three times by now).
 * As a final test, I've added some debug code which generates a few messages in the Firebug console. This way we can track down whether the script is loaded at all and whether it goes through with loading. Could you check your test page and tell me which messages (prefixed with "ArchiveTool:" you're seeing in the Firebug console? -- Porter21 (talk) 18:21, May 23, 2011 (UTC)
 * The message you got means that the ArchiveTool script starts running, but since you didn't get the other 3 messages, it doesn't finish. Since the button is inserted at the very end of the script, it doesn't appear because the script never gets that far.
 * I'm now trying to pin down exactly where the script gives up. I've inserted a few more debug messages - could you check which ones you're seeing? -- Porter21 (talk) 12:48, May 24, 2011 (UTC)
 * Anything different now? -- Porter21 (talk) 14:27, May 24, 2011 (UTC)
 * Getting closer - any changes? -- Porter21 (talk) 14:46, May 24, 2011 (UTC)
 * You get wgAction = edit when viewing the page (i.e. not when editing)? -- Porter21 (talk) 14:56, May 24, 2011 (UTC)

And there we have found the Wikia skin bug :) The wgAction variable (from MediaWiki core) should contain the action the user is performing currently, i.e. when viewing the page it should be "view", not "edit" - and it is for me. The ArchiveTool script checks whether the user is currently viewing the page as to avoid potential unwanted interactions with the edit screen. If wgAction is "edit" when viewing, it's perfectly understandable that the script aborts (it's actually intended). I'm pretty sure if you look at the page in Monobook, you will get "wgAction = view" in that console message - which is why it is working for that skin. -- Porter21 (talk) 15:15, May 24, 2011 (UTC)
 * Yeah, you should probably report it. I could fiddle with ArchiveTool to work around this bug, but it could affect any number of other scripts as well - wgAction is a rather commonly used variable. -- Porter21 (talk) 15:28, May 24, 2011 (UTC)
 * No problem. At least I now know the problem is not my fault :P -- Porter21 (talk) 16:10, May 24, 2011 (UTC)
 * Good to know, and it explains why I've had one user experience the bug on a Windows system. Uberfuzzy's reply leaves me wondering why it works for you in Monobook though (if it is a core MediaWiki bug). Oh well...
 * Regarding your question, wgAction by itself doesn't do anything. It is merely one of the variables which are checked by the script before it executes (to make sure it only executes on talk pages etc). Basically, since the variable contains a wrong value for you, the whole script doesn't progress beyond being loaded.
 * I think the following code should help fix your problem. What it does is that it corrects the value of wgAction based on the URL of the page you're viewing. Simply add this to wikia:community:Special:MyPage/global.js:

 /* Workaround for incorrect values of wgAction */ if (skin == "oasis" || skin == "wikia") { var locParam = location.href.substr(location.href.indexOf("action=")+7).split("&");

wgAction = (location.href.indexOf("action=") == -1) ? "view" : locParam[0]; }
 * Keep in mind that it usually takes a while until updates to global.js are applied as it is heavily cached. Hope it works :) -- Porter21 (talk) 07:03, May 25, 2011 (UTC)


 * Forgot to mention it this morning, but it's possible that you'll experience a "collision" issue for the page control dropdown on user talk pages when using scripts which add options to it. This is due to another bug with the Wikia skin which I reported months ago; the z-index of that button is too low, hence the user page container appears above it and you can't click on the lower options. There's a fix for it at the bottom of our MediaWiki:Wikia.css. -- Porter21 (talk) 14:48, May 25, 2011 (UTC)


 * Yeah, the cache should have been updated by tomorrow. I'll keep my fingers crossed ;) -- Porter21 (talk) 18:07, May 25, 2011 (UTC)


 * Glad it works :) I'll try to remember posting the fix over at community (I guess people would more likely notice it there than at dev). -- Porter21 (talk) 02:01, June 9, 2011 (UTC)

ArchiveTool. Yes, again . ..
I've made a change to the code on w:c:dev which should hopefully fix the issues. Unfortunately I won't be around long enough to check whether it actually works (busy time for me currently), so please let me know if it doesn't work. -- Porter21 (talk) 21:05, September 5, 2011 (UTC)
 * My bad - I overlooked that there had been a change in the structure of the page control button as well. I've fixed that (and tested it), so it should be fine now. It's better to check for the presence of the masthead than simply doing a namespace check (because of subpages etc). -- Porter21 (talk) 07:11, September 6, 2011 (UTC)