Talk:Elanthipedia bugs: Difference between revisions
GAMERGIRL151 (talk | contribs) (Created page with " =Archive= '''This section should be used only for bugs which have been fully resolved.''' If an issue re-occurs, please post about it on the main page. ==Unable to Dismiss...") |
No edit summary |
||
Line 88: | Line 88: | ||
: Needs the extension Cite enabled for this to work. I'll add it to the list of things to do once the major problems are stamped out. -[[User:CARAAMON|CARAAMON]] ([[User talk:CARAAMON|talk]]) 17:45, 31 August 2016 (CDT) </s> |
: Needs the extension Cite enabled for this to work. I'll add it to the list of things to do once the major problems are stamped out. -[[User:CARAAMON|CARAAMON]] ([[User talk:CARAAMON|talk]]) 17:45, 31 August 2016 (CDT) </s> |
||
::This should be fixed. --[[User:GAMERGIRL151|GAMERGIRL151]] ([[User talk:GAMERGIRL151|talk]]) 19:18, 3 September 2016 (CDT) |
::This should be fixed. --[[User:GAMERGIRL151|GAMERGIRL151]] ([[User talk:GAMERGIRL151|talk]]) 19:18, 3 September 2016 (CDT) |
||
==Italicized items in category list== |
|||
These are now working as they were before the update. There are two types of these links: |
|||
*Italicized links in the bulleted list at the bottom of the category page itself. This happens when a category page gets redirected to incorrectly. A lot of these were introduced when we made the big capitalization push, since many category pages were affected. I fix them as I come across them, since there's no real way to search for them. Here's what causes it and how to fix it if you want to do them if you come across them: |
|||
::A redirect to a Category page should have a colon in front of the 'Category' text. E.g.: <nowiki>#REDIRECT [[:Category:Spell types]]</nowiki>. If it doesn't include the leading colon then the redirect page gets added as an italicized item on the category page it redirects to. In short, the wiki thinks it belongs in the category unless the leading colon is there. |
|||
::Note that this also applies to links to a category page if the page itself is not supposed to be in the category list. E.g. a users favourites page might have a link to the crafting materials category and the proper syntax would be <nowiki>[[:Category:Crafting materials]]</nowiki> with the leading colon. Without the colon, the person's favourites page would show up as an item in the list at the bottom of the category page. These are rarer, and harder to spot since they're not in italics. |
|||
*Italicized links in the category infobox at the bottom of a non-category page (E.g. a creature's page). |
|||
::These links are links to concept pages instead of categories, and were italicized before the update. I can look into making the template not italicize them, but for now these are considered "working". |
|||
--[[User:ABSOLON|ABSOLON]] ([[User talk:ABSOLON|talk]]) 00:02, 31 August 2016 (CDT) |
Revision as of 19:01, 3 September 2016
Archive
This section should be used only for bugs which have been fully resolved. If an issue re-occurs, please post about it on the main page.
Unable to Dismiss Site Notice
*there is no link to dismiss the "ATTENTION Semantic searching and tagging for Armor, Weapon, Shield, and Post categories are not functioning properly. It is being worked on." notice at the top of the page
It's part of an extension called DismissableSiteNotice, something I'll ask onsite to add back in once we have the major problems stamped out. -CARAAMON (talk) 01:34, 31 August 2016 (CDT)- Fixed, thanks! --Kythryn 18:31, 3 September 2016 (CDT)
Ranik Map Index Formatting
Formatting went haywire on the top-level Ranik Maps page
Page Movement Errors
Getting the following error when I attempt to MOVE a page (This is the one I was moving News:Dateline 8/8/2012: WELCOME TO DRAGONREALMS):
- Error: 1146 Table 'elanthipedia2.smw_fpt_askdu' doesn't exist (wikisql2.simutronics.com)
I get the following error when I attempt to move pages:
- A database query error has occurred. This may indicate a bug in the software.
- Query:
- UPDATE `smw_fpt_askdu` SET s_id = '616505' WHERE s_id = '290888'
- Function: SMWSQLStore3::changeSMWPageID
- Error: 1146 Table 'elanthipedia2.smw_fpt_askdu' doesn't exist (wikisql2.simutronics.com)
- Backtrace:
- #0 /var/www/mediawiki/includes/db/Database.php(901): DatabaseBase->reportQueryError('Table 'elanthip...', 1146, 'UPDATE `smw_fp...', 'SMWSQLStore3::c...', false)
- #1 /var/www/mediawiki/includes/db/Database.php(1512): DatabaseBase->query('UPDATE `smw_fp...', 'SMWSQLStore3::c...')
- #2 /var/www/mediawiki/extensions/SemanticMediaWiki/src/MediaWiki/Database.php(334): DatabaseBase->update('smw_fpt_askdu', Array, Array, 'SMWSQLStore3::c...', Array)
- #3 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_SQLStore3.php(598): SMW\MediaWiki\Database->update('smw_fpt_askdu', Array, Array, 'SMWSQLStore3::c...')
- #4 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_SQLStore3_Writers.php(666): SMWSQLStore3->changeSMWPageID(290888, 616505, 0, 0, true, false)
- #5 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/storage/SQLStore/SMW_SQLStore3.php(351): SMWSQLStore3Writers->changeTitle(Object(Title), Object(Title), 114667, 36640)
- #6 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/StoreUpdater.php(235): SMWSQLStore3->changeTitle(Object(Title), Object(Title), 114667, 36640)
- #7 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/StoreUpdater.php(208): SMW\StoreUpdater->handleYetUnknownRedirectTarget(Object(SMW\SemanticData), Object(SMW\DIWikiPage))
- #8 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/StoreUpdater.php(180): SMW\StoreUpdater->checkForRequiredRedirectUpdate(Object(SMW\SemanticData))
- #9 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/StoreUpdater.php(125): SMW\StoreUpdater->doRealUpdate(NULL)
- #10 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/StoreUpdater.php(92): SMW\StoreUpdater->performUpdate()
- #11 /var/www/mediawiki/extensions/SemanticMediaWiki/includes/ParserData.php(261): SMW\StoreUpdater->doUpdate()
- #12 /var/www/mediawiki/extensions/SemanticMediaWiki/src/MediaWiki/Hooks/LinksUpdateConstructed.php(62): SMW\ParserData->updateStore()
- #13 /var/www/mediawiki/extensions/SemanticMediaWiki/src/MediaWiki/Hooks/HookRegistry.php(287): SMW\MediaWiki\Hooks\LinksUpdateConstructed->process()
- #14 [internal function]: SMW\MediaWiki\Hooks\HookRegistry->SMW\MediaWiki\Hooks\{closure}(Object(LinksUpdate))
- #15 /var/www/mediawiki/includes/Hooks.php(195): call_user_func_array(Object(Closure), Array)
- #16 /var/www/mediawiki/includes/deferred/LinksUpdate.php(139): Hooks::run('LinksUpdateCons...', Array)
- #17 /var/www/mediawiki/includes/content/AbstractContent.php(234): LinksUpdate->__construct(Object(Title), Object(ParserOutput), true)
- #18 /var/www/mediawiki/includes/page/WikiPage.php(2185): AbstractContent->getSecondaryDataUpdates(Object(Title), NULL, true, Object(ParserOutput))
- #19 /var/www/mediawiki/includes/MovePage.php(562): WikiPage->doEditUpdates(Object(Revision), Object(User), Array)
- #20 /var/www/mediawiki/includes/MovePage.php(258): MovePage->moveToInternal(Object(User), Object(Title), 'capitalization ...', true)
- #21 /var/www/mediawiki/includes/specials/SpecialMovepage.php(591): MovePage->move(Object(User), 'capitalization ...', true)
- #22 /var/www/mediawiki/includes/specials/SpecialMovepage.php(128): MovePageForm->doSubmit()
- #23 /var/www/mediawiki/includes/specialpage/SpecialPage.php(479): MovePageForm->execute(NULL)
- #24 /var/www/mediawiki/includes/specialpage/SpecialPageFactory.php(576): SpecialPage->run(NULL)
- #25 /var/www/mediawiki/includes/MediaWiki.php(282): SpecialPageFactory::executePath(Object(Title), Object(RequestContext))
- #26 /var/www/mediawiki/includes/MediaWiki.php(745): MediaWiki->performRequest()
- #27 /var/www/mediawiki/includes/MediaWiki.php(519): MediaWiki->main()
- #28 /var/www/mediawiki/index.php(43): MediaWiki->run()
#29 {main}- This should be resolved. --GAMERGIRL151 (talk) 19:18, 3 September 2016 (CDT)
Page creation
When trying to create a new page titled Elanthipedia bugs (as opposed to the current [[Elanthipedia Bugs]] page) in order to handle redirects, etc. it makes me do it using the Form:Player Characters form with the option to instead use the Form:BrawlItem form. This happens when I click on the redlink on this redirect page: Bugs.
This link is what it brings me to (the wiki parses the link incorrectly so you'll need to manually follow it via cut and paste):
https://elanthipedia.play.net/Special:FormEdit/Player%20Characters/Elanthipedia_bugs?alt_form[0]=BrawlItem&redlink=1
--ABSOLON (talk) 22:41, 1 September 2016 (CDT)
Just to add to this issue, it seems to happen with pretty much any redlink (weapon, item, etc). I just had the two item links here try to use the character template, too. -TEVESHSZAT (talk) 23:36, 1 September 2016 (CDT)Well huh. I'm not seeing a rhyme or reason to when this kicks in. If I had to guess, I'd suspect something's buggy with the Wikimedia core program or it's interaction with semantic forms... but I 'll keep poking it. -CARAAMON (talk) 16:02, 2 September 2016 (CDT)- This should be resolved. --GAMERGIRL151 (talk) 19:18, 3 September 2016 (CDT)
Missing Forms
The "Edit with Form" link is missing on item/shield/weapon pages. --Kythryn 11:47, 30 August 2016 (CDT)
- Edit with form is missing in all cases. I believe this is tied to property pages, since some of them still seem to be missing or not functioning correctly. Pages within a category (e.g. Category:Spells) are tied to a form via two things:
- The output template that is used on the pages that use the form and designated within the form's code to be used to output the form's results.
- A property added to a Category page that tells the wiki that pages within this category are to use a designated form.
- What appears to be broken here is #2; the property that states that a category should use a given form doesn't exist. See Category:Spells for an example of where the property designator [[has default form::Form:Spell| ]] is not working correctly because the either or both of the Property:Has default form page doesn't exist or isn't functioning correctly. The latter might be that properties that have multiple layers that are not functioning. I.e. The value Form:Spell might not be working properly because it is a compound value.--ABSOLON (talk) 23:02, 30 August 2016 (CDT)
- I seem to have been able to jumpstart the automatic usage of forms by simply empty editing the appropriate Elanthipedia namespace pages. Let me know if any are still misbehaving. -CARAAMON (talk) 01:49, 31 August 2016 (CDT)
- Spell pages, character pages, creature pages, and NPC pages are still missing. I.e. the ones on the Elanthipedia:Forms list that are in the default Page namespace rather than a custom or wiki one. The form can be accessed using those links, so the form itself is functioning correctly, it's just missing the link at the top of the content page.--ABSOLON (talk) 02:07, 31 August 2016 (CDT)
- I seem to have been able to jumpstart the automatic usage of forms by simply empty editing the appropriate Elanthipedia namespace pages. Let me know if any are still misbehaving. -CARAAMON (talk) 01:49, 31 August 2016 (CDT)
Yes, this appears to be fixed.--ABSOLON (talk) 09:50, 31 August 2016 (CDT)
Linking between pages and their talk pages
When clicking on the "Page" link at the top of a Talk page to view the main page does not always work. You remain on the talk page. E.g. Armor_talk:Ring_lorica_(crafted)
Related to this, before the update when we could still move pages, if you move a Page (which usually moves the talk page along with it) the talk page sometimes doesn't get moved and you end up with weird cross linking between the new main page, the old talk page, and the new talk page.--ABSOLON (talk) 22:41, 1 September 2016 (CDT)
This happens to any discussion page in the Item: or Armor: namespaces. Their Discussion page links are broken. See Template_talk:Item#Discussion_links_for_this_template_are_broken. - padhg (talk) 12:54, 2 September 2016 (CDT)- This should be fixed. --GAMERGIRL151 (talk) 19:18, 3 September 2016 (CDT)
References are not parsed
With the latest update, <ref>, </ref>, and <references /> are not treated as wiki tags. See DEPART for an example. - padhg (talk) 11:18, 31 August 2016 (CDT)
Needs the extension Cite enabled for this to work. I'll add it to the list of things to do once the major problems are stamped out. -CARAAMON (talk) 17:45, 31 August 2016 (CDT)- This should be fixed. --GAMERGIRL151 (talk) 19:18, 3 September 2016 (CDT)
Italicized items in category list
These are now working as they were before the update. There are two types of these links:
- Italicized links in the bulleted list at the bottom of the category page itself. This happens when a category page gets redirected to incorrectly. A lot of these were introduced when we made the big capitalization push, since many category pages were affected. I fix them as I come across them, since there's no real way to search for them. Here's what causes it and how to fix it if you want to do them if you come across them:
- A redirect to a Category page should have a colon in front of the 'Category' text. E.g.: #REDIRECT [[:Category:Spell types]]. If it doesn't include the leading colon then the redirect page gets added as an italicized item on the category page it redirects to. In short, the wiki thinks it belongs in the category unless the leading colon is there.
- Note that this also applies to links to a category page if the page itself is not supposed to be in the category list. E.g. a users favourites page might have a link to the crafting materials category and the proper syntax would be [[:Category:Crafting materials]] with the leading colon. Without the colon, the person's favourites page would show up as an item in the list at the bottom of the category page. These are rarer, and harder to spot since they're not in italics.
- Italicized links in the category infobox at the bottom of a non-category page (E.g. a creature's page).
- These links are links to concept pages instead of categories, and were italicized before the update. I can look into making the template not italicize them, but for now these are considered "working".