Hearthstone Wiki:Admin noticeboard

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

The Admin noticeboard is one way through which users can notify Administrators of issues needing administrative attention. While users are welcome to directly contact specific administrators (especially if they are seen to be active), posting here can be an easier and quicker way of ensuring that at least one admin will notice an issue and respond to it promptly. Remember to sign (using four tildes: ~~~~) when posting an issue.

Before posting an issue here, please consider the following:

  • This page is for reporting wiki issues. Please post discussions on the talk page.
  • Post only issues that require administrative action, i.e. blocking vandals, protecting pages, restoring deleted pages etc.
  • Do not post deletion requests here. Deletion requests should be made by adding {{delete|reason for deletion request}} to the top of the target page, which will then automatically mark the page as a candidate for deletion.
  • Do not post issues regarding content disputes. Try making a request for comment instead.
  • Mediation requests between users should only be made once a resolution could not be reached between users.
  • For issues regarding the use of this wiki, please see our help center.

In case of vandalism, posting about it here is low priority. Revert it first, anyone can do so. If the vandal created a new page, tag it for deletion. Assume good faith and consider leaving a message on that user's talk page to explain the reason. Post here only if the user has made several disruptive edits and/or persists despite a warning. Always avoid a revert war with the vandal; it is far better to wait until an admin has a chance to intervene. If a user must be reported here, please use {{user}}, preferably as the topic subject/headline.

Current issues[edit source]

Hearthpwn-poking[edit source]

The people responsible for updating card images on Hearthpwn always seem to be busy, and after making inquiries through various channels, I'm sad to say we still have numerous old versions of card text that was changed in August last year; and a plethora of more minor mistakes from even longer ago. These aren't errors in the import; the people who create images for Hearthpwn simply haven't bothered updating the images to match the new card text, or in some cases uploading it at all. It seems fairly simple, and Hearthhead is usually up to date with all this, but Hearthpwn seems to lag behind, often by a long way. While less important, Hearthpwn is also lacking any images at all for a number of Tavern Brawl cards, which is a bit annoying, especially as again Hearthhead seems to manage to get them up quite quickly.

The most important examples are Fel Reaver, Leokk, Snipe, Mirror Entity, Repentance and Sacred Trial, which have had their text changed. Scarab is now a Beast. A few Brawl cards have been changed, like Murloc Bonus, Battlecry Bonus [should have said: Spell Bonus ], Stolen Winter's Veil Gift and Winter's Veil Gift - Dragonkin Spellcaster has even had its name changed - while many more are missing entirely: Second Class: Druid, Second Class: Hunter, Second Class: Mage, Second Class: Paladin, Second Class: Priest, Second Class: Rogue, Second Class: Shaman, Second Class: Warlock, Second Class: Warrior. Fadeleaf Toxin lacking a card image might be intended as a joke, but it prevents the wiki from having a properly formatted image, or any golden image at all. Others are lacking minor changes to text like typos, highlighting, key line breaks or capitalisation: Dragonkin Sorcerer (you), Illuminator (Health), Ragnaros the Firelord (Can't attack), Ancient Watcher (Can't attack), Argent Commander (<br/>), Sneed's Old Shredder (Legendary) and Wild Magic (Showdown at Blackrock Mountain) (to your hand). That should be all of them, but it's possible I've missed some graphical errors or missing images.

I would happily handle this myself if I had access to a tool to create high quality images like this, but I'm not aware of one that would meet the standards we need for the site. Meanwhile, fixing these errors on Hearthpwn would also serve to make that site look better, which isn't really my problem but should probably be the prime motivation for whoever's this job is. -- Taohinton (talk) 00:41, 13 June 2016 (UTC)

