Wikia staff
  • I live in the janitor's closet at, but I often go on slumber parties all around the FANDOM network!
  • My occupation is Special Operations
  • I am part of the team that helps you promote your wikia — and make it look better. Click on "My Website" to put in your request, today!
  • Bio CzechOut has been at FANDOM since its earliest days. He likes comparing Irish whiskey with a good single malt, getting lost in a new city, and digging deep into the latest Apple® product.
  • [Show More]
Recommended LayoutYou are currently viewing Memory Alpha without recommended changes to the standard layout. To apply these changes, please click on the following Apply link - to just get rid of this notice, click on Reject. In either case, click Save on the page that follows.

Gral and Shran call a truce


Welcome to Memory Alpha, CzechOut! I've noticed that you've already made some contributions to our database – thank you! We all hope that you'll enjoy our activities here and decide to join our community.

If you'd like to learn more about working with the nuts and bolts of Memory Alpha, I have a few links that you might want to check out:

One other suggestion: if you're going to make comments on talk pages or make other sorts of comments, please be sure to sign them with four tildes (~~~~) to paste in your user name and the date/time of the comment.

If you have any questions, please feel free to post them in our Ten Forward community page. Thanks, and once again, welcome to Memory Alpha! --OuroborosCobra talk 05:32, 2 September 2007 (UTC)

Image Uploads

When uploading images, please make sure that you format them in the same way that other images have been formatted, with a license, proper citation, and a category. Thanks! -- Sulfur 02:58, 11 September 2007 (UTC)

Also, when uploading screenshots, could you please use the JPG format instead of PNG? PNG is useful for diagrams or drawings, but for all kinds of photography, JPG is the preferred format because it leads to smaller file sizes. Thanks. -- Cid Highwind 12:26, 11 September 2007 (UTC)

Lastly, ensure that you cite things in the proper format. Also, you don't need multiple categories. If you have (say for Spock) "Vulcans", you don't also need individuals and the top level image category. For example, see the changes I made to the image you just uploaded. -- Sulfur 00:35, 12 September 2007 (UTC)

Images to delete?

Regarding the following:
  • File:XindiSphereFires.jpg
  • File:ArcherPondersFuture.jpg
  • File:Enterprise departs spacedock.jpg
Got any plans for these orphaned images or shall we put them up for deletion? User:Gvsualan

All except

  • File:XindiSphereFires.jpg

will be used. Only after I uploaded all my pics for ENT: "The Expanse" did I notice that the synopsis wasn't actually finished. So within the next 48 hours, I'll be filling in bits from Act 3 and 4, which will allow for the use of the bulk of these images. Thanks for asking about them before deleting them unilaterally :):):) CzechOut | 13:14, 19 September 2007 (UTC)

Show preview

Hi, CzechOut. Just letting you know, when editing pages, even those you have marked as {{inuse}}, please use the "show preview" button as often as possible. Not only will you be able to view your edits before saving, you will lighten up the load on the database... and you will also avoid annoying other contributors by having constant edits to the same page appear on the recent changes. Using show preview allows you to check the changes you made without saving, thus allowing you to alter them/preview them repeatedly until you get it the way you like. Please remember this in the future. Thanks, and thank you for your contributions! :-) --From Andoria with Love 00:03, 14 September 2007 (UTC)

Disambig lks

Please note that Kirk does not go to the same place as James T. Kirk. When attempting to link to one, please do not link to the other, use a piped link in its place. -- Sulfur 13:30, 23 September 2007 (UTC)

Show preview, part deux

It is again asked that you please use the "show preview" as often as possible while editing. To reiterate what I said above, "Not only will you be able to view your edits before saving, you will lighten up the load on the database... and you will also avoid annoying other contributors by having constant edits to the same page appear on the recent changes. Using show preview allows you to check the changes you made without saving, thus allowing you to alter them/preview them repeatedly until you get it the way you like. Please remember this in the future." --From Andoria with Love 00:03, 14 September 2007 (UTC)

