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 T29879, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 27879 - LQT behaves poorly with $wgReadOnly = true

Summary:	LQT behaves poorly with $wgReadOnly = true

Status: NEW Product: MediaWiki extensions Classification: Unclassified Component: LiquidThreads (Other open bugs) Version: unspecified Hardware: All All Importance: Normal minor (vote) Target Milestone: --- Assigned To: Nobody - You can work on this! URL: Whiteboard: Keywords: Depends on: Blocks:   Show dependency tree / graph		Reported: 2011-03-05 22:02 UTC by Sam Reed (reedy) Modified: 2011-04-14 15:03 UTC (History) CC List: 2 users (show) agarrett bharris See Also: Web browser: --- Mobile Platform: --- Assignee Huggle Beta Tester: ---

Attachments Add an attachment (proposed patch, testcase, etc.)

Description Sam Reed (reedy) 2011-03-05 22:02:49 UTC If the wiki is set to read only, when you try and do a reply/add new post, it just sits there attempting to load it, with the spinning loader thingy... Comment 1 Sam Reed (reedy) 2011-03-06 01:58:02 UTC I'm guessing something like r83353 is needed in lqt.js... It loads the spinner, but never does anything to remove it again on error. Only on finishSetup