Guild Wars 2 Wiki:Reporting wiki bugs

From Guild Wars 2 Wiki
Jump to navigationJump to search
Please report all bugs found on Guild Wars 2 Wiki here.

This page is NOT for reporting game bugs, those should be reported at the official forums.



This page is used to report bugs with the wiki, this does NOT cover in-game issues.

  • If you are experiencing an in-game bug or issue that requires technical support, check the Guild Wars 2 official forums.
  • If you are experiencing difficulties getting past a specific part of the game, please use the "Search" box on the left to find the specific quest, mission, or region that you are finding difficult. You can review any tips on that page, and discuss it on corresponding talk page if more help is desired.
  • If you have a problem with contents of a wiki page, use the associated talk page.

Please review existing bug reports before creating a new one, these will be listed below. If you add a bug not related to the wiki (such as a bug in the game itself), the report may be removed with no actions taken.

When reporting a new bug, be sure to provide a description of the problem, your wiki username, any error message received, and any additional comments that may help someone reproduce and troubleshoot the suspected bug.

Key: Yes = Solved, Yes = Mitigated, No = Unsolved, No = Not a bug

Yes Semantic query: Printout skips data[edit]

See /archive 12#Semantic query: Printout skips data for full description.

Long term issue. Awaits https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/5036 which didn't make it into the release of SMW 4.0.0.

Mitigated by edits such as this one. -Chieftain AlexUser Chieftain Alex sig.png 12:47, 11 September 2022 (UTC)

Still happening as reported on Template talk:Trait list#Traits not displaying some elite specs correctly. -Chieftain AlexUser Chieftain Alex sig.png 17:35, 4 April 2023 (UTC)

Yes Mobile theme when viewed on desktop - not loading custom css at all[edit]

See /archive 12#Mobile theme when viewed on desktop - not loading custom css at all for full description.

Considered mitigated through javascript in Mobile.js, Common.js, and Minerva.js. -Chieftain AlexUser Chieftain Alex sig.png 12:47, 11 September 2022 (UTC)

Yes Widget counter bug[edit]

See /archive 12#Widget counter bug for full description.

Mitigated by removal of smarty counter logic from majority of widgets. -Chieftain AlexUser Chieftain Alex sig.png 11:07, 4 December 2022 (UTC)

No Empty or incomplete SMW queries[edit]

Description
Problem
  • The recent SMW upgrade to version 4.0.2 reset the whole database and therefore the queries asking for those properties may be empty. Hence you might see something like: "This item is not contained in any container." or "No results for sold by."
How to fix it
  • This can be fixed by using the Purge button on the top (only visible to logged-in wiki editors) or by adding ?action=purge in the address bar.
    • First, make sure that the properties on the wanted pages are stored correctly by purging the pages. Therefore, go to the pages that should be shown in query (obviously for large queries this is a non-trivial task, sometimes Special:WhatLinksHere can help).
    • Second, purge the page with the query.
    • In most cases this should fix it, if not feel free to report it here.
Example
  • Let's say we are on the page Mithril Ore and the section Contained in isn't showing the container Large Loot Bag.
  • First, we go to the page Large Loot Bag and hit the purge button to properly set the SMW properties.
  • Second, we go back to the page Mithril Ore and again use the purge button.