I sent this along today. I apologize for delaying on this, but with E3 going on, I was afraid it might get lost in the shuffle. I'll let you know when I hear back. oOeyes User-OOeyes-Sig.png 20:55, 19 June 2016 (UTC)
Thanks. Also if you could add Sapling to the list - it has a brown 'druid' frame in-game, not a grey 'neutral' one. Hopefully that's the last of them! -- Taohinton (talk) 02:31, 21 June 2016 (UTC)
Except for Sapling, which I just sent up, these should now be updated. Normally, this process should be happening automatically as changes in the card data are detected. The working theory is, given these are older changes, there might have been a problem in previous builds that failed to regenerate the images when the changes were detected. After later patches, the need to regenerate these cards wouldn't have been detected until the card data changed again. Hopefully, this is purely an old issue that isn't affecting the current versions of these tools, but if you do see images failing to update in the future while the actual card details are updated, pass it along. The automated process isn't likely to self-correct if only the image itself is old. oOeyes User-OOeyes-Sig.png 21:15, 22 June 2016 (UTC)
Excellent, indeed they have. One error on my end: it wasn't Battlecry Bonus that changed, but Spell Bonus. If you could poke that across that would be great, and should be almost entirely up to date at last!
I'm very glad to hear that such a system is in place for future changes. I'll be happy to point out if they fail to update in the future. -- Taohinton (talk) 22:12, 22 June 2016 (UTC)
Odd but related issue: Hearthpwn's static image for golden Undertaker hasn't been updated. As a result while the animated golden image on their site is up to date, the import keeps importing the old version (with the old card text) to the wiki. You can see the correct, animated version here and the old, static version here. -- Taohinton (talk) 23:12, 29 June 2016 (UTC)

Queries[edit source]

When using #ask, for single value properties like Has class, comparators like !, ~ and !~ work to check the value of that specific string, whereas for multiple value properties like Has abilities, comparators work to check whether any of the items on the list fit the bill. What this means is while I can ask for all cards that aren't mage cards, I can't ask for all cards that don't have Taunt, or Charge. Is there another way to achieve this, or is this something that just can't be achieved, like negative category searches? -- Taohinton (talk) 03:21, 21 June 2016 (UTC)

That's a longstanding flaw in SMW. The only workaround I know of for both, unfortunately, would be to create another property. It is awkward, but if we could establish a list of tags, abilities, and categories that we need to negate, I could have Card infobox look for them and add them to, say, Property:Doesn't have tag, Property:Doesn't have ability, and Property:Not in category. If we went ahead with this, it might be useful to just have a separate template for each that has the list. (Probably just be as simple as each one on its own line in the template.) The awkwardness of this hack is, though, that when changing these templates, it might be necessary to poke me to run a touch bot over all card pages afterwards. Even without that, it'd be something we'd want to try to do only sparingly. oOeyes User-OOeyes-Sig.png 21:00, 22 June 2016 (UTC)

Enchantment listings[edit source]

Why does this happen? Even if I search so that's the only thing in the table, it still gets put together. There are separate data pages and content pages (albeit redirects) for each one. -- Taohinton (talk) 23:28, 25 June 2016 (UTC)

A redirect cannot be a content page because it cannot call {{Card infobox}}. If Card infobox isn't called, properties aren't set on the page, so there are no property values to retrieve for that card.
At least, there shouldn't be. There's another longstanding issue in SMW: if you just redirect a page that has property values set, the property values don't get cleared. This is one of those painful bugs they never seem to fix. And now they end up getting mashed together in query results because they redirect to the same page. If you actually do want property values cleared before making a page a redirect, it is unfortunately necessary to blank the page first.
In the past, I've been able to do this retroactively to get the values cleared out, but this is the first time I've had this come up with the redirect equality functioning and the usual tricks aren't responding. If I can't figure another solution, I may be left with no choice but to ask dev to have the SMW tables wiped and rebuilt tomorrow, which will disrupt the wiki for a number of hours. oOeyes User-OOeyes-Sig.png 07:46, 26 June 2016 (UTC)
A scorched earth tactic seems to have done to trick:
  • Deleted the redirect target, Enchantment List, itself.
  • Deleted all the relevant content pages (which was done after removing the redirects, not sure if that step is necessary.)
  • Recreated all the relevent content pages. Did not restore them; literally recreated them placing "{{Card infobox}}" in them.
    • This cost us the page histories, but there was no meaningful history for these pages.
  • Restored Enchantment List, thus preserving the meaningful page history for that one.
