Various observations on how the wiki behaves and possibly some bugs too.
diff
- Can't see anything significant in the release notes.
- Not mentioned in the release notes, may have been changes to the associated skin instead of the actual MW package: Lots of CSS rules in monobook had a
body:not(.skin--responsive) prefix added to them. Vector amended yet again.
- The script which adds the "Leave article feedback" button will need amending to insert a span element inside the a element with the link in it.
- Bugs
- Low impact: Not sure if intentional, but a purge button appears on all special pages.
- CSS
- mw:Reading/Web/Desktop Improvements/Features/Visual Refinements
- Ideally would adjust how the clock is printed, within a span instead of just within an "a" element.
- Vector 2010 skin with "use legacy vector" UNTICKED and responsive mode UNTICKED; change in the way the elements are laid out in the skin means need to rethink how the ArenaNet triple link upperbar is located - suggest adding directly beneath the body element to make use of absolute positioning (relative to body).
- SMW
- Changes from version 3.2.3 to 4.0.2
- Vector amended yet again. CSS classes renamed (vectorTabs, vectorMenu, the drop down menu). Elements reordered.
- Broken stuff (desktop)
- Broken stuff (mobile)
- Mobile view JS doesn't immediately seem to be firing. All the embellishments we added to the mobile menu are gone. Ah it's a javascript error "menuData is null". Yes they seem to have removed the useful menu property. I'll see if i can find the fix. mw:Extension:MobileFrontend/MobileMenu.
- Will need to remember to edit the spanish wiki's mobile menu too when this breaks.
- Slight CSS tweaks required to remove opacity on the site name and change the CSS class for the "burger" menu.
- MW
- Seems ok, no more errors than previously reported on GW2W:BUG. 1 fixed (smw property processing error). 3 outstanding.
- New little indicator in the top-right when loading pages, pushes the LWS3/4/5 notification marker out of the way whilst loading but ok when finished.
- (Why have we still got modern/cologne blue skins available... grr)
- FWIW, I ran a query and there are around two thousand accounts set to use those two skins. Justin Lloyd (talk) 19:30, 18 March 2021 (UTC)
- They are nowhere close to being customised for this wiki. I would even lean myself out the window and say that there would be community agreement to remove them. —Kvothe (talk) 20:16, 18 March 2021 (UTC)
- Not much noise in the browser console, only one entry.
- Resource not found: "[...]src/mediawiki.skinning/images/magnify-clip-ltr.svg" - Looks like some kind of common icon normally found in the equivalent to this folder - maybe check what's in the 1.35 version you've used? Repeat this issue by visiting the page The Mists.
- Alex, this seems to only be a problem when not logged in, logging in eliminates the error. For some reason, the request when logged out starts with /wiki/Resources/..., but it is /resources/... when logged in. FWIW these images are distinct from the uploaded stuff, this is part of the MediaWiki distribution and stored under the top-level "resources" directory. I'm not sure what's causing this difference right now and so far it only seems to be for this one SVG ltr (left to right) resource image. Justin Lloyd (talk) 19:30, 18 March 2021 (UTC)
- Odd, i was logged in when i experienced that resource bug :S -Chieftain Alex
19:49, 18 March 2021 (UTC)
- I also had the impression it was skin-related, possibly between the new and legacy Vector skins, but I couldn't seem to confirm this. Justin Lloyd (talk) 19:59, 18 March 2021 (UTC)
- Extension- Semantic MediaWiki 3.1.6 → 3.2.2
- Might fix the outdated data problem on Property:Has location type - looks like it works now.
- I see a few namedargs fixes, maybe tree is fixed?
- Special:Browse has a few more section dividers but nothing significant.
- Nothing interesting in the changelogs.
- Extension- Page Forms 4.9.5 → 5.1
- Fixes for the jQuery UI log messages we've been receiving for over a year
- Good.
- Extension- MobileFrontend 2.1.0 → 2.3.0
- No tangible history because it uses hideous gerrit.
- Back-end
- Sysops cannot edit the user interface pages (JS/CSS). 1
Fix identified: The four user rights identified on Guild Wars 2 Wiki:Interface administrators need adding to the sysop group OR provide sysops with the Interface administrator rights.
- Additionally it may be required (e.g. if a message along the lines of "the current content model does not allow this page to be edited" appears) to use Special:ChangeContentModel twice before editing the CSS.
- Default parameter for smw #show: and #ask: functionality has changed (see below). 1 Purge all associated pages.
Need to identify a working fix. (github thread with an insufficient fix)
- Missing stuff
- 0
"MediaWiki no longer has a 'JavaScript-powered' wikitext toolbar built in. The old "bulletin board style toolbar", known as "the 2006 wikitext editor", has been removed, and instead sysadmins will be required to choose one (or more) of the several extensions available for this purpose if they need the functionality."
- No bold/italic buttons - suspect this is to steer people towards visual editor. Could be recreated with a common.js script.
- Broken stuff
- All widgets using jQuery are broken; (ReferenceError: $ is not defined)
1 Fix identified by poke. Help:Widgets example syntax updated, all widgets using jquery will require updating. Can't be done in advance of upgrade due to lack of forwards-compatibility. Can however identify which scripts will need updating. Fix is as follows:
Replace the RLQ line with RLQ.push(['jquery', function () { and replace the final line with }]);
- Widgets using non-protected data subpages need to be moved to the MediaWiki or User/.js namespaces. (ref)
- [[Widget:World map/data.js]] - workaround, apply admin protection to data subpage. 1
Protected. Will be removed with later MW update and require moving (ref)
- Event timer deprecated modules.
- Embed jquery UI elements 1 Fixed.
- SMW
sep=; needs replacing with valuesep=;. 1 Fix identified. Cannot be done in advance due to lack of forwards-compatibility. Can however identify which templates will need updating.
- Change to the default parameter response for #show: and #ask: 1 This appears to be a bug. If the page exists but the property does not, it returns
blank {{Expansion depth limit exceeded}} instead of the default parameter given.
- Template:Weapon infobox e.g.
{{#show:Inquest weapons|?Has canonical name|default=Inquest weapons}}
- Template:Effect icon and almost everywhere.
- This can be fixed by performing a null edit on the pages+related pages affected.
- format = ol/ul,
columns = x has been removed. Supposed to use CSS apparently. Should be able to fix this before migration.
- Template:Member list, Contained in, Gathered from, Salvaged from, Contains upgrade component, Armor set containers. 1 All fixed.
- 1
userparam = xyz when referenced from SMW result templates will now be called "#userparam" (i.e. any template referring to userparam needs modifying)
- div class="globalwrapper" has a new background image. Remove with CSS. 1 Fixed.
- Any widgets using
mediawiki.api.parse stop parsing wikitext.
- 1 These need to be updated to just use
mediawiki.api since the submodules are included in the top level module. (ref)
- 1 [[Has game icon::File:Weaponsmith.png|40x40px|link=Weaponsmith (vendor)]] works but [[Has game icon::File:Weaponsmith.png|link=Weaponsmith (vendor)|40x40px]] does not.
- Solution: Order the parameters like
[[Has game icon::<filename>|<size>|link=<link>]]
- Applies to: Any infobox with an icon.
- The current Special:RunQuery calls doesn't load the result anymore, e.g. Template:Recipe -> "Show base ingredients" doesn't display the table.
- Other notes
- Special:Preferences has an option to ignore all interface updates using OOjs -- may be have been removed later, can't see it anymore.
- SMW template and list formats have been deprecated (ref)
format=template needs replacing with format=plainlistformat=list needs replacing with format=plainlist
- Removed final list separator (", and") -- this may break something (didn't affect recipe lookups).
- Invalid image syntax (e.g. specify two different pixel sizes like so is highlighted when smw's "Has appearance::" annotation is used.
Mediawiki 1.30[edit]
- Broken stuff
- Event timer stuff
- jQuery.fn.bind() is deprecated
- jQuery.fn.delegate() is deprecated
- deprecated ResourceLoader module "jquery.ui.widget" + "jquery.ui.core" ... both of these come from the jquery.ui module for ".sortable". They recommend using "mediawiki.ui.button" or "oojs-ui" instead, but neither of these modules provides the same functionality.
- SMW gallery format with overlay images (opening the overlay image traps you preventing it from closing)
- SMW gallery formats have the image size in pixels forced onto the end of the annotation.
- Other notes
- External scripts loaded using mw.loader.load must not use the array notation.
- DPL3 with randomcount and randomseed (the latter has been removed) - example previously on GWW main page.
- MediaWiki:Searchsuggest-search
- Could remove Extension:Maps
Resource loading sequence[edit]
- Background
- Thinking about whether the gamelink widget could be written through the site-wide JS instead of using inline scripts, which seems to result in the chatlinks sometimes not being encoded/partial success (especially true of long pages).
- Method
- Firefox > Dev Console > Network tab. Load any page. Observe the resources that are called (particularly JS).
| #
|
Description
|
Specifics
|
| 1a
|
HTML for basic page structure
|
startup
|
| 1b
|
Widgets are included in the above. Scripts are loaded inline.
|
inline js
|
| 2
|
Core MW CSS and JS (ugly monobook)
|
built-in CSS and JS, config, jquery, access keys, tooltips
|
| 3
|
Site-wide common and skin-specific CSS and JS (pretty monobook)
|
site CSS and JS, jquery extensions, MW toolbox, MW API
|
| 4
|
User common and skin-specific CSS and JS
|
user CSS and JS
|
| 5
|
Group common and skin-specific CSS and JS
|
group CSS and JS
|
- Other observations
- Common/Monobook/User CSS is also loaded in addition to JS. This means the CSS skins are downloaded twice (waste of time). Fixed in a later version of MW? old post
CSS and JS[edit]
- The mobile layout (e.g. use of branding box word logo instead of the square logo) is applied if the Special:Preferences skin is set to Minerva or mobileaction=mobile_view_toggle is used.
- On a desktop platform, irregardless of whether the mobileaction=desktop_view_toggle or mobileaction=mobile_view_toggle setting is used, common.js is loaded.
- On a mobile platform, irregardless of whether the mobileaction=desktop_view_toggle or mobileaction=mobile_view_toggle setting is used, mobile.js is loaded.
- Minerva.css fails to load in all instances except on Desktop where Special:Preferences skin is set to Minerva.
- Monobook/Vector.css (or Vector if logged in and set in preferences) fails to load on a mobile platform where the mobileaction=desktop_view_toggle has been used.
- Vector-2022 also loads Vector.js and Vector.css.
The following tables illustrate what happens (using MW 1.38.2 and Extension:MobileFrontend 2.4.0)
What originally loads
| Scenario
|
Platform
|
mobileaction mode
|
Skin preference
|
Dominant skin (from mobileaction mode or skin)
|
Scripts loaded due to dominant skin
|
Style loaded due to dominant skin
|
Core scripts due to platform
|
Core styles due to platform
|
| 1
|
DESKTOP
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
Monobook/Vector.css
|
Common.js
|
Common.css
|
| 2
|
DESKTOP
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css
|
Common.js
|
Common.css
|
| 3
|
DESKTOP
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
|
Common.js
|
|
| 4
|
DESKTOP
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
|
Common.js
|
|
| 5
|
MOBILE
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
|
Mobile.js
|
Mobile.css
|
| 6
|
MOBILE
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
|
Mobile.js
|
Mobile.css
|
| 7
|
MOBILE
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
|
Mobile.js
|
Mobile.css
|
| 8
|
MOBILE
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
|
Mobile.js
|
Mobile.css
|
What should have been programmed to load
| Scenario
|
Platform
|
mobileaction mode
|
Skin preference
|
Dominant skin (from mobileaction mode or skin)
|
Scripts loaded due to dominant skin
|
Style loaded due to dominant skin
|
Core scripts due to platform
|
Core styles due to platform
|
| 1
|
DESKTOP
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
Monobook/Vector.css
|
Common.js
|
Common.css
|
| 2
|
DESKTOP
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
| 3
|
DESKTOP
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
| 4
|
DESKTOP
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
| 5
|
MOBILE
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
Monobook/Vector.css
|
Common.js
|
Common.css
|
| 6
|
MOBILE
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
| 7
|
MOBILE
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
| 8
|
MOBILE
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css
|
|
|
What I've set via JS to load (workaround)
| Scenario
|
Platform
|
mobileaction mode
|
Skin preference
|
Dominant skin (from mobileaction mode or skin)
|
Scripts loaded due to dominant skin
|
Style loaded due to dominant skin
|
Core scripts due to platform
|
Core styles due to platform
|
| 1
|
DESKTOP
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
Monobook/Vector.css
|
Common.js
|
Common.css
|
| 2
|
DESKTOP
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css (reloaded)
|
Common.js (skipped)
|
Common.css (unloaded)
|
| 3
|
DESKTOP
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
Minerva.css (added)
|
Common.js (skipped)
|
|
| 4
|
DESKTOP
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css (added)
|
Common.js (skipped)
|
|
| 5
|
MOBILE
|
Desktop
|
Monobook/Vector
|
Monobook/Vector
|
Monobook/Vector.js
|
Monobook/Vector.css (added)
|
Mobile.js (sent to Common.js - rest is blank), Common.js (added)
|
Mobile.css (blank), Common.css (added)
|
| 6
|
MOBILE
|
Desktop
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css (added)
|
Mobile.js (blank)
|
Mobile.css (blank)
|
| 7
|
MOBILE
|
Mobile
|
Monobook/Vector
|
Minerva
|
Minerva.js
|
Minerva.css (added)
|
Mobile.js (blank)
|
Mobile.css (blank)
|
| 8
|
MOBILE
|
Mobile
|
Minerva
|
Minerva
|
Minerva.js
|
Minerva.css (added)
|
Mobile.js (blank)
|
Mobile.css (blank)
|
Test cases[edit]
HTTPS redirects[edit]
- Session hijacking login test
- Login, and remember this login, under HTTPS. Now try to visit the HTTP login page. Success if cannot get to HTTP version.
- HTTP to HTTPS (article)
- HTTP to HTTPS (article talk, with apostrophe)
- HTTP to HTTPS (user space)
- HTTP to HTTPS (user space, with apostrophe)
- HTTP to HTTPS (user space, with apostrophe, with trailing slash)
URL character encoding[edit]
- Edit an article with an ampersand in the title
- Visit PR&T Esoterics. Press history at the top. Confirm history is shown. Now press edit at the top, and try submitting a change.
- Edit a talk page article with an ampersand in the title
- Test a chatlink is decoded in Special:Search (I kinda need to know which arguments the game sends when you type /wiki .. but I can't access GW2 here)
5 second response time when pressing submit[edit]
- Navigate to a new page title. Make some edits in the edit box. Press preview - it should load almost instantly. Press save - takes 5 seconds. User:Chieftain Alex/new page. Passes test if quicker. Delete afterwards.
Weird SMW pages[edit]
- Property:Change propagation — when you make a change to any property, this one shows up with the count of pages left in the processing queue.