Notes
  • Sometimes SMW queries are self-referencing and relying on properties of their own page, then one has to purge twice.
  • Alternatively, one can also use a mw:Null edit to purge the page (simply click edit and then save changes without performing any edit, note that you won't show up in the page history) or even combine a purge and a null edit to be sure that the properties and queries are working as intended.

I combined all SMW related bug reports in this section. --Tolkyria (talk) 09:11, 28 September 2022 (UTC)

Perhaps it may be a good idea to add to the message on every page that "If you experience problems, purge the page (twice max) to see if that solves the problem. If not, please report it ander Article Feedback" or something alike. I keep running into pages that fixed themselves after a purge. Disconnect (talk) 02:05, 30 September 2022 (UTC)
While this is the way to fix these problems, we do not currently recommend it openly to not waste anyones time since pages can "break" again due to the issues detailed in the next section ("Unparsed pages after null edit"). —Kvothe (talk) 22:27, 2 October 2022 (UTC)
Note this is probably still an ongoing issue, but I've archived many of the repetitive bug reports to Guild Wars 2 Wiki:Reporting wiki bugs/archive_12#Empty or incomplete SMW queries (not useful to display them all here).
  • Gallery view of weapon skins in a collection only shows some of the available pictures
  • API widgets broken on Open Skies achievements pages
  • Containers for items not showing
  • Queries not working?
  • Item References
  • Expression error: Unrecognized punctuation character
  • Missing acquisition sources for some LWS3 items
  • Ascended Breathers
  • Personal Story not loading/highlighting from API correctly
  • Weaponsmith/Novice recipes
  • Missing pages for database items - Destroyer Weapons
  • Why has the purging not been done automatically as part of the software update process?
Please however continue to create topics with === heading text === to report further bugs. -Chieftain AlexUser Chieftain Alex sig.png 00:16, 30 November 2022 (UTC)

December 2022[edit]

This bug is still occurring. There have been several reports on discord of pages losing their semantic properties. This is most observable where recipe pages "forget" their subobjects, and then the recipe list templates report fewer than expected recipes. -Chieftain AlexUser Chieftain Alex sig.png 11:07, 4 December 2022 (UTC)

It was reported by User:Greener that the number of empty queries seems to have reduced. This could be related to a patch applied on 17th January (although at first glance none of the changes look related). -Chieftain AlexUser Chieftain Alex sig.png 17:37, 25 January 2023 (UTC)

May 2023[edit]

Still happening. Found API:2/account/legendaryarmory without properties, purged to resolve. Also found the same on Seitung Province yesterday. -Chieftain AlexUser Chieftain Alex sig.png 22:19, 29 May 2023 (UTC)

No "|+order=" not sorting as expected[edit]

When looking at the currency for table on Imperial Favor, the sorting seems to sort the "250 Research Note" & "125 Imperial Favor" and "300 Research Note" & "150 Imperial Favor" entries in the order as just listed here, instead of the other way around, as'd be expected given the |+order=asc found in the {{vendor query table}}.
I can give the following queries/tables as more minimal examples (compared to the aforementioned template):

Has item cost
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
20000 (Imperial Favor)
500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
Has item cost
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
20000 (Imperial Favor)
500 (Imperial Favor)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
Has item cost
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
20000 (Imperial Favor)
500 (Imperial Favor)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)

The first table should have the costs sorted ascendingly by amount (i.e. as should also be the case in the table on the linked page). The further two tables are included for reference, where the costs should be sorted descendingly by amount and are unsorted respectively.
I'm guessing that this is a SMW bug. Nightsky (talk) 14:23, 22 October 2022 (UTC)