After all that, I'm not seeing the abnormal entry returning in queries any longer, so I think this has been fixed without the need for the even more expansive scorched earth approach.
If you really want these to be redirects and preserve the properties to show up in queries, regretfully, the necessary steps will be more involved and tedious:
  1. Move the content page to a different name. Allow the redirect to be created.
    • (Should be safe as the redirect is created as a completely fresh page. Property values should be moved with the original page.)
  2. Edit it to something like the example below.
  3. Then it should (hopefully) be safe to go to the redirect and change it to point to Enchantment list instead.
{{Card infobox
|datapage=Draw Offensive Play(35273)
|targetpage=Enchantment list
}}
I'd recommend doing only one or two as an experiment first, though. oOeyes User-OOeyes-Sig.png 08:27, 26 June 2016 (UTC)

Import request[edit source]

I've posted an import request on the proper page, but wasn't sure if you wanted extra notes added there or not. In this case we are wanting a bunch of new (mostly Tavern Brawl) cards imported, but also new images for a number of cards. We need new golden images for all priest and rogue cards (which have had a style update - the ribbons are white and black, respectively, rather than grey), as well as Innervate, Nourish and Voidwalker. We also need new regular and golden images for Uncover Staff Piece, Staff, Two Pieces, Staff, First Piece, Swordsman and Silithid Swarmer. However, some of these card images have not yet been updated on Hearthpwn, so this might need a separate import when they've fixed them. -- Taohinton (talk) 12:47, 13 July 2016 (UTC)

With the announcement of a new adventure coming out on August 11, it seems like we might as well delay the import until then. The adventure data will be a big import, and really is needed fairly quickly after it becomes available. I'll leave it up to you how best to handle trying to make that happen. -- Taohinton (talk) 15:02, 29 July 2016 (UTC)
I was a bit busy yesterday getting everything set up, but I wanted to say the people responsible did an excellent job of making the import happen as soon as the data was available - so please pass on my thanks to them. Having the data imported within hours instead of days has made it a lot easier to get everything into place. The new system for only updating images for cards with changes also seemed to work very well, and was useful for highlighting those changes. Good stuff!
There is one oddity or concern, which is that the cards added with the previous patch on July 12 were not added with the import. I thought the import worked by adding any cards that were missing, but in this case several missing cards were not added. I can simply add them myself manually, but I'm interested in whether something went wrong or if the import process no longer works the way it used to; this could make things a bit trickier. The cards in question were added with Patch 5.2.0.13619, for example Don't Push Me, Glorious Finale and Bamboozle. -- Taohinton (talk) 07:17, 11 August 2016 (UTC)
I apologize for the long delay in getting back on this. There was an issue with my work email, and I didn't notice right away. Left the reply sitting in limbo without me knowing it was there. >.>
Anyway, now that that's sorted out, they tell me the current process is now to just import new cards from the latest patch. I mentioned the cards you said were missing, and they imported those, but I'm not sure they understood all the cards from that patch were missing. I'm going to poke them again. oOeyes User-OOeyes-Sig.png 02:24, 20 August 2016 (UTC)
Yeah, the other 20 or so other cards weren't imported. However, after waiting since July I actually had to make them up manually a couple of days ago anyway since they have now appeared in-game, although I didn't obtain golden images.
I'm a little concerned about the new system, since it means unless we get an import each patch (which unless things change majorly we definitely won't get) we'll end up missing a lot of stuff. We probably won't miss too much important stuff, and I often have to make the Tavern Brawl cards myself anyway due to the lateness of the imports, but it will be a shame to lose the completeness, and will mean we can't trust the wiki's data collection in the same way. The older system definitely works much better for the wiki. -- Taohinton (talk) 04:36, 20 August 2016 (UTC)

