User talk:Cqm

Heads up
I patched that bug that was breaking  and pushed it out as v0.2.1. It's additionally now possible to completely blank pages, because it wasn't before, by giving an empty string as the wikitext eg. .  and   are also now back in, because I accidentally left them out of v0.2.0 because I'm a silly person. Anyway, 0.2.1 is already being loaded on the wiki, so it's all perfectly usable. If you need assistance with implementing something with it, you know where to find me (my talk page). Also, while I'm still doing documentation, look at the  object in your console to see if certain functionality exists rather than just going off that obscenely incomplete list on the wiki. 11:45, June 2, 2013 (UTC)
 * Also, if you want to work with the unminified version, you can just copy-paste this into your console and run it, because Tundra doesn't have a catch to see if it's already loaded. 11:49, June 2, 2013 (UTC)
 * I am actually terrible. Thank you for finding that, sir. I already pushed that patch out and it's already being loaded on the wiki. Two things though. Firstly, you see that object that gets logged out to the console with error messages? You can use a  callback to respond to errors with the data in that object, like this:


 * The  is exactly the same as the object that gets logged out. Since moving a page throws an error if the page you're moving doesn't exist, you don't have to pre-check if the page exists, you can just do something like this (incorporating your code here):


 * Second thing, in case the readme didn't make it clear, Tundra is supposed to be used like this:


 * Tundra does begin to load as soon as the import statement runs, but it's asynchronous, and in the short span of time of the page loading, it might not be finished loading yet by the time your script runs. Using  makes sure it is. Keep in mind that it's also asynchronous, and the function you give it won't necessarily be run at the same time as the code around it (it might be if it's already loaded, but please don't rely on it). Perhaps you can do something like, putting the code that creates on the form on the page inside   so it's ready and functional as soon as it appears and to reduce timing conflicts inside your own code.  12:43, June 3, 2013 (UTC)

God letters talk
Sorry, forgot to thank you for notifying me ;) Greatly appreciated :3 18:51, June 8, 2013 (UTC)

Re: Chatlogs
I would just like to have all references to that name in search results etc removed for personal reasons. Hope you understand. :) Rankata28 (talk) 09:39, June 9, 2013 (UTC)

Hur
o.o 23:21, June 9, 2013 (UTC)
 * Yeys ^-^ 23:43, June 9, 2013 (UTC)
 * Yey it does ^-^ Good job & thanks. <3 01:56, June 10, 2013 (UTC)

hi
 CÅM  FIX YOUR JUNK you keep join/quitting in the chat. Please fix. Thanks. 06:26, June 10, 2013 (UTC)

I saw it
And now that I have some juicy [ blackmail], I am going to make you my bitch. 15:21, June 12, 2013 (UTC)

Desysop
Thanks for the explanation ;) Greatly appreciated 07:54, June 18, 2013 (UTC)

RE: Collapsible navboxes
Since the template is used alot, we can test out your changes in Template:Navbox2 first. 00:32, June 21, 2013 (UTC)
 * Can you change [Expand]/[Collapse] to [show]/[hide] (with s and h in small caps) per the earlier style? And please shift the v.d.e. links to the left by 5px, and the [show]/[hide] links to the right by 10px. 13:54, June 21, 2013 (UTC)
 * K, thx! 14:20, June 21, 2013 (UTC)

Re: pengLocations
I'll have a look at the updates. As for why I did some things a certain way, I kept as much of the previous code as possible and just added new functionality, rather than do a total re-write, even though the change was still extensive. -- 22:53, June 21, 2013 (UTC)

re:Conditionals for js
The Dropadd.js should load under the condition: (wgPageName.match('/Charm_log') && $('#charmguide').length) || (!wgPageName.match('/Charm_log') && $('.charmtable').length) The monstercalc.js needs this condition: $('span#XPEach').length || $('span#GEPrice').length || $('span#killXP').length That should work 13:54, June 22, 2013 (UTC)

Re: Your Bot and br-tags
I don't quite understand your response on this subject.

I'll note in advance (as Rich Farmbrough pointed out) that exchanging the standard-compliant format " " for the equally standard-compliant format "  " in either direction is a trivial computational load, so if wikia prefers the former format, there is no real harm in converting all the wiki source to the latter format, and then having wikia convert it back before serving up pages.

