Last modified: 2011-04-30 01:21:30 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T22555, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20555 - Page look-and-feel (and login status) differs by page/user/browser after upgrade from 1.12
Page look-and-feel (and login status) differs by page/user/browser after upgr...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.15.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
intranet-wiki
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-09 00:10 UTC by Kane Muir
Modified: 2011-04-30 01:21 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kane Muir 2009-09-09 00:10:19 UTC
* MediaWiki version: 1.15.1
* PHP version: 5.2.3 (isapi)
* MySQL version: 5.0.24-community-nt
* Installed extensions: ParserFunctions (version 1.2.0); SyntaxHighlight

We recently upgraded our intranet wiki from 1.12 to 1.15.1, to get access to collapsible tables (with a little customization of special pages MediaWiki:Common.css and MediaWiki:Common.js). However, the look-and-feel of pages varies. Some pages display in what I presume to be the latest look-and-feel, whereas others are decidedly less attractive. Also, the browser CAN lose the user's login status - until an "acceptable" page is accessed, when all is good again - but pages can appear "bad" but also retain the logged-in status.

The good/bad behaviour seems to depend on a combination of user/page/browser - but it is consistent for a given combo. All users run Windows XP. Browsers are Firefox 3.0 & 3.5 and IE 6/7/8. 99% sure we are not using skins in any way.

Any help would be greatly appreciated.
Comment 1 Kane Muir 2009-09-15 06:52:56 UTC
Seems to be an issue with browser cookies. Logging out, then logging back in again seems to cure the problem.
Comment 2 Siebrand Mazeland 2009-09-15 07:02:19 UTC
INVALID per comment 1.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links