Switching "200px" image redlinks to text links in {{Card}}[edit source]

When using {{Cards}} to provide lists, if a card has no image (but we do have a content/data page) we get a red "200px" link to upload an image. {{Card}} seems to say it will display a text link if an image is missing, and this does happen on occasion, but most of the time we simply get the image redlink. This makes regular {{Cards}} lists unsightly if we have missing images, preventing automation, and causing various problems for us.

We need the text link to be displayed instead of the redlink, when we simply don't have an image for an existing card. Ideally, a 200px width div would allow the cards to stay in alignment when this appears - otherwise everything gets skewed - and also stop the names running into each other. But, if that's not possible, the text link will do. I've had a look at the workings but can't make out where's it's going wrong. -- Taohinton (talk) 22:46, 19 July 2016 (UTC)

I added the 200px div. For a moment, I thought I had solved the rest of this, but rereading what you want, there isn't really any great solution:
  • The usual way to handle this problem is to use an #ifexist check to see if the file is there and output a normal text link if it doesn't, but that's only good for up to 100 images on a page total. oOeyes User-OOeyes-Sig.png 22:49, 21 July 2016 (UTC)
  • The quickest solve-this-problem-now way is probably for me to edit {{Card infobox}} so it doesn't set anything to Property:Has image or Property:Has gold image if the file isn't uploaded, but I think that would add caching issues because I'm not sure uploading the image would actually trigger the properties to update. The content page would probably have to be resaved (or wait for cache to refresh on its own).
  • Or I could ask the Hearthpwn crew to change the importer to work as I originally thought it would. If it didn't add filenames to image or gold_image on the data pages when there's no image to upload, it would already work as you would like. But I haven't even heard back on the import request from last week yet. :(
