User talk:OOeyes

From Hearthstone: Heroes of Warcraft Wiki
Jump to: navigation, search

Hi, Trying to fix the image links for cards like this one: I made this edit: but I don't know if templates have an immediate effect or not. I can't see my edit at all on the final page. Can you take a look and check if my edit makes sense? I also think cards with ' in their names need the same fix but in that case we would have to use #replaceset instead, right? Razzen777 (talk)

Yeah, those fixes should be on the data side, in {{card data}}, rather than trying to fix after it's pulled into the page. Otherwise, you'll remove the valid colon after File. I'll take care of it momentarily, and I apologize... I'll have to revert the edit to {[t|card box/layout}}. Also, Card box is only used on Hunter secrets and the other two pages like it. {[t|card infobox}} and {{card infobox/layout}} are the ones used on regular card pages. This is why you're not seeing your edit. OOeyes (talk) 16:53, 29 August 2013 (UTC)
Thanks for the reply. I had looked earlier at {{card data}} but didn't see that it uses the same way to build the links to the available images. This is my first time doing anything on a mediawiki so I'm still learning how to navigate into the templates when I catch a bug in there or when one needs an edit. Razzen777 (talk)

I was looking at {{Template:Card_by_ability_header}}, I believe the description column should have a minimum width set (if possible) and don't know why the table is set at max 65% width. If you look at Charge_(ability) and resize the browser you can see that as you reduce the available width for the page, the table starts looking pretty weird but it wouldn't if it wasn't limited to that 65%. I'm not going to modify that template as I don't know the formatting rules for this wiki yet. Also, on the template for the rows, wouldn't it be better if the class icon was removed? The class name and color code is enough to provide the class information. Razzen777 (talk)

Noticeboard[edit source]

I haven't received any response yet from you to my posts on the noticeboard talk page from July regarding implementing card tags, tables, etc. If you're simply busy, that's fine, but I'm concerned you may have missed them entirely. The only pressing points are having concepts (or equivalent means) for making card set tables, and adding tags to the infoboxes. -- Taohinton (talk) 14:17, 12 September 2014 (UTC)