Can you clarify what you think the |+order= parameter is supposed to do? Is it supposed to sort the records returned within a single table row? -Chieftain AlexUser Chieftain Alex sig.png 08:35, 23 October 2022 (UTC)
I think it's supposed to sort the individual instances assigned to a property. (So, yes, it should sort the records returned within a single table row in the tables above. (For tables with more columns it'd of course be within a cell instead of row then.))
As a more elaborate example; considder e.g. the following assignment:
{{#subobject: example
| Has item cost = 250;Research Note+125;Imperial Favor |+sep=+
}}
This'll set "Has item cost" to two instances of the record; "250 (Research Note)" & "125 (Imperial Favor)".
Now if asked for this to be sorted in the output, it should sort these instances as specified. Considder e.g. the following query:
{{#ask: [[{{FULLPAGENAME}}#example]]
| ?Has item cost |+order=asc
}}
This should then yield "125 (Imperial Favor)" & "250 (Research Note)", in this order; sorting first by the first property in the record in ascending order and then by subsequent ones if neccessarry (though i don't think there exists a way to specifiy the sort order for record properties other than the first, so it sorting by subsequent ones may not be the case; although it does appear to work that way (See e.g. Legendary Insight#Currency for, Gift of Prowess#Sold by and Gift of Compassion#Sold by; which do seem to order ties in the first property by the next.)).
The weird thing is that it doesn't even seem to be sorting alphabetically, as otherwise 250 & 125 and 300 & 150 wouldn't always be the other way around as 1000 & 2500.
Another weird thing is that the table with the unordered records above appears to have them ordered by the second property of the record, Imperial Favor & Research Note, in that order; though i suppose that may be coincidence with them all being assigned in that order in the "vendor table row"-template on the vendor page. Nightsky (talk) 14:46, 23 October 2022 (UTC)
Did yoy see my test at User:Chieftain Alex/sandbox? -Chieftain AlexUser Chieftain Alex sig.png 15:22, 23 October 2022 (UTC)
I don't really look at pages in the user namespace unless being pointed at or pinged there, so i did not; untill reading your messages at least (which are more descriptive of the test than your message here if i may add).
I'm afraid your test still leaves 2500 & 1000 in an undesirable order, though it does seem to do fine with 125 & 250 and 150 & 300 (as well as all the pairs of different digit length); so it's certainly an improvement.
Also, since you made me check the documentation, i found that there's also n-asc and n-desc, which do seem to work as a workaround. See also the following tables:
Has item cost
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
20000 (Imperial Favor)
500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
1000 (Research Note), 2500 (Imperial Favor)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
50 (Imperial Favor), 100 (Research Note)
75 (Imperial Favor), 150 (Research Note)
125 (Imperial Favor), 250 (Research Note)
150 (Imperial Favor), 300 (Research Note)
Has item cost
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
200 (Imperial Favor)
20000 (Imperial Favor)
500 (Imperial Favor)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
2500 (Imperial Favor), 1000 (Research Note)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
100 (Research Note), 50 (Imperial Favor)
150 (Research Note), 75 (Imperial Favor)
250 (Research Note), 125 (Imperial Favor)
300 (Research Note), 150 (Imperial Favor)
Nightsky (talk) 17:22, 23 October 2022 (UTC)
I think the goal should be sorting alphabetically by the name of the cost item, not the cost amount. That way the cost column will be consistently ordered throughout the entire vendor table. So I think Alex's solution is ideal. --BuffsEverywhere (talk) 18:19, 23 October 2022 (UTC)
To be honest, that's nothing really new. SMW records are extremely unhandy to use, one can neither return them in plain format with the suffix # (e.g. plain number format for currencies, that's why we had #replace/dplreplace for some time to get rid of thousand seperator, later switched to text property), nor use the suffix |+order properly (applies to first record field only), nor use something like |+limit or |+offset (there it get's extremely strange, at least the last time I tried it). Furthermore, although text properties are sorted numerically due to Guild Wars 2 Wiki talk:Requests for technical administration#Sorting pages with numbers, this doesn't apply to record fields when using |+order=asc (|+order=n-asc works though). Hence one can't also use numerical comparison operators on record fields (such as > greater equal, >> greater, < and <<), these are still using string comparisons which returns numerical nonsense results.
Alex solution isn't sorting alphabetically, it's just displaying how it is stored in the vendor table row. The only way to sort it alphabetically would be to swap the properties of Has item cost to Has item currency, Has item value (which at this point would be insane to do) to get the currency in the first position and then use |+order=asc.
Also sorting numerically by the currency value makes no sense, for example try, it returns a different currency order for different items:
{{#ask: [[Sells item.Has armor set::Triumphant Hero's armor (light)]]
| ?Sells item
| ?Has vendor
| ?Has item cost|+order=n-asc
| class = wikitable sortable mw-collapsible mw-collapsed
| format = table
| mainlabel = -
}}
So I think right now the best is to leave it as it is and use the original subobject order which relies on the wiki input. --Tolkyria (talk) 18:51, 23 October 2022 (UTC)
I'd have managed to suggest reversing the order of the properties in the record and point out that Alex's table is like sorting the unsorted table above by clicking on it's header, albeit lacking the subobject column, but that'd have been about it; so i'm glad that you pitched in with all the additional information.
One thing i'll have to contest though is that the results are returned in the order they were set, as i don't think that's guaranteed to be the case. (Hence me using coincidence above, since i think it is one. (Which is unfortunate; would have certainly be a simpler solution than reversing the properties of the record.)) To give an example; it has been pointed out that the currency order in this table was a jumbled mess (before the order was specified), even though they all were set in the same order on the vendor pages or the templates thereon, as applicable. See e.g. the following query, where the first entry has the currencies the other way around as they are specified, at least at present:
SubobjectHas item cost
Portable Magnetite Shard Exchange/Bastion of the Penitent#vendor5250000 (Coin), 25 (Legendary Insight)
Portable Magnetite Shard Exchange/Salvation Pass#vendor6025 (Legendary Insight), 50000 (Coin)
Portable Magnetite Shard Exchange/Spirit Vale#vendor5325 (Legendary Insight), 50000 (Coin)
Portable Magnetite Shard Exchange/Stronghold of the Faithful#vendor5725 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Bastion of the Penitent)#vendor9125 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Salvation Pass)#vendor9925 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Spirit Vale)#vendor9225 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Stronghold of the Faithful)#vendor9625 (Legendary Insight), 50000 (Coin)
And, yes, n-asc wouldn't make sense everywhere, but it'd have been something easily possible; though i'd prefer sorting by name first as well. I agree that it'd not be a good time to do it now though, given the still fragile state of the wiki. I'm rooting for ArenaNet to figure out and fix what's wrong in the near future. Nightsky (talk) 15:01, 24 October 2022 (UTC)
Actually, i think it was this table instead. So the following query applies more:
SubobjectHas item cost
Portable Magnetite Shard Exchange/Bastion of the Penitent#vendor5225 (Legendary Insight), 50000 (Coin)
Portable Magnetite Shard Exchange/Salvation Pass#vendor6025 (Legendary Insight), 50000 (Coin)
Portable Magnetite Shard Exchange/Spirit Vale#vendor5325 (Legendary Insight), 50000 (Coin)
Portable Magnetite Shard Exchange/Stronghold of the Faithful#vendor5725 (Legendary Insight), 50000 (Coin)
Qadim's Portable Magnetite Shard Exchange/Exchanges#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Qadim's Portable Magnetite Shard Exchange/Exchanges#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Bastion of the Penitent)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Bastion of the Penitent)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Bastion of the Penitent)#vendor9125 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Gaeting Crystal)#vendor1121 (Legendary Insight)
Scholar Glenna (Hall of Chains)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Hall of Chains)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Mythwright Gambit)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Mythwright Gambit)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Salvation Pass)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Salvation Pass)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Salvation Pass)#vendor9925 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Spirit Vale)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Spirit Vale)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Spirit Vale)#vendor9225 (Legendary Insight), 50000 (Coin)
Scholar Glenna (Stronghold of the Faithful)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (Stronghold of the Faithful)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Scholar Glenna (Stronghold of the Faithful)#vendor9625 (Legendary Insight), 50000 (Coin)
Scholar Glenna (The Key of Ahdashim)#vendor31 (Cube of Stabilized Dark Energy), 1 (Eldritch Scroll), 25 (Legendary Insight), 50 (Obsidian Shard)
Scholar Glenna (The Key of Ahdashim)#vendor41 (Gift of Complex Emotions), 1 (Gift of Desert Mastery), 6 (Ball of Dark Energy), 150 (Legendary Insight)
Sorry about that. I think i got the tables mixed up. Nightsky (talk) 16:19, 24 October 2022 (UTC)
Fair, you got me there, I wasn't precise enough. I hope this one is correct: if you don't specify a property printout |+order, then multiple property values are returned in the internally specified order. For some reason the internal order may not rely on the specified wiki order. The internal order can be viewed when using Browse properties and navigating to the subobject by clicking the eye icon. However, I have no clue how this happened in your example with Portable Magnetite Shard Exchange/Bastion of the Penitent#vendor52, even checking the history yields no reasonable result how this could have happened.
A different approach, that at least could be reproduced, to mess up the property order (haven't tested it today, I hope it still applies):
  • Set the property values A, B and C to one property. In general the property would store "A, B and C" for this property.
  • Remove property value A, then in general the property would store "B and C".
  • Readd property value A, since B and C are already set, they are ignored and the property would store "B, C and A".
This might partially explain currency order mismatches, however, I'm not sure if this still holds after a complete SMW database reset.
--Tolkyria (talk) 17:50, 24 October 2022 (UTC)
All i can tell you for sure on that is that i don't have a counter example to it.
I've no clue how it could have happened there either. I have a wild theory though, in that it may sort them by some hash of the values, that for whatever reason may include the subobject name, that just happens to make them sort the other way only on that page. Also another one, in that it might be that way due to one of the currency pages not being known to SMW at one point, due to it sometimes seeming to forget at the moment, at that having stuck with that one page.
If that works to have them scrambled then that makes it seem like there are some tests SMW does to determine already existing property values, not recreating them, likely having them retain insertion order; then just returning them in that order later. Nightsky (talk) 18:59, 24 October 2022 (UTC)
Is this an actual bug? I don't recall any SMW documentation indicating that records can be sorted. -Chieftain AlexUser Chieftain Alex sig.png 11:07, 4 December 2022 (UTC)
Call it whatever you want, bug, anomaly, or the SMW devs actually never cared or thought about this behaviour. However, it's definitely nothing we can fix from our side (except adjusting our records which might be an insane task to do). Maybe we could add a small note to Guild Wars 2 Wiki:Semantic MediaWiki, otherwise I would suggest to mark this topic as resolved.
For me the conclusion of this topic is: The datatype record in fact can be sorted in property printouts with the suffix |+order=asc/desc/n-asc/n-desc, however only in the first record property field. Using the suffix # to return a plain format (e.g. for numbers to suppress the thousand separator) is not possible. --Tolkyria (talk) 12:38, 4 December 2022 (UTC)
According to the documentation +order= datatype support is all datatypes, which records are a part of, which would make it seem as that they should indeed support sorting. And while n-asc and n-desc seem to work, the sorting of asc and desc remains inconsistent, since it's neither string ordered throughout nor numerically ordered throughout; though it seems to be ordered in some way consistently, in that using asc in place of desc or vice versa reverses all entries seemingly reliably (based on the first two of all of the tables in this section; which may not present an exhaustive dataset); which is something i'd say makes it bugged.
This may mean that sorting by name when the properties of the record are reversed would also be affected in some way.
And if reversing the properties would be to insane to do, i guess using n-asc and n-desc in favour of asc and desc would have to do. Nightsky (talk) 00:15, 7 December 2022 (UTC)

Yes Food page filters broken[edit]

The filters on the food page are broken.

https://wiki.guildwars2.com/wiki/Food

Need a bit more info on this, I adjusted the filter code a few days ago, but it appears fine to me.
Q1: Does the box containing the filter buttons load? Do those buttons have icons?
Q2: If the buttons do load, which one are you clicking? What happens and hiw is that different to what you expected? -Chieftain AlexUser Chieftain Alex sig.png 18:07, 22 February 2023 (UTC)
Sime was encountering an issue which looks to appear as "mw.loader.using is not a function" within the javascript console.
I've moved this block of code to the end such that the filter function will still work even if the above error appears (the buttons will look like they have unparsed wikicode). If I can figure out how to avoid the error entirely, I'll put another patch in. -Chieftain AlexUser Chieftain Alex sig.png 21:04, 22 February 2023 (UTC)
Have you considered adding something like this? Nightsky (talk) 15:41, 23 February 2023 (UTC)
I'm not sure that works, but we can try it. -Chieftain AlexUser Chieftain Alex sig.png 17:23, 23 February 2023 (UTC)
For what it's worth; that suggestion is based on a previous report/occurence on/of the same error some time ago, according to which at least it should. Nightsky (talk) 21:02, 23 February 2023 (UTC)
Trying it on the mainspace version. Any comments, feed back here please. -Chieftain AlexUser Chieftain Alex sig.png 18:32, 24 February 2023 (UTC)
I'd have added it to the existing defer method in order to not introduce another method (and having to find a name for it) personally, but the method you added looks fine to me. Nightsky (talk) 00:02, 25 February 2023 (UTC)
Yeah this way is a bit ugly with two deferred methods, however it renders the buttons as fast as possible with this method, and only waits on the MW bit for the retrospective addition of button text. -Chieftain AlexUser Chieftain Alex sig.png 14:34, 25 February 2023 (UTC)

Skill filters broken[edit]

Seems like this might be a similar issue. On many skill and trait pages (some examples: Leap, Teleport, Retreat, etc) the filter does not work. I found one that works (Evade), and the pages that do not work show multiple errors in the console. ~Sime 15:15, 14 July 2023 (UTC)

Template hadn't been updated (I wasn't aware of its existence), not really a "wiki" bug. -Chieftain AlexUser Chieftain Alex sig.png 15:33, 14 July 2023 (UTC)
Yeah I checked related changes and did not see anything indeed, but it was reported on the discord so I wanted to report it here as well. ~Sime 15:39, 14 July 2023 (UTC)

