User talk:Cade Calrayn

 Find archived discussions here: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10

Portable infoboxes: the return!
Hey Cade! Hope you've been well since Community Connect!

Just wanted to hit you up about portable infoboxes. It looks like most of the discussion and development here at Wook happened before CC, so I just wanted to see what we could do to restart the conversation and production.

I think you ran into a few questions back in the summer that may never have been answered, but I wondered if you could restate the problems you believe still exist, in case conditions have changed for you since August.

Ideally, we'd like top work with you to finish the work of conversion in the next few weeks, so you should know you have the total attention of the engineering staff. I'll be running point on communication, so please gimme whatever questions you have, and I'll get answers back to you in a jiffy. I think you probably have one of my cards from Community Connect, so do feel free to email me directly, if you'd find that more convenient. Thanks! 21:03: Tue 10 Nov 2015
 * Sorry, I've had a busy week; I'll take a look today. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  16:01, November 17, 2015 (UTC)
 * No worries; we all have those :) Let me know if there's anything I can do to help speed the process.  16:05: Tue 17 Nov 2015


 * So, I've taken a look and with my addition of a footer, there's only two issues really still there:
 * There's no way to reproduce the functionality of the imageBG parameter, which lets us put a background behind images that are partially transparent or not large enough (see Category:ImageBG). I'm checking on how widespread/if the width parameter is still used.
 * Our Imagewidth template is unusable with the portable infoboxes, and the image quality improvement from its resizing is lost. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  21:35, November 18, 2015 (UTC)
 * Thanks, man :) Lemme look into these issues and I'll be back with questions, solutions, or maybe even both :) 21:42: Wed 18 Nov 2015
 * I can tell you immediately that the general way in which infobox images are handled in PIs with respect to your first point is to simply add code to the CSS which does a max-width of 100% (to stop super wide images from escaping the infobox boundaries) and then to do a height of 100%. In other words, it automates the width-setting process in a way that doesn't change the aspect ratio of the image, and therefore obviates the need for individually setting widths.  It also would eliminate the need to find a background. The images that typically would be most dis-served by this process would be ones that are less than 100px wide.  Do you have such small images being used in infoboxes here?  21:47: Wed 18 Nov 2015
 * Yeah, the imageBG parameter's only used when an image is less than 250px wide, which is the standard (and maximum) width of the vast majority of our infoboxes. A lot of WEG and comic images are like this, and it's not always a white or black background. Corinna A'Daasha, Kandria A'Daasha, Akanseh, and Alph are a few examples from Category:imageBG (though it seems there a few unnecessary uses in there). There's also instances where parts of the image is transparent, like Adelhard, Tani Ab'yla, and AccuTronics. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  21:58, November 18, 2015 (UTC)
 * Okay, thanks for that greater detail. Another question, is imagewidth actually working? I've tried several different infoboxes, and no matter how wide or narrow I set my browser width, the image width stays the same. As always, forgive me for asking dumb questions, but I'm just trying to quickly come up to speed here. :)  22:08: Wed 18 Nov 2015
 * It won't be affected by your browser width; all infoboxes images are loaded at 250px regardless. What it does is load the image itself at a larger size than 250px wide (not too large, and scaled to the actual size of the image) and then has the infobox's CSS automatically resize it to 250px wide, thus maintaining the quality that you'd have at the larger size. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  22:11, November 18, 2015 (UTC)
 * Do you have maybe an example or two infobox images where imagewidth kicks in? Or does this happen to every infobox image?   22:26: Wed 18 Nov 2015
 * Everywhere, yeah. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  22:28, November 18, 2015 (UTC)
 * You may remember Shareif from Community Connect. He and I have been examining imagewidth for the past little while and I'm not sure we're properly understanding it. In the last few minutes I've built a little demo of it at User:CzechOut/ImageTest, where I've put a standard whatever call directly on top of an infobox-processed version of the same image.  Presumably, because the image is within character, it must be flowing through imagewidth as well.  But I can't see any difference between the two sets of images.  Am I misunderstanding something?


 * I'm not asking to challenge or dispute you, by the way. Rather, Shareif is so intrigued by the notion that there might be a trick he's missing in improving infobox image quality, that we might want to build your code, or something very like it, into the basic infobox code itself.  So the more we can understand about what's going on, the more likely it is that we can just make "Wookieepedia standard image handling" into "Wikia standard image handling".


 * If you have a better example of where image quality is definitely enhanced over Wikia's/MediaWiki's standard file calls, we'd be very much interested to see it. 23:40: Wed 18 Nov 2015
 * Hey Cade! :) Shareif and I are still very interested in what imagewidth is actually doing under the hood, but so far have only been able to see that it's increasing page load time. If you could give us a clearer example of where it's making a big difference as to image quality, we'd love to see it, as we'd love to improve infobox image quality for all of Wikia, if possible. Thanks! 20:20: Mon 23 Nov 2015
 * To be honest, I'm no longer actually able to see a difference between the two. I remember it being visible at one point, but I'm not really seeing it anymore. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  00:06, November 24, 2015 (UTC)
 * So, just to confirm, imagewidth is no longer a concern for you? And you spoke before of checking on how widespread the imageBG parameter actually is.  Were you able to get an assessment of how significant that usage was so that we can determine how much of a blocker it really is?   22:35: Mon 30 Nov 2015
 * Yeah, I don't think Imagewidth is a dealbreaker. However, ImageBG is widely used; I've gone through some more of Category:ImageBG, but it seems like there's at least several hundred, if not around a thousand, cases where the parameter is definitely in use and is needed. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  16:56, December 1, 2015 (UTC)