It's actually kind of an annoying issue. I really wish the built-in link syntax had something for this since it has to check if the image exists anyway, but it's just not there. oOeyes User-OOeyes-Sig.png 22:49, 21 July 2016 (UTC)
The third option definitely sounds best (albeit that isn't really saying much considering the other two options!). Would this work retroactively, or only for new cards? And would it be possible to fix this for the currently image-less cards? Maybe something to poke their way once they do get round to the data import. -- Taohinton (talk) 11:50, 28 July 2016 (UTC)
No, it wouldn't work retroactively since we don't normally import over existing data pages. There would be no harm in removing the filenames from the data pages manually (to avoid any possible confusion, just for those with missing images). Otherwise, I think there may be a way to bot it. My schedule is looking it may be pretty tight for the next several days, though, so I don't have a good ETA to offer on that. oOeyes User-OOeyes-Sig.png 01:29, 29 July 2016 (UTC)
I can probably find all the ones currently missing images myself, but I'm not sure how to remove the filenames? Also does Card infobox convert all : to - in image names due to a technical limitation? It's always a minor annoyance to work around. -- Taohinton (talk) 02:39, 29 July 2016 (UTC)
Oh, *facepalm*. I think I brainfarted and confused this with another setup, as this one is providing an automatic default in {{Card data}}. Okay, since we don't overwrite data pages here on imports, making option 3 work would probably require me to add something like has_image in alongside has_gold, have them add it to the importer, and then add it to all existing data pages. Option 2 might actually be less of a pain at this point. I think either way, we're stuck in a situation where uploading a missing image for a card is either going to require editing the data page to tell it the image is there (option 3) or resave the content page (option 2). And option 2 is ultimately a lot quicker to set up. oOeyes User-OOeyes-Sig.png 03:59, 29 July 2016 (UTC)

Artists tables[edit source]

I'd like to integrate the info for artists into the card data system, so we can have automated listings; at present we have to state the same info three different places for each card! I've added Property:Has artist and started tagging the pages, but I need your help to create a table template for Artists that can list cards by artist, like the ones we have there at present. The lists there are currently pretty huge, but we can split them into card set subpages as we've done elsewhere, which should make them a lot more manageable. However, we currently only have a few dozen cards tagged so this shouldn't be a problem for testing.

One issue is that Blizzard never really bother with consistency, and so we have some artists being called two or three different versions of their name on different cards. We have redirects in place but obviously this won't change what's actually stored in the property, which I assume would be a problem when making a table like this. Is there a way to have e.g. cards by "Alex Alexandrov" and "Alexander Alexandrov" listed together as by the one artist, given that the first page is just a redirect to the second? -- Taohinton (talk) 10:16, 7 August 2016 (UTC)

I've added artist and voice actor to {{Custom card table}}. As for the redirect issue, I edited {{Card infobox}} to put the artist param in the new #follow function when it gets assigned, so if the provided artist name corresponds to a redirect, it'll assign the name of the target page instead. oOeyes User-OOeyes-Sig.png 10:52, 9 August 2016 (UTC)
Excellent, #follow is exactly what I needed for the redirects! However, I think you missed what I was asking for with the tables: if you check out Artists you'll see the (manual) tables there are laid out a bit differently to any current template; most importantly the table gathers all the cards by each artist, making it almost a bunch of link-only tables in one. I'm not sure if this is doable or not as an automated table, or if so whether it might need a different setup to work. -- Taohinton (talk) 11:48, 9 August 2016 (UTC)
Oh. Well, it's doable this way, but the property set up is backward of the optimal set up for these tables. I mean, you'd have one #ask to grab the artists, and then a separate #ask (minimum) for every artist in the list to get the cards. I could try to set it up, but I'd expect it to timeout quite a bit easier than the card tables. Since the tables are artist-centric, not card-centric, the reverse design is much better optimized, say a "Property:Created art on" set on the artist pages instead. That lets the table be constructed with a single query. oOeyes User-OOeyes-Sig.png 13:53, 9 August 2016 (UTC)
Also, it doesn't look like there's a category for the artist pages? I was going to make a quick mockup, but this is kind of a non-starter without a way to get a list of the artist pages. oOeyes User-OOeyes-Sig.png 14:20, 9 August 2016 (UTC)

Caching issue variant[edit source]

I've twice now encountered a variant of the usual caching issue that does not respond to the usual "saving without making any changes" approach, but is fixed as soon as I save any actual change to the page in question. Since this is contrary to the usual rules/advice (and I've never encountered it until recently) I thought I'd mention it. If it's likely to be an ongoing state of affairs I'll amend Help:Missing cards. -- Taohinton (talk) 14:58, 11 September 2016 (UTC)

Setting properties for other pages[edit source]

Is there a way to set a property for a page, from a different page? I've looked over the guidance for #set and the like but can't find any mention of such a feature. I'm considering moving the remaining content on 'token' pages like Mirror Image (minion) over to their 'parent' pages (Mirror Image), but not being able to use {{setartist}} for the token page from the main page is a problem. -- Taohinton (talk) 10:14, 31 October 2016 (UTC)

I'm afraid that's a simple no. You can assign properties only to the page you're editing. The alternative SMW provides is #subobject, kinda like creating a page within a page that has only property values, but that's the rub: only property values, no categories. Thus, they're excluded from any query that looks at a category, which is most or all of ours. oOeyes User-OOeyes-Sig.png 18:54, 31 October 2016 (UTC)

Sound files[edit source]

Since Hearthpwn now hosts sound files for all minion cards, would it be possible to include them in imports from now on? This would be a great addition to our card pages and is the one thing that's missing, compared to Hearthpwn and Hearthhead. Format-wise, Hearthpwn seems to use .ogg, which would be fine. -- Taohinton (talk) 06:16, 15 November 2016 (UTC)