I followed this conversation over here from Shran's talk page and have a couple suggestions for your power outage issues. If you use an external editor that will allow you to save your changes locally and then upload to the server once, you will have the best of both worlds. Otherwise, you could use a simple text editor like Notepad and copy the entire text of an article and edit, then paste over top of the old article text when you're done. You can save locally that way, too. Possibility number three would be to invest in an UPS device that will power your computer for a minute or two as the power goes out, then you can quickly save your edit to notepad before it shuts down. --Topher 20:29, 24 September 2007 (UTC)
As long as you're using the save preview as often as possible, that's all we ask. If you have a legitimate reason for making so many edits, that's fine. That said, though, I would try one of the suggestions Topher offered above. Instead of editing in sections, I would edit the entire article at once (by clicking the "edit this page" tab at the top of the page) and copy, paste and save my progress to Microsoft Word or Notebook. If the power goes out, you'll have your changes saved in a Word document or Notebook file and can just copy and paste it back into the editing box on MA. (You have probably tried this or thought about this already, but just to be sure...) Also, I would suggest using Mozilla Firefox when editing MA. With Firefox, when the power goes out and after you reboot and restart Firefox, it will ask you if you want to restore your session. Click yes, and it should reload the editing page, complete with all the changes you made prior to the power outage. This isn't guaranteed, of course, but it's done it without fail for me in the few times I lost power or I accidentally closed my browser or something. Anyway, those are just some suggestions and if they don't help, then I wouldn't worry about it. But do look into those. ;) --From Andoria with Love 21:46, 24 September 2007 (UTC)


Whatever was wrong with the images should be fixed now. Try re-uploading your Tessa image. --From Andoria with Love 21:04, 29 September 2007 (UTC)

Sorry, meant to add this to Eyes Only's talk page. Oh, well, he found out, regardless. ;) Now, if you'll excuse me, I gotta go drop some more trees... :P --From Andoria with Love 21:22, 29 September 2007 (UTC)

Are we reaching? ;)

Hey, CzechOut. Just making sure you read the responses from Sulfur and myself regarding your show preview question. Let me or Sulfur know if you have any more problems. --From Andoria with Love 03:28, 8 October 2007 (UTC)


Koukám, že někdo tu mluví česky odkud jsi?? sleduji jak zde přispíváš.. :-) já pracuji na vlastních projektech.. se mužeš kouknout na mém profilu tady... petr

Speedy Deletes

Moved from now-deleted PfD...

Not sure what the hell I did, but somehow in trying to leave a message about the template itself, I created a subpage of the template talk page. Basically just administrative request; speedy deletion recommended. CzechOut | 22:05, 30 October 2007 (UTC)

Please note that it's best to use the Immediate Delete page for those, rather than creating these PfDs. -- Sulfur 23:21, 30 October 2007 (UTC)

Of Gods and Men

Hey, CzechOut. I did some investigating on that broken link for Star Trek: Of Gods and Men. Apparently, the site is temporarily down due to an abundance of traffic caused by their announcement of the impending release date. Kind of scary, huh? If the site goes down just because they announced something, imagine what will happen when they actually try to release the darn thing. - Bridge 20:12, 3 November 2007 (UTC)

Hello, again. The above is based on what I read at forums from one of their administrators or webmasters. Actually it's a little more detailed than I realized. Seems in conjunction with announcing the release date, they sent out a newsletter to a bunch of people who had registered for it and that caused the site breakdown. - Bridge 20:37, 3 November 2007 (UTC)

Temporal Cold War Story Arc

Thanks for helping get a few episodes in there. Although when I made the arc I did it with the intention of the main episods in the arc; such as those that directly involved Daniels or Silik (so as to avoid putting all of ENT Season 3 in there). -Lord Hyren 19:12, 14 November 2007 (UTC)

a tip to improve your editing

hi. i saw on your user-page that you like to get help on how to improve your editing. i took a look on your sandbox-page. there i noticed one thing. you could, instead of doing a normal link to an episode, use the episode-template. {{e|(episode name)}}. then it looks a little better, from my POV. When you hoover your marker on the link, you can see in what season+number the episode is/has. other templates it's good to use is the uss-template. The Enterprise-D will with that template look like this: {{USS|Enterprise|NCC-1701-D|-D}}.and last Shipclass-template.{{class|(classname)}}. I like templates, they are many times much faster to use than normal linking. --myÖrlogstalkkaptenpage 09:33, 19 November 2007 (UTC)


Hi, CzechOut. Could you please confirm, on this page, whether or not you find your objections to the prospect of the Gorkon article receiving FA status have been sufficiently resolved? --Defiant 20:55, October 19, 2011 (UTC)


Next time, before creating categories, you can bring it up for discussion, like it says to do in the policy. Since I wouldn't have supported a category for Medical databases, that has been deleted. - Archduk3 18:54, June 3, 2012 (UTC)

