Last modified: 2009-09-18 13:59:56 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 T22719, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20719 - Preferences' time offset (timezone) corrupted (maybe also stub link threshold)
Preferences' time offset (timezone) corrupted (maybe also stub link threshold)
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Andrew Garrett
http://de.wiktionary.org/wiki/Spezial...
: code-update-regression
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-18 11:36 UTC by Melancholie
Modified: 2009-09-18 13:59 UTC (History)
1 user (show)

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


Attachments

Description Melancholie 2009-09-18 11:36:24 UTC
With the latest code update, user defined time offsets have been changed/corrupted.

Suddenly there is a wrong time offset and wrong timezone specified at [[Special:Preferences]].

E.g. +1 instead of +2 hours, suddenly. And "Europe/Berlin" etc. is suddenly not chosen/shown by default in the drop down menu, for some users.
In the form below there suddenly is a '45'!

If re-enabled "Europe/Berlin" it works again, but the '45' is still shown after reload (with no effect anymore), although removed before save.

Note that under "Threshold for stub link formatting (bytes)" there is also that mysterious '45'.

----
I would understand if it were '42', but '45'? ;-)
Comment 1 Melancholie 2009-09-18 11:40:06 UTC
See [[wikt:de:Benutzer_Diskussion:Melancholie#Problem_bei_letzte_.C3.84nderungen]]
It's the case on every wiki, but not sure if for every user. But at least for two I'm sure ;-)
Comment 2 Andrew Garrett 2009-09-18 13:59:56 UTC
Resolved in r56184, fix deployed.

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


Navigation
Links