Last modified: 2013-02-17 08:16:24 UTC
http://www.mediawiki.org/wiki/Thread:Extension:LiquidThreads/FAQ/Edit_button Someone reported: "Is there a way to put the [edit^] and [History^] buttons on the top of the page as tabs. I understand that the point in threads is to allow for discussion, however moving the buttons from their standard position makes it harder for people to use the page. I'd be willing to modify my source code if you could give me a hint at where the change might be located." I fully support this idea and filed this as enhancement bug.
There is a distinct difference between editing a *page* and editing a *thread* and editing a *post within a thread*. This is a complicated problem, but putting the edit and history links at the top of the page is not going to solve your problem as described.
(In reply to comment #1) > There is a distinct difference between editing a *page* and editing a *thread* > and editing a *post within a thread*. This is a complicated problem, but > putting the edit and history links at the top of the page is not going to solve > your problem as described. Sorry Brandon, you misunderstood. The requester wanted to have the single additional buttons [^edit] and [^history] on top of the "standard, non-lqt" mediawiki page, i.e. the action=edit and action=history for the current page. I support this wish, as I often was puzzled where to find this unusual links, when they were not tabs. This happens for old talk pages, where you add {{#userliquidthreads:1}} and where then the Lqt section is often miles away at the end of the (non lqt) "header" Take this example: http://www.mediawiki.org/wiki/Extension_talk:User_Merge_and_Delete User coming to that page do _not_ see how they can add or edit the page - they need to go down the whole page to find [^edit] and [^history] links (after having Lqt activated on this page. The bug aims to ask the Lqt developers to find a solution, that these two links are tabs of the page, on top of the page.
This bug has not been touched in at least six months. With this in mind, I've been asked by the bugmeister to bump this bug's priority down for "High". Concerns can be addressed to mah@everybody.org.