I honestly had no idea that simple category creation required committee approval. Thanks for pointing out the policy. I'll adhere to this in future. Unfortunately, that means I probably won't be spending any more time trying to improve the category tree. I simply have too many responsibilities elsewhere to monitor an approval page here for 7 days to see if the motion passed.
Still, if I can, I'd like to offer a few observations, as someone who has spent a lot of his time on Wikia organising category trees:
  • I think the whole policy is built on shaky ground. It's hardly a "labor-intensive process to remove or alter a category name once it exists", as the policy suggests. I've made tens of thousands of category moves at w:c:tardis, and there's nothing remotely difficult about it. In fact, it's probably the easiest part of pywikipedia usage. Sure, ordinary users might have a tedious time of it, but pywikipediabot scripts make a lie out of this entire policy. Since I learned how to use pywikipediabot from sulfur, I naturally assumed that you guys wouldn't really have a policy entirely based on just what an ordinary user can do with categories. And I mean, you've got experience with pywikipediabots too, don't you? Surely you don't believe that the policy is telling the truth. I'm not saying the policy should necessarily be abolished, but the rationale should at least be plausible, don't ya think? Heck, the policy says that "categories must be orphaned to be deleted", which is simply not true of the MediaWiki software at all. You can delete categories with any number of members. And with Wikia's changes to categories, you stand a decent chance of a person creating a page with a non-existent category, anyway. A bluelinked category hardly means what it used to when the policy was written.
  • I'd also point out that this rather complicated process of category approval may be one of the reasons that your category tree isn't particularly well developed. Now maybe you like how things are, but a lot of your categories are so huge that browsing is a forbidding prospect. I mean, category:Computer technology is entirely amorphous. It could be much more helpfully subcategorized. I have a devil of a time finding things around here just because everything is in such whopping great categories like category:medicine, category:biology and whatnot. I have to page through almost all of these categories just to get to the letter T.
  • Finally, your category tree ultimately has no single root. Category:Memory Alpha maintenance for instance is a completely separate tree from category:Lists, so you've got multiple category trees instead of one. That makes it harder to understand the overall structure of the database. You've placed the key to the category tree at Memory Alpha:Category tree instead of making it self-evident in the actual category tree itself. I have to be honest and tell you that, despite being registered here since 2007, I had no idea what the category tree of this wiki tree was until you directed me to Memory Alpha:Category tree — cause you just can't find it by simple browsing.
    czechout@fandom    <span style="">20:15: Sun 03 Jun 2012 
I'll only say that there are reasons that we have the category processes we do. It's important for the need and scope of a category to be worked out before it is created. What makes perfect sense to you for a category or organization might not make any sense at all to others. If you have suggestions for new categories that you feel would make things better organized, feel free to suggest them. Much like yourself, people work on them or suggest categories when they can; that's probably why some of them may still need reorganization. 31dot 20:21, June 3, 2012 (UTC)

Okay, so there are "reasons" but those reasons certainly can't be those which are actually listed at the policy page. All I'm suggesting is that the reasons given at the policy site should be truthful. There's zero truth there now, and anyone who's touched a bot knows that.
Also, sure, your idea of a category tree might not jibe with mine. But if one has to submit each individual category for committee decision, one can never make genuine forward progress on a tree. Or at the very least that progress will be so incredibly slow as to deter any user. I mean what happens if I get approval for the grandchild category but not the grandparent? Building a category tree is a process of one category leading to another. If you're requiring that each categorical level be approved, it's entirely possible that a tree will never be created because the categories at the top of a section of branches fails, even though its children succeed.
For instance, let's say that I wanted to create:
Medical databases
Starfleet medical databases
Klingon medical databases
Talaxian medical databases
And imagine that Medical databases passed the review process but Talaxian medical databases didn't and Databases itself didn't. I'm not that bothered by Talaxian failing because that doesn't upset the overall structure. It's a bottom-level category, and maybe there just aren't enough articles to justify it. Fine. But the failure of Databases is far more troubling. I would obviously have started my debate on Medical databases under the assumption that Databases would be approved. So now where do I anchor Medical databases, and its two children?
Now, maybe you would say that's not how the system goes around here. Maybe the deal is that you first get Databases approved, then you go on to Medical databases, and only then do you move on to the more specific ones. But what would that take? 21 damn days unless support from the community made it go faster. A simple, two level branch could take as much as 21 days around here! Surely you can see that's an inefficient way to build a category tree.
I just don't see how you can actually build a structure if you have to get approval for each and every girder that you're adding to the assembly. This policy, it seems to me, is one which does not assume good faith. It says to your user base, "You're probably gonna screw it up, so we'll create such an elaborate approval process that you won't even bother with categories anymore." Or, worse, it's saying, think about categories as an isolated island of information. Get approval to build that island and then move on to the next. This one-at-a-time approach is entirely antithetical to the notion of a tree.
I urge you to let people try to build trees, not islands. Sure, the average user might make mistakes along the way with the name of the odd category. But these can certainly be addressed ex post facto and easily changed with a bot once consensus on a better name has been reached. The name of any category is as cosmetic and pliable as the name of an article. To suggest that the average user would do some sort of serious harm to the database by having the free ability to create categories is insupportable. In the first place, most users don't give a damn about categories. And in the second, those that do will probably make an appropriate category, even if they get the name slightly wrong. The user bold enough to attempt categories has no interest in creating a useless category, because they still have to take the time to apply the category manually, page-by-page. For instance, the community might not like the nomenclature "USS Whatever personnel" — maybe you want to put the registry in there — but you'd be hard-pressed to admit that it's not useful to have a category of some name about the USS Whatever's crew. Once the user has done the hard work of adding the category to various pages, it's then a snap for the admin to quickly rename the category properly.
I ask you to consider which is better:
  • getting someone who's enthusiastic about starting and adding a new category to do the grunt work of adding that category and connecting it to the tree, and then cleaning up any mistakes with a 2-minute bot run
  • stopping them cold in their tracks, making 'em submit a formal request, and then making them wait seven days until 100% of their enthusiasm is spent, leaving you with an approved category name that then doesn't get applied