Infobox
Thanks for the heads up about the hide button; I was kinda scratching my head over that one. Well, this example infobox is almost ready to debut at User:CzechOut/Ship. Coupla questions for you:
 * 1) I need to alter some of the CSS.  I put my changes in MediaWiki:Infoboxes.css and was just going to add a little @import line over at Common, while also redacting the PI code at the bottom of Common.  My thought was this would keep all the tedious interstitial editing out of Common's history.  Does that seem like a reasonable plan of action to you?
 * 2) *Go ahead.
 * 3) I understand from Brandon that you guys need, as a matter of course, a week's debate on the sample infobox before we get underway with more full-scale conversion. How would you like to handle that debate period? Do you want to introduce the designs for approval, or should I do it?  Or would you like to pass it around more informally in the Wookieepedia IRC channel?   03:12: Tue 08 Dec 2015
 * 4) *The general IRC consensus is that no, this wouldn't need a CT; it's a behind-the-scenes change with minimal visual changes, just like the previous template rework when I converted them to metatemplates. One minute though, we're still discussing it. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  03:24, December 8, 2015 (UTC)
 * Cool. Just remember that the CSS in Infoboxes.css will square the circle on a lot of the differences between the non-PI and the PI.  I can implement those now, if it'd help the debate.   03:28: Tue 08 Dec 2015
 * Actually, now that we look at it, your ship example page definitely shows a difference in the image quality, and that was a sticking point for a few people when the quality changes first came about. Also, some other issues: the image on the portable infobox links to the actual image and not the File: page, which is a significant issue for us, and it'd be nice if the row label text could be centered vertically. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  03:35, December 8, 2015 (UTC)
 * Thanks for the feedback!
 * The labels are now centered vertically.
 * The bottom of the box now has a bottom border radius
 * I'm not too sure what you mean about linking to the image rather than the file page. Whether at Millennium Falcon or either box at User:CzechOut/Ship, the infobox image seems to do the same thing: bring up a light box and show the image. Could you please define a little more what behaviour you'd like to have happen?
 * I'm still not able to see a difference between the PI image and the non-PI image. Could you maybe provide screenshots which demonstrate the lack of quality in the PI image?


 * Sorry if these last two points seem tedious to you, but I wanna get it right for you, and I just can't see what's actually wrong.  05:19: Tue 08 Dec 2015
 * For one thing, the portable infobox image is loading at 270px wide and isn't being resized at all, so it's leaking over the edge. Here is a comparison of the two at their proper dimensions; I'd upload it but it seems there's something up with our abusefilter. As for the other image thing, it's in Monobook&mdash;clicking on the image should lead you to the File: page and not here. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  14:47, December 8, 2015 (UTC)
 * You should find the "leaking-over-the-edge" phenomenon to now be fixed. (You may have to ?action=purge the URL to see the changes.)  Is that all that you were meaning — an image dimension issue — or was there some other image quality metric that was troubling?
 * As for the Monobook thing, I'll take a look. Thanks for defining that better! 15:42: Tue 08 Dec 2015
 * Thanks to Grunny's quick help, the Monobook issue you described has been fixed. As always, you may need to ?action=purge your URL to see the change working. Were there any other outstanding issue that you and the gang have? I'm at your disposal to fix things (or ask more and smarter people to help), so please don't be shy about making requests! 16:21: Tue 08 Dec 2015
 * Hey, I've checked more on the imageBG issue youy described earlier, now that we have a more or less working prototype infobox. Turns out that a significant number of the things in category:imageBG are sort of false positives. It took me around 50 random clicks before I found one that failed to extend to the limits of the infobox, and therefore showed the background.


 * However, there are indeed still some images where the background shows up. One thing we can do in the very short term is to change the default background to white, which would eliminate even more things as false positives.


 * Then I can work with our engineers to see if there's something we can do to accommodate switching the background for that fraction of category:imageBG that really needs it. In other words, I suggest we continue to look for a fix for this issue, but not let it block deployment of PIs, since it affects relatively few pages. Does that seem reasonable?  02:50: Wed 09 Dec 2015