I'm passing along the request to see if they can work that into the process on their own. If so, I'll sort out what needs to happen here. oOeyes User-OOeyes-Sig.png 04:18, 17 November 2016 (UTC)

Main page tweaks[edit source]

We're starting a project right now to review and improve the main pages across Gamepedia. For the first stage here at Hearthstone Wiki, I've just added responsive features to a copy of the current design here, just to make it friendlier when the browser window is narrow. In short, it will collapse into a single column when the screen is sufficiently narrow, and the icons are now capable of wrapping onto a second line. I'd like to go ahead and put that up ASAP since it's a change most people probably won't even notice.

Our community manager has some other adjustments he'd like to see, so I'll be following this up with a fresh mock-up in the near future. oOeyes User-OOeyes-Sig.png 04:28, 17 November 2016 (UTC)

I've never been very happy about the width issues on the front page, so I'm fine with improvements in that direction. It is certainly a very big change on my display, and the downside is the second column bits are mostly empty when shifted down to the bottom. Centralising the video would help a bit. There's also a bug where narrowing down from two columns to one column adds a big chunk of empty space at the bottom of each block (even more so if you expand up from one to two columns first).
I'll be interested to hear what other improvements they have in mind. -- Taohinton (talk) 04:48, 17 November 2016 (UTC)
Looking at it again, I should probably get a little more fancy and set up the right column to fold up into two separate columns once it's been pushed underneath since each one of them has relatively narrow content. I should have time Friday or over the weekend to experiment with that. I think the bug should be fixed regarding the extra space; I missed updating one line of code there. oOeyes User-OOeyes-Sig.png 07:48, 17 November 2016 (UTC)
I was actually going to suggest that, but didn't want to make any more work for you! Sounds good. -- Taohinton (talk) 08:36, 17 November 2016 (UTC)
The new column behavior is now set up on the mockup. oOeyes User-OOeyes-Sig.png 08:09, 18 November 2016 (UTC)
Looks good, and the bug is indeed fixed. -- Taohinton (talk) 13:43, 18 November 2016 (UTC)
I've pushed the responsive version live. Should have more adjustments mocked up in the near future, which I'll link from Project talk:Community portal instead of here when it's ready. oOeyes User-OOeyes-Sig.png 01:50, 21 November 2016 (UTC)

[edit source]

Blizzard have recently reduced the name of the game from Hearthstone: Heroes of Warcraft to simply Hearthstone. They've consequently reworked the logo for the game, including removing the superfluous wording, but also redoing the remaining 'Hearthstone'. It's been pointed out to me that our Hearthstone Wiki logo therefore no longer quite matches the current logo for the game (as seen on the loading screen, the official site, etc).

It's minor, but if you're already planning on doing some presentation tweaks, it might be good to update our logo to match the one now used in the game. You can see the new one here, compared to the old one here - the shape of some of the letters has changed (notably the new long 'R'), there are little nicks/new texture on the letters, there is new lighting, and the 'O' has new graphic effects.

To be clear, we're very happy with the current logo, and are not wanting it to be overhauled or changed in any other way, only for the lettering to be updated if possible. -- Taohinton (talk) 19:11, 18 December 2016 (UTC)

Like most of the graphics in the current skin, that was kicked in to me from our design team. As the needed changes are beyond my graphic design skills, I'll pass the request up, but being so close to the holidays, I'm not even sure I'd get an answer soon, much less an updated logo. oOeyes User-OOeyes-Sig.png 19:39, 18 December 2016 (UTC)

Image files[edit source]

The delay for images to update to the most recently uploaded version goes on; in some cases images updated two weeks ago are still showing the old versions. I've tried everything and for the most part nothing works to speed it along, but I have noticed that in some cases, the card page itself has updated, and the mouse-over tooltip has updated, but {{Card}} is specifically lagging behind. If there's a difference in the mechanisms, the one used by tooltips seems to be superior; upgrading {{Card}} similarly would help significantly. -- Taohinton (talk) 05:51, 19 November 2016 (UTC)