As an admin elsewhere, I would take the mis-named — but populated! — category any day of the damn week.
czechout@fandom    <span style="">21:19: Sun 03 Jun 2012 
I moved your post here, to keep the conversation in one place, as I prefer to do with my usertalk page. I will say that if you wish to have it out on this issue, that you do so at Memory Alpha talk:Category suggestions instead of just on various users' pages. The only other comment I have is that I cannot agree with your last statement- it's not just about the name, but about things like scope, formatting, etc. 31dot 21:24, June 3, 2012 (UTC)
Frankly, I think the scattered "damn"s are unnecessary, and do not build goodwill towards your point of view. 31dot 21:25, June 3, 2012 (UTC)
You also do not have to propose each individual category, if you wish to add a few to reorganize a larger one- we have approved blanket category additions in the past. I apologize for the multiple posting; but I see things as I reread your post. 31dot 21:30, June 3, 2012 (UTC)
Um, what? I gave a thoughtful and detailed assessment of current policy and you criticize me for using the word damn three times for appropriate contextual emphasis? Last time I checked, damn was only archaically a swear word and definitely a word with multiple appearances in the subject matter of this wiki. I didn't step one centimetre outta line, but if it offends you, I'll certainly apologise and try to restrain my use of it.
I should also point out that I didn't choose where to ask these questions. You came to my page. I'm just answering your hail, as it were. So I'd appreciate it if you actually answered me, rather than absurdly suggesting that your user talk page isn't the place to respond to, well, you. I'd prefer a bit more of a focus on the merits of what I'm saying rather than being told where I can ask my questions or what words I can use while making my inquiry.
You've said, "It's not just about the name, but about things like scope, formatting, etc." I've been around wikis for a long time, so I find that just a tad baffling. A category is just a step on a ladder, a branch on a tree. From a backend point of view, one category has no different scope than another. They all perform exactly the same function, a function defined uniformly by the MediaWiki software. There are only two types of category: hidden and visible. That's it. There aren't big and small categories. There aren't categories for strings and other categories for numbers. All categories are for pages. You can't, therefore, "format" a category. Every category has the same format. And in terms of scope, a category merely forms a bridge between its parent and its child. So it's scope should be narrower than its parent but broader than its child, and the only useful definition that a category has is its name. Any text you might want to put on the category page is all well and good — but it largely goes unread by people who are just trying to add a category to a page with autosuggest.
As I've said, I really don't think I've got the time to shepherd a number of intricate category tree changes through an elaborate approval process. Instead, what I'm trying to figure out is simply the rationale for the policy. Did you guys get burned at some point by "category vandals"? Was there some big schism at some point in the wiki's past over the creation of categories? Was the policy written before most admin had bots? Is this a holdover thing from the pre-Wikia days and a very much earlier version of MediaWiki? There's gotta be some explanation why Memory Alpha:Category tree is flat out fibbing. And the other thing is that it's not even really that enforceable these days since most users don't see redlinked categories anymore. Most users could plausibly create a new category without even knowing it. So if it's possible to innocently create a new category, how can you logically have a rule against it? You can't get mad at someone for doing something Wikia don't want them to even see that they're doing.
At the end of the day, what I'm saying is, look at the policy. Don't just accept it as is. Consider whether it's still relevant in the current Wikia climate. Allow yourself to wonder whether it's compatible with the basic precepts of "assuming good faith" and being bold.
czechout@fandom    <span style="">23:29: Sun 03 Jun 2012 
Since you seem to be all about policies, you should read the one about keeping your indentation consistent. Saying damn does not bother me in and of itself; I'm a big boy, and I don't seek an apology- I was only stating I feel that it doesn't help your case.
I cannot speak to the entire history of this site, as I have only been here since 2007. I only know that the procedure for discussing categories has been here relatively unchanged that entire time, with few complaints. I frankly don't see what the problem is here, despite your lengthy explanations; I don't think it is "an elaborate approval process" to post what you want to do and get someone to agree with you. We are not the US Congress; things can get done if people want them to.
I originally posted here merely to clarify a point, not to debate policies with you- doing which should be done on the talk page of the relevant policy and not a specific user's page, since policies concern all here. If you dislike the category suggestion page, then bring it up on that page; it is your right to do so. You may have some interesting points, I don't know, but they should be debated and discussed in the correct place. 31dot 01:36, June 4, 2012 (UTC)

