Last modified: 2012-08-05 20:24:53 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 T31320, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29320 - "drag to new location": when moving a reply (down under a thread) to become a new thread and leaving new subject (required) open: ApiThreadAction crashes with "Error: no-valid-subject: undefined"
"drag to new location": when moving a reply (down under a thread) to become a...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: High critical (vote)
: ---
Assigned To: Andrew Garrett
http://svn.wikimedia.org/viewvc/media...
:
: 25457 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-08 22:06 UTC by T. Gries
Modified: 2012-08-05 20:24 UTC (History)
2 users (show)

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


Attachments

Description T. Gries 2011-06-08 22:06:16 UTC
ApiThreadAction crashes and does NOT show the string 'No subject, or an invalid subject, was specified'

	$this->dieUsage( 'No subject, or an invalid subject, was specified',
				'no-valid-subject' );


instead of the wanted error message, javasacript throws ugly "Error: no-valid-subject: undefined" error.

Please dear LiquidThreads2.0 Experts, can you please fix this legacy version Lqt1.0 problem now? I tried to fix it, it is very difficult.

(Cannot wait to undetermined time when Lqt2.0 is released.)
Comment 1 T. Gries 2011-06-08 22:08:44 UTC
This is a very-difficult-to-find-and-to-fix bug. Andrew, please can you do me a personal favor and fix that, please.
Comment 3 Helder 2012-08-05 20:24:53 UTC
*** Bug 25457 has been marked as a duplicate of this bug. ***

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


Navigation
Links