Well, they're separate files:
So that's three separate files getting updated at three separate times. Removing the sizes is the simplest option technically to get them to use the same file. In a day or so (once I can be sure the needed CSS is pushed out), I could modify those templates to push out the full size file instead and resize on the browser side. oOeyes User-OOeyes-Sig.png 01:32, 21 November 2016 (UTC)
That sounds like it would help a lot with speeding up the process; the file itself sometimes still takes a while to update, but the infobox and especially the {{Card}} versions usually lag a long way behind that. That said, presumably there's a reason it was set up that way - will the change mean sacrificing loading speed/other functionalities? -- Taohinton (talk) 05:37, 21 November 2016 (UTC)
I think the developers were probably thinking more along the lines of, say, 1200px images being resized to 300px, and why send that much data if most will only see it at 300px? If the 1200px version is rarely viewed, then yes, this is a good optimization. The way card images are being used on the wiki doesn't work out that way, though. The resizing is by very small amounts, and users are more likely to end up viewing two or three versions, so for this particular case, it actually makes things worse: three versions in our image cache on the server and three versions in your browser cache. If it'd occurred to me before that this was happening, I'd probably already have optimized it away. oOeyes User-OOeyes-Sig.png 08:02, 21 November 2016 (UTC)
Only one concern then: Will making the browser do the resizing work itself make big pages like Whispers of the Old Gods with hundreds of images load significantly slower? These already take a fair while for all the cards to appear (at least on my humble setup). Most pages don't have so many cards displayed, but the main expansion ones do, and those are some of our most popular pages.
A related question: All card images imported since around March this year appear jagged, and their writing and shapes distorted, when viewed at either 200 or 184px. You can see some good examples here: the non-updated images shown are notably smooth and blended in comparison. The issue doesn't seem to be in the base images though, but in the other size versions. Are the new versions somehow not optimised for these sizes, or is it that there's been some change to the behind-the-wiki magic in that time, and the non-updated images are simply still using the old versions? Is there anything that can be done? Obviously this ties into the first matter a bit. -- Taohinton (talk) 11:24, 21 November 2016 (UTC)
Yeah, the file sizes do have a fairly big jump, so that would be an issue. One example is 96k up to about 160k. For now, I'll just change Card infobox to use the 200px images. That may help a little with the caching issues. The quality issue is probably due to the change in the image library some time back. It seems to use a faster but lower quality resize. :( oOeyes User-OOeyes-Sig.png 08:57, 22 November 2016 (UTC)
Yeah, looking at the differences in the file sizes that might be a bad move for the big pages, but yes the change to the infobox should help a little at least. Is there any way I can force a refresh of the 200px version of a given image? Wouldn't need to do it too often, just for a few problem cards. Re: the image library I take it there's nothing we can do about it? It's mostly a small loss of quality but across the whole site it adds up. -- Taohinton (talk) 16:15, 22 November 2016 (UTC)

Collapsibles[edit source]

We've started using collapsible divs in certain places to help navigate lengthy lists (eg Card back), as well as to hide specifically optional stuff (currently just Wild format cards, eg Put into hand#Cards). They're very handy, but the interface is a bit clunky.

Ideally rather than having a central caption and then a little orange link at the very right, it would be great to simply have a "Click to view X" caption which served as the 'expand' button itself; and likewise changed to "Click to hide X" when expanded. Is this something that would be doable? If having a user-defined caption is tricky, a generic "Click to [view/hide] section" would be fine. -- Taohinton (talk) 21:01, 6 December 2016 (UTC)