I must have forgotten to leave a message, but I set up tags some time ago, along with the three custom templates that use them: {{Custom equipment card table}}, {{Custom minion card table}}, and {{Custom spell card table}}. If you'd rather use concepts for it, the property name is just Has tags instead of Has abilities, so something like [[Has tags:Area of Effect]] should work fine in a concept, and {{Card by ability table}} could work for that, since despite its nongeneric name, it's turned out to work for any concept. I believe right now, the tags are set up to be invisible in the infobox with the idea that they would just be used for selecting cards to put in tables, as we already have abilities as a visible alternative, but that'd be fairly trivial to change. oOeyes User-OOeyes-Sig.png 17:54, 12 September 2014 (UTC)
Yeah, the original idea was to have tags invisible, but as the system developed it made sense to have them visible. I've moved the ones that don't want to be in the infobox (namely expansion/era-sorting and card art-related) to categories at the bottom of the page; the remaining tags are quite handy to have displayed and clickable (I'm hoping!).
Regarding sorting, I've already set up concepts using tags; as mentioned it would be easier to use a custom template, but we'd need one for all/any card type, rather than separate ones for each. What I'm struggling with though is setting up a concept for card sets. I tried but obviously couldn't get quite the right syntax (or there's something else I'm missing). Again, it would be even simpler to use a custom template for that, but we'd need one that included all card types. -- Taohinton (talk) 14:57, 14 September 2014 (UTC)
Any progress with these bits? -- Taohinton (talk) 17:22, 31 October 2014 (UTC)
I think I may have some time this weekend for these requests. I'll try to get it all wrapped up in the next couple days. oOeyes User-OOeyes-Sig.png 06:52, 1 November 2014 (UTC)
{{Custom card table}} is now available. It works for spell, equipment, and minion cards.
Tags have been made visible and now link. This changes their nature slightly, because like abilities, the page name and the preferred link text are not always the same. I set up {{Card tag page}} for this case. Right now, it's nothing but a placeholder that just outputs exactly what it's given, but you can see {{Card ability page}} for an example of a template with the same purpose that actually does something. The basic idea is that you use the preferred link text as the tag name in {{Card infobox}}, and when that isn't the same as the page it should link to, you can add it to Template:Card tag page. Perhaps a line like: |durability-related=Cards related to durability as a quick example.
For card sets, the property name is Is part of set. [[Is part of set::Basic]], for example, should work in a concept. At least, it worked in a quick test on Special:Ask.
I think that gets everything caught up? I apologize, but it was a crazy month, and it feels like I'm forgetting something yet here... oOeyes User-OOeyes-Sig.png 06:39, 4 November 2014 (UTC)
Thanks. I'm still a bit busy with various projects to have gone through all the details, but looks good so far! -- Taohinton (talk) 15:44, 11 November 2014 (UTC)

Data import[edit source]

You haven't replied to my post on the noticeboard yet, and since this is time-critical, I thought I'd ping you here. Any update would be appreciated, to let me know where I stand. -- Taohinton (talk) 22:09, 1 April 2015 (UTC)

My apologies. Some things came up yesterday afternoon, and I see I missed some things in the confusion. I'll talk to the relevant people tomorrow and see what can be arranged and look into the tooltip issue as soon as I can. oOeyes User-OOeyes-Sig.png 23:38, 1 April 2015 (UTC)

Infoboxes[edit source]

In case you didn't see my note, I'm hoping we can get multiple infoboxes set up before Thursday; the first multi-boss fight will be released then so obviously the page will be getting a lot of traffic, and it's currently missing the boss for the first half of the encounter. -- Taohinton (talk) 17:45, 8 April 2015 (UTC)

I did see it. It's been a busy week, but I've set aside some time today to make the needed changes. oOeyes User-OOeyes-Sig.png 18:47, 8 April 2015 (UTC)
Thanks again. -- Taohinton (talk) 20:19, 9 April 2015 (UTC)

Data import[edit source]

Posting this here to make sure it finds you as quickly as possible! The latest patch has just hit the servers and has perhaps 70 new cards, so we could really do with a data import as soon as possible. The data has just been imported to Hearthpwn so hopefully it won't be too hard to CC it to the wiki too.

I was just in the middle of writing up a list of what we would ideally like re: data imports, but in brief:

  • All new data
    • Cards (all cards, from any set, including Cheat and Credits)
    • Hero Powers
    • Heroes/Bosses
    • Enchantments (previously unwanted, now wanted if only so we have a complete list)
    • Basically any new card data available
  • Images, new or updated

We definitely *don't* want existing data overwritten, but apart from that I'm quite happy to accept anything they want to throw at us. However, if it's more convenient to specifically import only the new/Tavern Brawl/Credits stuff, that's fine.

As usual, time is of the essence, as getting the import done now rather than later would save a mountain of manual work. Any compromise that would make that happen would probably be acceptable. -- Taohinton (talk) 21:26, 12 June 2015 (UTC)

x_x ... Ouch, that was bad timing. There's been some maintenance in this area today, so I was out of touch. I don't know how easy it'll be to get this going over the weekend, but I'll try to get in touch with the relevant people tomorrow. oOeyes User-OOeyes-Sig.png 03:38, 13 June 2015 (UTC)
That's ok, and thanks. New patch on Friday not the easiest for arranging imports ;) -- Taohinton (talk) 12:04, 13 June 2015 (UTC)
It sounds like the HearthPwn team shares that pain. It sounds like they took some kind of a shortcut getting it up to HearthPwn so fast, and the downside to that is that some more work needs to be done before the wiki importer can use the new data. Of course, they do sometimes surprise me and get things rolling faster than they tell me, but right now, the word is it'll have to wait until Monday. oOeyes User-OOeyes-Sig.png 23:15, 13 June 2015 (UTC)
I apologize for the delay on this. They've told me they're working on refactoring the importer so it can work directly from the Hearthpwn database so this can be faster in the future. The current ETA for the import is now tomorrow. oOeyes User-OOeyes-Sig.png 21:01, 16 June 2015 (UTC)

Eyes! You still exist![edit source]

My apologies for stalking you on this wiki, but I recently re-downloaded gw1 to play with some friends and I got nostalgic and toured gwiki a bit. Saw you were still active on a bunch of wikis so I thought I'd pop in and say hello :D --El Nazgir 12:52, 19 July 2015 (UTC)

Redirect equality[edit source]

Re: our discussion last year about redirect equality, it seems Gamepedia has competed its upgrade to 1.26? If so, putting the change we discussed into place would be helpful. With all the new cards I'm spending a lot of time at the moment updating links, due to the current issue. -- Taohinton (talk) 23:17, 9 April 2016 (UTC)

*facepalm* Right, I lost track of this among all the upgrade issues. I've added support for following redirects to Template:Card, along with an exactpage parameter in case it's needed. I can't remember if any others need to be able to follow redirects. It's not difficult to adapt them now that the #follow function is available, though. What that does is check if the given page is a redirect, and if so, it returns what it redirects to. Otherwise, it just parrots out the page name it's given. So it's not much more than changing things from [[Has page::{{{page|}}}]] to [[Has page::{{#follow:{{{page|}}} }}]]. Or let me know if I've missed something, and I'll add it in. oOeyes User-OOeyes-Sig.png 01:57, 10 April 2016 (UTC)
Oops, missed this reply. {{Card}} is working beautifully now, thanks. Is it possible to have wiki-link tooltips similarly show the target page rather than the redirect? e.g. every time I want to link to Yogg-Saron I have to type [[Yogg-Saron, Hope's End]] or ideally [[Yogg-Saron, Hope's End|Yogg-Saron]], in order to get the tooltip to show up.
On a related note, tooltips no longer show for me on any talk pages, including Hearthstone Wiki talk:Admin noticeboard (or this one); they haven't for quite a while now. -- Taohinton (talk) 00:12, 18 April 2016 (UTC)
Well, there's good news and bad news. The good news is that it was easy to get links to follow the redirects if the link is already enabled for a tooltip; that was just using #follow in MediaWiki:To-tooltip-page-name. The bad news is that only links to pages in Category:Has tooltips enabled or any of its subcategories get activated presently, and I never thought to test redirects in the category check code. So, it works if I put the Yogg-Saron redirect directly in that category, but otherwise, the extension will conclude it's not supposed to have one. Any fix will have be internal to the extension and go through dev for deployment, and I'm afraid I have to make The Black Death Wiki a priority since the game will be in early access soon.
Re: tooltips on talk page, the extension is configured by default not to enable any tooltips except on a few specified namespaces, and none of the talk namespaces are specified by default. I'd have to get dev to put the setting in our configuration tool, though. It hasn't been needed yet, and I'm not sure how long the turnaround would be on that. oOeyes User-OOeyes-Sig.png 09:37, 18 April 2016 (UTC)
Fixing the first point would be good, although it might be manageable to manually set up the redirects with categories. The latter point would be handy, since it's useful when having discussions about card mechanics and the like, but it's not a very high priority.
Slightly higher priority: something you've changed seems to have broken tooltips all over the site :P I'm getting the Molten Giant/Tooltip bold floating text in place of an image, every time. Other than that I shouldn't need to hassle you with anything for a while (fingers crossed!). -- Taohinton (talk) 19:02, 18 April 2016 (UTC)
I'm not able to replicate this issue in either Firefox or Chrome. If you could, when you have a page with some links up that should show tooltips, add ?debug=true to the end of the URL in your address bar. That loads all scripts in a different way and hence (for that page, anyway) bypass anything you have cached. If the tooltips work correctly in the debug mode, it might be as simple as needing to do a hard refresh outside of the debug mode to get your browser to reload the scripts. oOeyes User-OOeyes-Sig.png 00:59, 19 April 2016 (UTC)
And big facepalm. It just hit me. It's a language issue... when the extension pulls up MediaWiki:To-tooltip-page-name, which tells it how to figure out the page name for the tooltip from the page a link links to, it's actually pulling it up in the user's language rather than the wiki's default. That's how you're bypassing the custom message and getting the default. That must have happened when I had to change how the message was pulled up to avoid the message cache due to an error that caused in Semantic MediaWiki. I can work around it for now by overriding it for specific languages. A proper fix will have to wait until I have a block of time long enough to fix these bugs and test that the fixes don't break anything else. oOeyes User-OOeyes-Sig.png 04:09, 19 April 2016 (UTC)
Just found this. Unfortunately, your subsequent changes don't seem to have helped at all on my end; I'm still getting the same bold text tooltips. I've tried adding ?debug=true and that doesn't help either. Since you're pressed for time and it was the changes to allow for redirects that caused the problems to start with, perhaps it would be best to simply revert those changes until you have time to set things up in a foolproof way? -- Taohinton (talk) 07:32, 19 April 2016 (UTC)
What's your language setting at? I tried to hit the more common ones as a temporary workaround. Basically, it's just copying the contents of "MediaWiki:To-tooltip-page-name" to "MediaWiki:To-tooltip-page-name/language code", where the language code should be here: oOeyes User-OOeyes-Sig.png 09:06, 19 April 2016 (UTC)
I've set one up for my language code (en-gb), and it's now working once again. I've added the other missing ones from our list of 10 most common nationalities, too, so hopefully most people won't get the error. -- Taohinton (talk) 14:09, 19 April 2016 (UTC)
I forgot to leave a message noting that this issue should be resolved now. oOeyes User-OOeyes-Sig.png 21:31, 6 July 2016 (UTC)

CSS color fix for Common rarity[edit source]

Hello, I just noticed that the color coded label for Common cards doesn't show up readably in card infoboxes since it is white-on-pale. I assume this is only since the recent site re-skin. Example: Earthen Ring Farseer Other rarities look fine. The best looking solution from my perspective would probably be to give the Common style a dark text-shadow so it outlines the text - with some Stack Exchange suggestions I felt like text-shadow:-1px 0 1px #444444, 1px 0 1px #444444, 0 -1px 1px #444444, 0 1px 1px #444444; looked pretty good. The other solution would be using gray text color, which is not the end of the world but isn't really matching the color of the rarity gem in the game anymore.

As far as I know I can't change CSS styles myself, can you take care of it? Thanks! - jerodast (talk) 18:18, 30 April 2017 (UTC)

It's done, but as an administrator, you can since that extends permission to edit in the MediaWiki namespace, and the relevant page here is MediaWiki:Common.css. oOeyes User-OOeyes-Sig.png 10:40, 1 May 2017 (UTC)