I've also inserted CzechOut's reply to the original post here where I think it happened chronology, and I'll reply to parts of it here as well, saving the policy parts for that talk page. I have not read the rest below that.

For the record, I have no experience with a working bot, though I do have a username "reserved" for one, and all my edits to categories are done by hand. Since I'm the guy who has subdivided some of our largest categories, and added other ones containing hundreds of pages, I'm down right offended that you think it's so easy that it isn't worth mentioning. Until all users have bots by default, our policies and guidelines will reflect that fact and highlight the amount of time and effort it takes to change one of these. Also, since it doesn't seem clear, MA is not a wiki that was created at wikia, and our host does not make or change the policy on this site every time they make an asinine decision that breaks a basic function of the software. You may buy their reasoning, but the MediaWiki software and I do not. - Archduk3 05:00, June 4, 2012 (UTC)

Well, the category script is, in fact, so easy you don't need to know anything about bot programming or regex to use it. Literally, the bot says, "What's the old category? What's the new one?" And that's it. There's no need to be offended by that. It's just a statement of fact that it's simple. I don't know why you'd want to deny yourself such a useful tool. I'm sure you could find someone here who'd help you set one up. Certainly I'd be glad to help you, if asked.

Because of the existence of pywikipedia scripts, it's just a straight up lie that it takes any significant time or effort to change a category name. I don't deny that if you choose to edit manually it will take a long time — but that's totally your choice. If instead you spend the time learning what a pywikipediabot can do to improve your editing efficiency, you'd soon come to realise how much time you literally wasted doing it manually. Seriously, the very first time you ran the category script, you'd instantly wonder why you ever did it any other way.

And your suggestion that every user should have a bot only underlines your current knowledge gap about bots. In no way would you ever want to give ordinary users access to such a powerful tool. This in fact is why Wikia don't give even bureaucrats the power to declare a user a bot, and why they don't even let non-admin ask for the bot flag.

I'd urge you not to be so proud of the time you've spent doing things the hard way. I'm not trying to denigrate your past work; believe me I've done plenty of tedious, manual work myself. But if there's no need to, why would you want to?

Finally, I know you have a belief that somehow the pre-Wikia life of this community confers upon it some sort of special status that gives you the right to be openly contemptuous of Wikia. As you've probably surmised, I've got my doubts about that. But in this instance I pushed as hard as I possibly could against the bluelink category thing. It's one of the few changes that I think it's totally stupid. But it's the way that it is. There's little use in saying that it doesn't have an at least potential impact on you. Your WantedCategories list may be clean now, but will it remain so when you finally get some new Star Trek content next year that drives a flock of inexperienced editors to your site? And if Wikia pull the WantedCategories report, which could well happen, it'll be even harder to catch what in the past we've called "uncreated categories".
czechout@fandom    <span style="">05:47: Mon 04 Jun 2012 

Actually, MA is treated differently from the rest of wikia right now, and it is copyrighted differently from the rest of wikia, excepting Unencyclopedia; so yes, I do have grounds to treat a company that:

  1. Acts like it owns the material here that "by law" can't be use for profit, or elsewhere that can't be "owned" in a traditional sense
  2. Treats it's "active content maintainers" like slaves, and it's users like idiots
  3. Clearly has no intent to...
    1. Keep it's word on anything that can't change at their whim
    2. Providing a working and stable system
    3. Teach people how to use the software as designed
    4. Listen to feedback or acknowledging that it might have
    5. Provide any real transparency on how they make their money off of your work
    6. Treat you like the people who are doing the work that gets them their money
    7. Stay a content creator instead of a content content aggregator
  4. Spends more time getting people like you to think it's OK for them to do those things then beta or bug testing their "features" the liars, thieves, and downright nefarious collection of people it really is, and that's the way it is. Oh, and I'm not "proud" I haven't got around to getting a bot yet, but I'm not going to treat those without one like second class users when proposing polices. That kind of biased thinking is a slippery slope, and you might want to check your footing. - Archduk3 06:25, June 4, 2012 (UTC)