"In Chrome version 27, void tags, such as br, img and input, are not escaped. This is also true in version 21 of Firefox."

Odd. I also tried Chrome version 27 (on windows), Chrome 28 (on linux) and Firefox 21 (on both), as well as other browsers, and invariably saw wikia serving up pages with the self-closing format of the tag: " ".

"Apparently it is up to the browser how the page is rendered."

What does this mean? On the one hand, it is tautological&mdash;a browser is a piece of software which renders html pages. On the other, if the suggestion is that browsers tweak their "View Source" output rather than displaying the actual source received over the wire, I didn't see that. I observed wikia's http responses both before and after processing by the browser, and didn't see any case where the "View Source" pane differed from the packet capture.

A third interpretation would be that how wikia parses the wiki source to produce html depends on some browser-specific feature, such as the User-Agent header. Again, I saw no evidence of this with respect to the &lt;br&gt; tag. Note that to minimize the chance that I was "corrupting" a page with an older browser, so that my newer browser received a cached version rather than a freshly parsed version, I chose pages from the top of Special:Contributions/Cblair91Bot.

"the bot altering the tags is technically correct"

or rather, it is technically not incorrect. It is implementing an aesthetic choice between two valid options, not a technical fix. Qloque (talk) 12:07, June 23, 2013 (UTC)


 * Thanks, we're seeing the same thing, but using language differently.


 * wikisource &rarr;wikia&rarr; html source &rarr;internet&rarr;browser&rarr; DOMtree &rarr;rendering&rarr; browser window

" regardless of the formatting in the wiki source; while inspecting the parse tree generated by the browser shows a variety of results, depending on the browser and the inspector's preferred way of displaying a particular parse node. Qloque (talk) 22:42, June 23, 2013 (UTC)
 * So the html page source generated by wikia and delivered to the browser always contains break tags as "

Moving Exchange: pages
I see that you moved a few of the pages on Special:WantedPages atm to the right place. I was wondering whether moving Exchange-namespace pages requires special tools (because of the bots using them) or not - wouldn't want to ruin anything... 09:06, June 27, 2013 (UTC)

Re: Moving pages
Ow! I guess I shouldn't try fixing things if I can't do it properly. Won't ever happen again. Sorry! 10:25, June 27, 2013 (UTC)
 * Oh well. It's a much more complex process than I thought it is and I don't think I can move pages without breaking something, so next time I'll ask someone else to do it rather than attempting it myself. 10:41, June 27, 2013 (UTC)

Moving Pages
Hello, I saw you posted a message on Regis Dramen's talk page about moving pages. You probably noticed that I also attempted moving one of the teleport scrolls pages, it was me that saw they had changed in game and I asked Regis to show me how to move pages to change the names on wiki. I'm sorry we did not do it right and caused you more work. I still have some questions about your message, if you could answer them for me hopefully I can move pages correctly in future.


 * 1) If I check Special:WhatLinksHere how will I tell when there is a double redirect?
 * 2) If there is a double redirect how should I fix it?
 * 3) Does a wanted page also occur when a link on a moved page is broken or does it only occur for a broken exchange price? If its only for exchange prices that break what happens to other types of broken links in articles?
 * 4) How do you fix wanted pages?

Maybe if there is a guide on moving pages you can just point it out to me instead. Thanks 10:37, June 27, 2013 (UTC)


 * I think understand now, thanks alot :) 14:50, June 27, 2013 (UTC)

Hai
User talk:Fswe1. Have fun. 08:44, June 28, 2013 (UTC)
 * Talk:God Letters should be closed as consensus for option 2 per John Ayliff's statement, and, well, the consensus. Do we need a(nother) sysnub for that or can we just go ahead and get it over with? 17:27, June 30, 2013 (UTC)

RE: collapsible wikitable in userspace
do you know why the collapsible wikitables in userspace shows "Expand/Collapse" instead of "show/hide" (such as in User:AzBot)? 06:09, July 3, 2013 (UTC)

Collapsible
I think I like whatever scripts we had before for collapsible tables. As I remember it, the expanding and collapsing was rather smooth. With the mw- default ones, I can see each element being created/destroyed. It ain't pretty. 23:48, July 3, 2013 (UTC)
 * Okay, so I'll have to live with the ugly? FYI, I didn't literally mean it when I said destroyed, lol. 23:56, July 3, 2013 (UTC)