Yes File upload size limit[edit]

Probably not technically a bug, but Special:Upload presently states the maximum permited file size as 2 MB instead of the previously allowed 8 MB. Nightsky (talk) 19:51, 21 March 2023 (UTC)

That's odd. I'll take a look. Justin Lloyd (talk) 20:06, 21 March 2023 (UTC)
This should be fixed now. Justin Lloyd (talk) 20:45, 21 March 2023 (UTC)
I can confirm that it works. Thank you! Nightsky (talk) 23:32, 21 March 2023 (UTC)

No Reference previews[edit]

Reference previews only appear when logged out, but not while logged in. And, not sure if related, but in case it helps: Attempting to turn of the media viewer using the gear shown when viewing a file while logged in doesn't actually turn of the media viewer (nor change the acompaning setting for it the preference settings (Which is where the gear found in Page previews goes to (Special:Preferences#mw-prefsection-rendering) while logged in, while providing options to toggle Page previews and Reference previews individually instead while logged out.) accordingly). Nightsky (talk) 14:48, 3 May 2023 (UTC)

Missed item name in mouseover preview[edit]

Mouseover on "normal" references like Divinity's Reach shows the name of the object or location as a part of page preview. Typical article begins with the description where the name is mentioned in first few words; as a result is is shown in the preview. However, for many items the description in their articles is missed, at most they include a citation with in-game description. While it's not a problem for article itself, it creates a problem for preview because the name of an item is usually missed in such citation.