In absolutely no way am I suggesting that people without a bot are "second class users". The current category policy does a nice job of that already. The direct implication of current policy is that the admin here do not trust the average user to create the category tree. That is abundantly clear in the 2004/5 coversations at Memory Alpha talk:Category tree. Bot-enabled admin would absolutely democratize the category process.
Moreover, your emphasis on the "effort" and "hard work" it takes to change category creates a second class citizenry. Only in your example, the limiting factor isn't possession of a bot, but rather the possession of time and patience — neither of which are genuinely necessary to the changing of categories.
In my view, it's not that admin and users are groups separated by power, but groups separated by focus. Admin have a different set of rights because they are the wiki's janitors. They must clean up the joint, because they've been equipped to do so. Having a bot is simply an extension of those rights — a tool that admin can use to accomplish the onerous housekeeping chores that are, by definition, theirs to complete.
I honestly don't know why you're being so truculent about this; it's clear you took actions last month that necessitated sulfur to fire up his bot for simple template replacement. If you had a bot, you'd be able to be bold, as you clearly wished to be in that instance, and yet not obligate anyone else to clean up after you.
Besides, it's a total red herring to suggest that this category issue is about whether people can have bots on this wiki, or whether having a bot makes certain users "second class" for not having one. The community has already ruled that bots are allowed here. Since there are users running bots, it hardly matters that you personally don't seem to want to. What matters is that policy be written to accommodate the realities of what bots can do.
czechout@fandom    <span style="">14:37: Mon 04 Jun 2012 
And the reality is that the category scheme we have... works. And works well. Sure, it's not the same one you use at the Doctor Who wiki, but it works well for MA. -- sulfur 14:44, June 4, 2012 (UTC)

Wikipedia links

Just a tip; Wikipedia links should not be within the in-universe portion of articles, as Wikipedia is not a part of the Star Trek universe. I removed the links, but left the words at band music. 31dot 18:29, June 9, 2012 (UTC)

Speedy deletions

To clarify for you, articles should be tagged for speedy deletion only under these circumstances. Just FYI. 31dot 21:54, June 10, 2012 (UTC)

Deep Space 9 v Deep Space Nine

Please note that the station is "Deep Space 9" and the show is "Deep Space Nine". Please take this into account when adding it as a link on articles. Thanks. -- sulfur (talk) 19:18, September 10, 2012 (UTC)


Not sure what sulfur told you, since your communication isn't on site, but sidebar image must control all image sizes in the sidebars for them to be used. Just a FYI for your work on the drafts. - Archduk3 03:19, July 7, 2016 (UTC)

Sidebar image doesn't work in the new style of sidebars, something I did communicated previously. One of the big reasons I left a couple of them un-finished, because I couldn't come up with a way to handle size changes (ie 'halfwidth') in a clean way.
The starship sidebar draft still doesn't do that, but it's "better" than it was. I'm not the biggest fan of arbitrarily putting hard pixel counts in there to force only "half width" in that way, but I'm not sure how else to handle it. -- sulfur (talk) 10:40, July 7, 2016 (UTC)

What's the problem with SI? Is it the named parameters or something else? The other templates seem to work fine, so it must be something about that template specificly that isn't working. - Archduk3 13:43, July 7, 2016 (UTC)

I'm not sure what it is, but I worked with a couple of engineers to try and suss it out, and it didn't display things or deal with things properly with the newer sidebar style. That was a big reason why I didn't continue to work on a few of the sidebars while I was doing the conversions a few months back. -- sulfur (talk) 13:54, July 7, 2016 (UTC)

Is there a similar problem with the military conflict and rank sidebars? Both of those use different image widths too. It might be worth it to try creating/using a "clean" (without the named parameters) SI template call to see if that's the problem, or if it's something else. SI uses both expressions and a template inside another template, so figuring out the failure point is key, obviously, instead of doing the typical wikia thing of just letting failure dictate how something is going to be. - Archduk3 14:08, July 7, 2016 (UTC)