Infobox image quality
I think that we've managed to fix most of the problems you mentioned above, but I've looked again at User:CzechOut/Ship I finally figured out that the image resolution of the PI was crapping out when you zoomed in with your browser. The non-PI doesn't do this.

But the thing is, when viewing the infobox at the normal resolution, you'd be very hard-pressed to tell, particularly because the natural width of the PI is smaller than the non-PI. And not all pictures demonstrate this flaw as prominently as the Falcon. As you noted it with the images at User:CzechOut/ImageTest, you can't see the difference, no matter what the zoom level.

We've entered a period now where engineers are scarce as we wind down into the holidays. So I guess the question I have for you now is just how much of a problem this is for you guys? Is it going to prevent us from deploying the new PIs in time for The Force Awakens? 21:49: Thu 10 Dec 2015
 * Chiming in here to reinforce Shawn's point very directly: given the fact that this only happens when you zoom in, I can count on one hand the amount of people who this would actually impact. So considering the benefits far outweigh this very minor issue, let's not consider this an actual blocker. Let's move ahead with the portable infobox conversion, with the understanding that, after the holiday, engineering will be able to look into and address this problem one way or another. - Brandon Rhea (talk) 22:45, December 10, 2015 (UTC)
 * Overnight, a gang of not-yet-holidaying engineers took a good, hard look at the portable infobox image quality issue. They have formulated a response that will improve image quality globally. It's based on your imagewidth solution, following your logic of increasing the width/resolution of the image from which the PI image is derived.


 * This plan is in code review now and will be deployed on Monday.


 * I've been getting updates all day on it, and I have absolutely no doubt that you're going to see satisfactory results Monday. It will completely obviate the need to continue using imagewidth, and, indeed, spread the logic of your template to the whole of Wikia.


 * Would it therefore be okay if we started doing infobox conversions this weekend, and allow the code that improves the images to go live ever-so-slightly after conversions have begun in earnest? 20:20: Fri 11 Dec 2015
 * Honestly, I've been super busy this week with the final week of school and the bot work, so all my little free time has been put towards managing the bots. I'll be able to catch up on these messages tomorrow morning; thanks again for your patience and work. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  20:22, December 11, 2015 (UTC)
 * Hey, hey :) Looks like you had quite the productive weekend round here. The Legends/Canon switch seems to have gone well. With that and school, I can totally understand why you didn't have enough time to get back to me on infoboxes.  Still, I'd really like to get this wrapped up by Wednesday, so that all those people who are going to start flooding the site after Thursday night's showings of EpVII will be able to look on their phones (maybe even from the theatre lines!) and get the best possible viewing experience.


 * Towards that end, I've started dumping all the portable infoboxes I've created locally on my machine to /Draft pages here. You should know that we're still on track for a push, later today (or maaaaayyyyybeeeee tomorrow) to fix the imagewidth issue, and I think we've taken care of the vast majority of your objections.  Do you think it'd be okay to start approving these drafts?  17:19: Mon 14 Dec 2015
 * Give me three hours or so, I've got an exam in an hour, and then I'm clear to take a look. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  19:04, December 14, 2015 (UTC)
 * Okay, now that I've resolved the variety of technological issues that just happened to pop up in the last six hours, I've got one outstanding issue with the infoboxes; namely the imageBG field. Was this ever implemented? Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  01:25, December 15, 2015 (UTC)
 * Hey Cade! Thanks so much for beginning to approve these /Drafts. You should know, if you haven't already noticed already, that there is some lag between when a /Draft is posted and when you can actually see the button to "see the draft" in Special:Insights. So you kinda have to just keep adding /Draft to URLs to figure out whether there's a /Draft there or not. Also, some of the template classification is a bit tricky.  For instance, with Information, even though it's in an infobox category, it's actually "non-article" because it's only/principally used outside ns:0.   01:27: Tue 15 Dec 2015
 * What about the imageBG parameter? Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  01:37, December 15, 2015 (UTC)
 * Sorry; we had an edit conflict. No, imageBG has not been addressed. As I pointed out earlier, it's something that affects only some of the ~1000 pages in category:ImageBG. There are:
 * many straight up false positives in that list
 * many others which have a white/transparent background, and so don't actually reveal any problems
 * some which were a problem in the non-PIs, but are no longer a problem since PIs are narrower
 * I roughly estimate the number of pages with a genuine background problem at ~.05% of your total pages. Since it's such a small number, I was hoping we could work on that after Christmas. IF I have a misapprehension about the size of the problem, please let me know and I'll see what I can do about reprioritising it. 01:40: Tue 15 Dec 2015
 * No problem, makes sense. I've got some serious back pain right now, so I'll be back in a bit. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  01:52, December 15, 2015 (UTC)
 * Oh, one thing we do need to keep is the ParamCheck stuff from the bottom of the original versions; those are used for maintenance categories. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  01:59, December 15, 2015 (UTC)
 * Heya :) I'm sorry to hear you're having back pain. I know how badly that sucks, so I don't want to overtax you. I've been trying to release a few new infoboxes every few hours, so as to minimise the time you had to spend at the computer doing approvals.  I'm not sure that it worked, but that was my intent. I'm stopping for the evening now, so that should give you a definite break until morning.


 * Since you've already approved the basic style that all these take, we could just have Grunny finish up the initial approvals tomorrow, and then when you're feeling better, you and I can jointly go over any problems you detect in individual infoboxes. Or not. :) Whatever is easier for you to do. :)


 * If you can get to some approvals, there are a few that are super high priority.


 * Obviously, we'd like to get Character done, since it's the infobox on the most number of pages. Shareif has had this working for several months now, and I recently made a few tweaks to bring the styling to the same standard as the rest of the infoboxes. You can play around with the  variable in the example at Character/Draft to discover how readily the colors change.


 * Other high-priority targets include Movie, Television episode, and any of the templates that are on more than 2000 pages.


 * Finally, I didn't see your request about ParamCheck stuff until a little while ago, after I'd uploaded several dozen more infoboxes. I'm a little confused about the ParamCheck code, since I only ran across it a few times. On a few occasions, it was delivered via parser functions; on others, by a Lua invocation.  But by and large it was just absent, so those few times I came across it, I thought it was just experimental code and so didn't include it in the PI. Since it appears so inconsistently, emme ask you a couple of questions:
 * Is it supposed to be on every infobox template, and people just never finished the job of adding it?
 * If so, would you like to take this opportunity to just put it on every template? Or should I only put it back where it was?
 * Do you prefer the Lua version or the parser function? (Personally, I think that since you've got the Lua code running well, it probably makes most sense to use that.)


 * Again, sorry for making a wrong assumption, but we'll get it cleared up soon enough. :) 09:15: Tue 15 Dec 2015

Infobox approvals
It's probably time to start a new section, since we're not really talking about infobox image quality anymore.

As you may have discovered Special:Insights is somewhat slow to update, so I'm gonna try to keep you apprised of my uploads here. That way, you don't have to go hunting through the whole list, like I think you did when you started approving yesterday.

I'm now trying to release infoboxes in groups of 5-10, along categorical lines, so it's easier for you to study them as a group of related infoboxes. I've just finished uploading the entirety of spacecraft infobox templates and category:Vehicle infobox templates.

Still, the infobox that needs approving — really, ASAP today — is character. By far, the thing that most casual fans are going to want from their phones as they descend upon theatres this weekend is information about the characters from EpVII, so it's vital we get that going just as soon as you possibly can.

Thank you so much for all the work you've put in to improve Wookieepedia over the past coupla weeks. We're almost at the finish line where we can all relax into just being fans again. 20:48: Tue 15 Dec 2015
 * Thanks, I would've started again earlier today but I've been moving apartments. I was actually just going through your contribs, as like you said Special:Insights isn't the most up to date. I looked at Character last night, but it was an unfinished version (which appears to have been updated). I do have one issue&mdash;our Category:Event infobox templates actually have a width of 300px instead of the standard 250px, and I wasn't sure how/was too tired to figure out how to apply that to the portable versions. Any ideas? (also, it looks like they no longer do three/four columns across, but that was always a bit of a hack via an infobox within an infobox or something.) Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  23:22, December 15, 2015 (UTC)
 * Also, now that I've popped back into IRC, it's been pointed out to me that images aren't loading at the 250px max; see Xexto for example&mdash;it's loading at 240.918px instead, and thus we've got borders. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  23:28, December 15, 2015 (UTC)


 * Lemme answer those questions in just a second. Just wanted to say Category:Media infoboxes (though perhaps not the subcats) is ready for your perusal as well.  23:52: Tue 15 Dec 2015


 * Okay, sorry for the delay. Infobox widths are easily manipulated, but I wanna make sure I understand what you want. Are you saying that character, and character alone is supposed to be 300px, while the rest are at 250px?
 * No, just Battle and the rest of the infoboxes in Category:Event infobox templates; I forgot the colon to force a link above.


 * PIs absolutely can do four columns across, but since I couldn't find a natural 4-party war, I was thinking that was a pretty edge case that could wait on development until after this weekend. I think I'm right in saying that, far and away, the most natural form of the multi-party infobox is just the straight-up twofer, which these boxes I think do better than the originals.  Nevertheless, there are a number of pathways to traverse with the >2 boxes, but it would be really helpful having several examples of a 3-party and 4-party conflict to experiment on.
 * Galactic War would be a 4-party war, though you're right, it's relatively rare. 3-party wars are more common. As long as it's still on the table for later, sure.


 * Finally, Xexto is very much an edge case, because the image is naturally very tall, and therefore to get a proportional version of the image, whilst at the same time sampling from an oversized image, the image does take up slightly less than 250px. These cases are extremely rare, but thanks for pointing it out.  I can pass it up to the engineering team for further analysis. At least until January, when the engineering team are fully back at their desks, the basic rule of thumb is that if the height/width > 2, you'll probably see that the image won't fully extend the 250px width allotted to the infobox image. file:Gasgano.jpg has a h:w ratio of 2.07.  00:09: Wed 16 Dec 2015
 * Hmm, okay. To be fair, we've generally had a (unofficial?) policy about very tall images, so we'll see how widespread it is. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  00:23, December 16, 2015 (UTC)
 * The case of Xexto has indeed been pushed up the food chain, and is now well-ticketed with the engineering staff. I wouldn't expect many further such cases. Obviously, an easy solution for this one is just to resample the image so that it's (proportionally) just a little (like 20, 30px) wider. Again, as this image demonstrates, the magic number is a 2:1 height:width ratio.  Anything below that is fine; anything above, and you'll likely see images not stretching full width (for now).    00:31: Wed 16 Dec 2015
 * Okay, you should find Battle/Draft (and the other templates that use the Battle and Event themes, after purging your browser's cache, are now 300px widths. 01:00: Wed 16 Dec 2015
 * I didn't much like leaving you, even for very long, a whole class of infobox that unclearly presented its information. So one possible solution to the Battle multi-party issue is simply to make the thing wider whether you've got 2, 3 or 4 parties. I've now changed the width to 400px for the "Battle" theme, and given you a side-by-side look at the Battle page. I've also given you 300 and 350px widths for comparison there on the Battle page. Lemme know which one you think is the best! 23:22: Wed 16 Dec 2015

Rest of the infoboxes
All the rest of the infoboxes are ready for your approval. As we know, Special:Insights is displaying more templates than that are actually infoboxes. But if you again use my contributions list — or better this list, you should be able to knock them out pretty easily. Obviously, even though the remaining unapproved templates are the "stragglers", the earlier in the day you can approve, the better. Might help us reach a few more people standing in line for Thursday's showings.

Though I will remain available to you for further refinements of the infoboxes as we've already discussed, I did just wanna pause for a moment prior to TFA's official launch and thank you for your cooperation with the infobox project. I know you've had a lot of stuff going on in other areas of your life, but you've been a Wikia Super Star with all this. Thank you so much! 09:17: Thu 17 Dec 2015 09:17, December 17, 2015 (UTC)
 * Okay, we've got some issues with images:
 * As you can see here, captions aren't supported by the infoboxes, and it's dropping the image as well, resulting in a lot of hits in Special:UnusedFiles.
 * A lowercase f on the file is also causing the image to be dropped, as is any type of misspelling in File. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  02:52, December 20, 2015 (UTC)
 * Has there been any further discussion about the size of the conflict/event infoboxes too? They are way too big, and it'd be good if we could get that resolved. If you haven't checked in the Wikia skin, Cade, please do so and you'll see what I mean. - Brandon Rhea (talk) 23:43, December 21, 2015 (UTC)

Hologram template
Hey Cade. I'm not sure how much work this will take, but is there any way you could change the hologram template so that instead of having to put for canon pages you could just type , and for Legends pages you would put  ? I changed the template myself however I realized that all the Legends pages would just link to the canon hologram page, so I changed it back. Is there anyway you could change this and all the Legends pages that link to the canon hologram page? If you can get it working fine for that template, could you do the same thing with the holocron template? Thanks. Cevan   (talk)  22:48, December 18, 2015 (UTC)

Questions about Battle
Hey Cade. I'm not sure how familiar you are with the revamp of Battle a couple weeks back, but I figured you'd be the best person to ask. There are two errors with the template that I can't seem to bypass. The first is the fact that for two or more "sides" for the battle, if just one field is blank in the MediaWiki code, it is omitted when the page displays the template. An example is the battle of Haruun Kal: "casual2" is left blank, but instead of that field appearing as a blank field on the page, the data from the "casual1" field completely covers that row. The second error I ran into is that bullet indents don't appear to work within a field, i.e. the "forces1" field on bombing at the Jedi Temple. If you know of any workarounds to either of these errors, could you let me know? Thanks!  CC7567  (talk) 02:13, January 5, 2016 (UTC)
 * Hey Cade, just wanted to follow up with you regarding this and see if you might know what's up. If not, no worries. Thanks.  CC7567  (talk) 21:54, January 29, 2016 (UTC)
 * I also have a GA nomination that is being held up as a result of this, so getting a fix would be appreciated&mdash;especially since the nomination is being held up for something outside of my control. - Brandon Rhea (talk) 23:24, January 29, 2016 (UTC)
 * I've informed CzechOut as to the issues; I'm not seeing any way for me to personally fix the issues except for the bullet point ones&mdash;it's the fact that the rows are set to centered-text alignment. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  14:43, February 1, 2016 (UTC)

Falleen
Hey Cade. In accordance with the naming policy, I've moved what used to be Falleen over to Falleen (species), and done the same for the Legends page. The planet pages still have to be moved, however could you possibly have RoboCade switch all links to "Falleen" to "Faleen (species)|Faleen"? Same goes for the Legends counterpart. I'd really appreciate it. Thanks. Cevan   (talk)  15:53, January 18, 2016 (UTC)
 * Actually, Falleen is explicitly defined as one of the exceptions to the policy, along with Gand. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  15:57, January 18, 2016 (UTC)
 * Gah, my mistake. Sorry about that. Cevan  IMPpress.svg  (talk)  16:29, January 18, 2016 (UTC)

Hair dye
Hi! I'm trying to make a canon article for hair dye. I moved the legends article to "hair dye/Legends", but when I try to create a new, canon hair dye page, it does not work - when I click "save page". nothing happens, because a page with that name, already exists (the legends page). Can you help me? --Nightlily (talk) 22:00, January 18, 2016 (UTC)
 * Edit: Never mind; I figured it out; it was due to a redirect.

Hi Cade.
I was just wondering, in your opinion what would be some of the most powerful crystals to use of construction of a lightsaber to ever exist. 110.148.164.133 07:47, January 19, 2016 (UTC)

http://starwars.wikia.com/wiki/Richard_Madenfort

Of course, 'anon' deleted the verify tag. The tag said to add sources. 'Anon' added sources. Therefore 'anon' deleted the tag. The tag did not say not to delete the tag, it said add sources. Sources were added. If it wasn't a proper source, why not put the tag back up so that 'anon' would know it was not enough and would continue to add more sources.

--98.235.110.31 20:13, January 19, 2016 (UTC)
 * I'm looking at the exact text that was deleted, and there was no sources. You simply added an unnecessary reference for the actor's stage name, not for the statement that he appeared in the movie. We're not the Buffyverse or Taylor Swift wikis; we have standards. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  20:54, January 19, 2016 (UTC)
 * again, if it wasn't a proper source, why not put the verify tag back on instead of simply deleting the page. --98.235.110.31 22:02, January 19, 2016 (UTC)

Mandalorian Neo-Crusaders/Legends
Hey Cade; sorry to bother you, but when you have some time do you think you could have RoboCade move Mandalorian Neo-Crusaders to Mandalorian Neo-Crusaders/Legends, and update all the links to the page? I noticed just a short while ago that all of the The Clone Wars episode guides from seasons one to three or four have been updated with trivia galleries (they were lacking these back when StarWars.com was updated). The trivia gallery for "Wookiee Hunt" lists off many of the trophies in the Trandoshan hunting lodge, including the Mandalorian Neo-Crusader helmet. I've already got a canon version of the page typed up and ready to paste in once the switch has been made. I was going to switch all the links over and move the page myself, but there are just far too many to do it manually. I'd really appreciate it if you could do this whenever you're able to. Thanks! Cevan   (talk)  02:24, January 22, 2016 (UTC)
 * Should we actually treat that as a canonical fact, though? The fact that it appears in a trivia gallery, rather than the episode gallery, suggests to me that it could just be saying it's a reference. Saying Neo-Crusaders are canon seems speculative. - Brandon Rhea (talk) 18:06, January 22, 2016 (UTC)

Blue Squadron (Rebel Alliance)
There is a page called Blue Squadron (Rebel Alliance)/Canon. I'm guessing it should be moved to Blue Squadron.--Nostalgia of Iran (talk) 17:43, January 22, 2016 (UTC)

Shouldn't Blue Squadron (Rebel Alliance)/Canon be moved to Blue Squadron given the Legends to Canon switchover?--Nostalgia of Iran (talk) 00:33, January 27, 2016 (UTC)

Busy?--Nostalgia of Iran (talk) 15:50, January 28, 2016 (UTC)

Moving Military (Republic) to Republic military
It appears I do not have permission to do this since the page already exists as a redirect for the Legends Republic Military article. I'm not sure why I named the former article that in the first place (mistake on my part) but it appears it wouldn't have worked either way. The warning told me to contact an administrator. Will you help me out with this? Thank you! Reddyredcp (talk) 18:00, January 23, 2016 (UTC)

Using Ansel Hsiao's pictures
You recently said that Ansel Hsiao's pictures are only canon if they come from actual sources. Does this mean that they have to have been used in a book? I have seen other users put his pictures on the wiki with the only source being the fractal sponge website. Johnnyrocket64 (talk) 18:14, January 23, 2016 (UTC)

Merchant
Hey Cade, could RoboCade move Merchant and all links to it to Merchant/Legends? Thanks! -  AV-6R7  Crew Pit 01:11, January 25, 2016 (UTC)

Wat Tambor's Voice Actor Episode II
Hi Cade Calrayn, I've posted a source where Matthew Wood talks about Wat Tambor and mentions that Burtt provided the voice. It's on Tambor's talk page on the Legends section.--Jade Cooper (talk) 18:01, January 26, 2016 (UTC)

Images of Sith Empire spacecraft
Hi Cade! Could you please move/rename Category:Images of Sith Empire spacecraft to something more appropriate so that that category can be used for images of the original Sith Empire spacecraft? Thanks!  Imperators II (Talk) 15:53, January 28, 2016 (UTC)

Sorry to bother, How did you added a "Canon image" on a Template Tab?. Just wanted to know.

Thrawn links
Hey Cade, when you have a moment, could you have RoboCade change all links to "Thrawn" to "Mitth'raw'nuruodo|Thrawn"? I had started to do it manually but many of them are on talk pages, and there are a great many of them. Thanks. Cevan   (talk)  23:22, January 29, 2016 (UTC)
 * Hi there again, Cade. Really sorry to add yet another thing I'd like you to do when you have the time, however I noticed that all links to Minister were not updated in the canon switchover; the Legends and canon pages for it were renamed, however all pages linking to them were not. Thanks again, I really appreciate it. Cevan  IMPpress.svg  (talk)  20:02, January 30, 2016 (UTC)
 * First I'm going to need to know why for the Thrawn thing. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  14:04, February 1, 2016 (UTC)
 * Nevermind about the Thrawn thing, actually. At the time I posted that I was in a bit of a frenzy fixing several redirect links, and that one caught my eye as another offender; you don't have to worry about it, though. I would appreciate it if the canon and Legends Minister links could be fixed, however. Thanks Cade. Cevan  IMPpress.svg  (talk)  01:31, February 4, 2016 (UTC)

Chad
Where exactly is Chad mentioned in Star Wars: The Force Awakens: The Visual Dictionary? -  AV-6R7  Crew Pit 21:02, January 31, 2016 (UTC)

SWTOR NPC Images
Hi Cade. I see you do a lot of work on SWTOR articles, so I figured I'd ask you. This isn't really what I devote most my time to on this wiki, but I do have some SWTOR images, and contribute those when I can. I was wondering if there any policy regarding using NPC images from Jedipedia. For example, Kaldeni was removed from SWTOR, so it's likely difficult to find a screenshot of her. Would it be permissible to use an image of her 3D model from the Jedipedia site, as seen here? StarsiderSWG (talk) 20:32, February 1, 2016 (UTC)
 * I've got it covered; I haven't uploaded the images yet because I wanted to take the time to rewrite those one-sentence articles that Mauser crapped out, and I've been busy lately. At the moment, I've only missed.... 11? characters that were removed since launch. Cade  StupidRepublicEmblem-Traced-TORkit.svg  Calrayn  20:36, February 1, 2016 (UTC)
 * Cool, good to see someone is taking care of all those screenshots. StarsiderSWG (talk) 21:02, February 1, 2016 (UTC)

Mining droid
Hey Cade, I moved Mining droid to Mining droid/Legends. Could RoboCade move all the links to the Legends page? Thanks! Cwedin (talk) 23:35, February 1, 2016 (UTC)

Infobox help
I created a game infobox, but it lacks color and is unreadable. Can this be corrected? Cwedin (talk) 21:59, February 2, 2016 (UTC)
 * Thanks for the help! Cwedin (talk) 03:00, February 3, 2016 (UTC)

This may be an ultra-newbie-ish question, with an obvious answer I can't see, but why did RoboCade delete my edit on the Aayle Secura article? 68.32.245.158 23:16, February 3, 2016 (UTC)