Page MenuHomePhabricator

LQT should intercept "section=new" edits through API as well as skin interface
Open, LowestPublic

Description

To quote Roan:

LQT hijacks section=new via the PerformAction hook, but it doesn't make
any attempt to hijack section=new in the API. Instead, LQT has its own
API for posting things

This leads to tools that use the edit API (such as the Feedback tool) being incompatible with LQT.


Version: master
Severity: normal
See Also:

Details

Reference
bz41276

Event Timeline

bzimport raised the priority of this task from to Low.
bzimport set Reference to bz41276.
bzimport added a subscriber: Unknown Object (MLST).
Qgil added a comment.Mar 19 2013, 3:50 PM

I guess LQT extension must be a good citizen and get along with other extensions? Under the exclusivity is there by design, this looks more like a bug (and a major one) rather than an enhancement request.

Setting to "Normal" because I lack the background. Feel free changing to Major if you agree that blocking other extensions deserves that.

See also [[mw:Thread:VisualEditor/Feedback/Eror on Feedback?]]

Is this solved by Flow?

Is this solved by Flow?

No. Flow's version of this same problem is T59989: S2. Flow API: Let code add a new topic with action=edit&section=new.

Elitre added a subscriber: Elitre.Jan 8 2015, 5:12 PM
He7d3r updated the task description. (Show Details)Mar 29 2015, 6:50 PM
He7d3r set Security to None.
Jdforrester-WMF lowered the priority of this task from Low to Lowest.Aug 4 2016, 11:34 PM

LiquidThreads has been replaced by StructuredDiscussions on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as "Lowest" priority.

Qgil removed a subscriber: Qgil.Aug 8 2016, 8:09 AM