There are two main issues with the logos -- and I would tend to agree with Archduk3 that these issues also apply to ranks.
  1. Logos are usually transparencies, and thus a call for the infobox images to be (max-)width:100% -- which is wholly appropriate for the main infobox images, which are either 4:3 or 16:9 -- eschews much of the alpha element. That is, the transparency seen on the left and right of the image is "pushed aside" by the main image "growing" to be 100% width.
  2. They tend to be exceedingly portrait oriented. There is a point at which the ratio between height and width is over-skewed towards height, and thus a command of max-width:100%; height:auto serves to create a super-long image. Roughly, that point is when the image is more than 2 times taller than wide. The best solution I found was to use one of the default widths in {{sidebar image}}. Since that width was already in wide use on the wiki, I figured it would create the least number of differences between what was showing in non-portable sidebars, and what will display in portable ones.
    czechout@fandom    14:53: Thu 07 Jul 2016

My question is why SI wasn't working to get that width value. It should produce the same thing you "hard coded" if everything is working correctly. What's the point of failure? - Archduk3 03:23, July 12, 2016 (UTC)

Well, I was trying to make {{sidebar starship}} work -- not {{sidebar image}}. As you probably know, {{sidebar image}} is misnamed. It's not a sidebar. It's just a helper template that happens to have the name "sidebar" in it. If you use it independently of a sidebar, you don't get a sidebar. So I didn't try to "fix" it in any way.
I just took the default intent of SI and thereby solved the problem of the massive mission patches. My solution went exclusively to that problem, for the two reasons listed above.
So I guess that, at this time, I concur with sulfur: I don't know what's up with {{sidebar image}}. But I wouldn't mind some guidance as to why it's important to preserve.
It's only on about 1500 pages, and it's used in a way that could be better handled by a simple use of a second <image> instance. Retaining it would be, in most cases, redundant, wouldn't it? Something like <image source="image2"> would do what it's called upon to do -- evidenced by the fact that the sidebar at USS Korolev works whether you use {{sidebar starship}} or "sidebar starship/Draft".
If you could give me some examples of where {{sidebar image}} is required, or information as to why you think something like USS Korolev works better with SI than with the image handling inherent in PI code, it'd be really helpful! :)
czechout@fandom    04:58: Tue 12 Jul 2016

The SI template(s) are suppose to control the size of all images used in sidebars, and it works just fine in unconverted templates, so it only needs to be "fixed" becuase you're "breaking" something. While the 100% images don't need to be controlled from SI anymore, since the new format already handles that, the multiple image uses, like the ones at Earth-Romulan War and crewman, or the halfwidth image uses, at USS Valiant (NCC-74210) and United Federation of Planets, still need to use SI, unless you can work out a different way to control those sizes in multiple sidebar templates from a single location. That said, SI should probably be reworked to reflect the difference in how the 100% images are controlled once all the sidebars are converted. - Archduk3 05:31, July 13, 2016 (UTC)

Sorry for the delayed response; I've been out for a bit. Thanks so much for the further examples. I'll look more specifically at it over the next few days to see what really is going on. If you find any other examples of multiple, side-by-side-imaged infobox that you think might illustrate your issue, please don't hesitate to send them my way!
czechout@fandom    16:46: Fri 15 Jul 2016
Okay, so the issue seems to have been solved. Please take a look at User:CzechOut/Conflict and tell me if you see anything that the newly created {{sidebar image portable}} isn't performing on the PIs like {{sidebar image}} does on the non-PIs. Thanks!
czechout@fandom    05:16: Thu 21 Jul 2016

As should be obvious with the other examples I've added, a verticle centering issue reamins. There are also Issues with the formatting of some text in SMC too. I'm limited right now in the number of browsers I can test, since I remember some never supported the side-by-side image placement in the original SI. It would be nice to know if this fixes that too, or how that not working again would look like. Sulfur might be able to test that out in the morning. - Archduk3 05:42, July 21, 2016 (UTC)

Vertical centering issue fixed. As for text formatting, that's not really something I'm actively doing here. Sulfur would know far better than I what those issues are. I know there were some minor differences between the old boxes and the PIs that have already been converted, so I'll consult with him on what needs to be done in that area. The thing I'm going to try to work on now is the last case you gave there, in which the {{{image2}}} is not meant to be side-by-side with {{{image}}}, but rather at the bottom of the sidebar. That's an interesting case I hadn't anticipated.
czechout@fandom    05:50: Thu 21 Jul 2016
Okay, that case is now solved, too. I don't think there's anything wrong with the images anymore, do you?
czechout@fandom    05:58: Thu 21 Jul 2016