For example, Charm of Brilliance article doesn't have a specifically written description, it's not required there. But when we look at the article with reference to this charm, we may get a problem. The table in the Recipe: Relic of Evasion article shows only the icon of this charm in the "Cost" column, but not the name. When we try to find out its name by mouseover, we see only the in-game description of a charm, like any other charm, that's all.

How to fix: if the "common" text description is empty and the in-game text is shown instead in preview, add the name of the article (= item name) in the first line, for example:

Charm of Brilliance
Used to craft runes. — In-game description

--213.248.166.94 11:53, 19 November 2023 (UTC)

No Wiki brightness changed recently[edit]

So viewing any page on the wiki affects my browser brightness or contrast. I am able to mitigate somewhat by using mobile view and starting to search, but loading any page really up the brightness. It can't only be me, but seems like it is, or it would be resolved by now. The error is recent, and very obvious. Same thing in an inprivate Edge browser and my usual Chromium.

-86.21.43.57 23:51, 27 February 2024 (UTC)

I haven't modified any of the CSS recently. Can you provide a screenshot? I'm unable to reproduce this in Edge, Chrome or Firefox. -Chieftain AlexUser Chieftain Alex sig.png 23:53, 27 February 2024 (UTC)

Sorry, I have recreated the issue on another site. I just happen to use this one a lot ;). Local issue. Thanks for taking the time to read and reply. Please delete. Further edit: It is linked to HDR apparently, but I didn't get further than reinstalling my GeForce driver and it's resolved.