Unfortunately, it looks like I'd have to write something custom. At least, the documentation on mw-collapsible isn't showing anything like this. While it isn't particularly involved, this is catching me in the middle of a move and without steady internet access, so I'm not sure when I'll be able to get to this. oOeyes User-OOeyes-Sig.png 03:51, 7 December 2016 (UTC)
Just a reminder that this would be appreciated when you get the time. Hope the move wasn't too stressful! -- Taohinton (talk) 00:43, 3 February 2017 (UTC)
Apologies for the long delay on this. It slipped my mind, and now I'm churning through a backlog, but I'll try to slip this in within the next few days. oOeyes User-OOeyes-Sig.png 18:20, 7 February 2017 (UTC)
I tried to keep it pretty close to how mw-collapsible works, but there is a difference in how you add text to the link. You can see it in my sandbox currently, but basically, it's just an extra attribute on the div, like this:
<div class="hw-collapsible" data-text="the content below">Content</div>
Content
oOeyes User-OOeyes-Sig.png 10:23, 13 February 2017 (UTC)
Excellent! One thing: could you set the 'Click to hide the content below' (etc) text to <big> or equivalent; that's how we had the previous divs set up and it helps the zipped sections to stand out. -- Taohinton (talk) 09:30, 15 February 2017 (UTC)
I know you have your hands full with style matters at the moment, but if could find the time to make this change that would be great - then I can get on with switching the current divs over. -- Taohinton (talk) 16:54, 28 March 2017 (UTC)
I think the style change I just made should be equivalent. oOeyes User-OOeyes-Sig.png 06:52, 29 March 2017 (UTC)

Login problem[edit source]

I'm unable to login to this wiki. I am sent to Special:UserLogin which then sends me automatically to and after I go through the process of login I'm sent back to the initial Special:UserLogin .

I went to and did the login there - it works. I then went to other wikis (wow.gamepedia.com and fallout.gamepedia.com) and everything works just fine - I am logged in, I can edit, I can delete, etc.

I tried to logout and do the login from other wikis - it works for the other wikis.

But, still, nothing works in  ! I'm still being redirected to Special:UserLogin .

77.54.209.65 22:26, 2 March 2017 (UTC)

And I had to remove the URLs, otherwise it wouldn't let me save the page.
77.54.209.65 22:27, 2 March 2017 (UTC)
Logins should be redirecting you to www.gamepedia.com now. Once you're logged in on one Gamepedia wiki, it should automatically log you in to others immediately by just clicking "Sign in" at the top; you won't need to enter your username and password again. If this isn't happening, I'd recommend trying to clear your cookies as something there may be causing trouble with the new login system. oOeyes User-OOeyes-Sig.png 02:04, 3 March 2017 (UTC)
I've done all there is to do. I re-checked and it's still the same shit - out of around 10 wikis, only this one doesn't work (like you describe).
Meanwhile, in terraria.gamepedia.com

Gamepedia wikis are currently experiencing technical issues related to the recent login changes. Some user accounts may currently be stuck in a login "loop" on certain wikis, and some users' editing, recent changes, and watchlist preferences may be reverting to their defaults. Gamepedia is aware of these problems, and is working to correct them.

77.54.209.65 02:32, 3 March 2017 (UTC)
Did you try resetting your app cache + local storage? Aegonostic (talk) 02:36, 3 March 2017 (UTC)

Standard year bot run[edit source]

As one of the last tasks on my list before I disappear, we need a bot run for these cards to swap the Category:Standard format cards call to Category:Wild format cards. Thanks for all your help, and take care! -- Taohinton (talk) 18:58, 5 April 2017 (UTC)

Bot job is kicked off and running. oOeyes User-OOeyes-Sig.png 08:44, 7 April 2017 (UTC)

New user can't edit[edit source]

A new user just posted on my talk page that they were blocked by an "abuse filter" when trying to edit. They have no edit history, aren't blocked that I can tell, message they quoted looked like it had no reason to be blocked, so I'm at a loss. If anyone would like to take a look, here's the link: User talk:Jerodast#Abuse Filter

Thanks! - jerodast (talk) 05:31, 10 April 2017 (UTC)