That seems to have solved it for this sidebar. I assume the SI sub template for the three image case at crewman with the rank sidebar just needs the thumb call dropped, more or less? - Archduk3 06:05, July 21, 2016 (UTC)

Well, the PIs are actually powered by {{sidebar image portable}}. Since it's not a sidebar itself, I imagined there might have been some applications that didn't involve a sidebar, so I wanted to preserve {{sidebar image}}. But {{sidebar image/3img}} only appears on one page, so we can probably just change that template to fit the needs of crewman, once {{sidebar rank}} gets converted.
czechout@fandom    06:13: Thu 21 Jul 2016
Archduk3, I know you were concerned about {{sidebar rank}}. After working with it quite a bit yesterday, I'm convinced it's not really an infobox. It may well be a "sidebar" in MA terms, but it's simply a way to display a series of images vertically. Because it has no true "data" inside of it, the things one has to do to get it to render on the desktop actually make it less appealing in mobile OSes. Additionally, it has a lot of non-standard styling as compared with other infoboxes. The biggest deviation is that previous MA archivists have set its width to be just 200px in Common.css. As you know, this is far narrower than the standard sidebar width of 292px.
Accordingly, I'm just going to leave it alone. I've changed its template classification to that of an image-handling template. I've also supplied sulfur with screenshots of how {{sidebar rank}} looks on an iPhone with PI code and non-PI code to demonstrate that it's better off if not considered an infobox.
czechout@fandom    17:04: Fri 22 Jul 2016

What's the rationale for red links to not appear in the sidebars now, or is that unintentional? - Archduk3 16:26, July 24, 2016 (UTC)

Which redlinks did you mean specifically? MA has long employed #if statements for the text-based variables within sidebars such that an undefined variable wouldn't appear. That's the same behavior as exists with the new sidebars. However, if you choose to put a link to a non-existing page as the value of a variable -- such as setting "30000" to be the value of {{{date}}} -- then a redlink will appear in both old and new sidebars. So there's really no change as far as data values are concerned.
If, however, you're talking about redlinks to non-existent images, then that is something which is a bit different. In the new sidebars it is, by Wikia Engineering intent, that non-existent images are simply ignored. You don't get a redlink; that part of the sidebar is just skipped. The reason for this change is probably twofold at least: 1) it's consistent with how data variables work; and 2) many communities would prefer for errors not to show to readers.
Sulfur has been both happy and sad about this change. In the case of the new episode title cards, it's a positive benefit that the image handling works this way. But he has expressed concern about the behavior elsewhere. There are some new sidebars -- {{sidebar comic}} being one -- where he has successfully introduced the redlink-for-missing-images behavior. So a solution exists, but I'm not sure whether it's sulfur's intent to put it everywhere. In any case, it's an easy fix that you guys can talk about and retrofit at any time.
czechout@fandom    16:25: Mon 25 Jul 2016

Bot cleanup

Not that I expect anyone to even remember, or have ever actually worked on, getting your bot to stop creating redirects for pages that have no incoming links every time someone is renamed, but what's the status of that? Also, I need User:DarienLeonhart/wikia.css and User:TwoTailedFox/wikia.css deleted, and then these links removed, or just let admins delete CSS and JS pages again, and I can do it myself. - Archduk3 17:23, January 8, 2020 (UTC)

Hey there! Sorry for the delay in responding, but I'm currently on vacation.
Your questions are honestly a bit outside my day-to-day work. I vaguely remember talking to Sulfur about this kinda thing in the past, but my work hasn't put me in orbit of this stuff for quite a while. I'm not aware of any current plans to stop this type of redirect being made, as it's convenient to the process of renaming.
All I can say with surety, though, is that removing the personal CSS pages of users is not meant to be something admin can do. As Help:Personal CSS and JS, clearly states, ". . . other users on a community, including admins, cannot edit another user's personal CSS and JS pages." That would apply to the redirects-upon-renames, as well.
If you'd like to ask for an exception to be made in these cases, you could send in a Special:Contact to get a current view from our Customer Support staff.
As it turns out, you'll need a Special:Contact, anyway, to answer your other question. See, my personal bot has never edited here, so I assume you're talking about one operated by other Fandom staff members. A Special:Contact message is the only way to ultimately put your request before the operator of whichever bot you mean. Please be sure, when you file your message, to mention the name of the bot — and to give some links to the kind of behaviour you're interested in overcoming.

czechout@fandom    15:36: Thu 16 Jan 2020
Community content is available under CC-BY-NC unless otherwise noted.

Fandom may earn an affiliate commission on sales made from links on this page.

Stream the best stories.

Fandom may earn an affiliate commission on sales made from links on this page.

Get Disney+