Allow posting new sections to top of page on a per-page basis
OpenPublic

Description

As you can see in this URL, I want to add a parameter(the actual in that preloadedtext/template. The problem is that there is no magic word that recognize the actual full URL of that page, nor is there a way to give the preloadtext any parameter. A "quick 'n dirty" possibility for adding the desired parameter would be allowing me that I can use the appendtext of the API like in the following URL:
http://en.wikipedia.org/w/index.php?title=User_talk:Mabdul&action=edit&editintro=Template:AFC_submission/user_talk_editintro&preload=Template:AFC_submission/user_talk_preload/sandbox&preloadtitle=Your+submission+at+%5B%5BWP%3AAFC%7CArticles+for+creation%5D%5D&section=new&appendtext=GPL}}

With this change, I would be able to change the actual system (by moving the actual pagename to the end) of our preloaded template and thus being able that the "accepting" reviewer don't have to type the accepted page manually. (this template is existing of course also for declining)


Version: unspecified
Severity: enhancement
URL: http://en.wikipedia.org/w/index.php?title=User_talk:Mabdul&action=edit&editintro=Template:AFC_submission/user_talk_editintro&preload=Template:AFC_submission/user_talk_preload/sandbox&preloadtitle=Your+submission+at+%5B%5BWP%3AAFC%7CArticles+for+creation%5D%5D&section=new&page=GPL
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=15494

bzimport added a subscriber: Unknown Object (MLST).
bzimport set Reference to bz31919.
Mabdul created this task.Via LegacyOct 24 2011, 1:37 PM
kaldari added a comment.Via ConduitMay 15 2012, 6:11 PM

I'm having a bit of trouble understanding your request. Are you saying you want to preload a template into the editing interface and also pass parameters to that template via the URL? If so, there is no practical way to implement that as the edit page has no awareness of templates and their parameters, i.e. it wouldn't know where to plug in the parameter text. Could you explain more specifically what you are wanting to accomplish. Perhaps there is a better way to achieve it.

Mabdul added a comment.Via ConduitMay 16 2012, 9:57 AM

I believe that you misunderstood me and rereading my own bug report I understand why.

The API allows to add sections/text at the top of the page through the api call 'appendtext' this would be very helpful for some tasks at enwp if we can use that also by using the normal GUI.

This is in contrast similar to the &section=new only at the top of the page, because &section=-1 doesn't work (the first section is filled in the text field) nor is &section=0 always usable since preloaded text doesn't work in both cases

What we need (the TeaHouse and the AFC team) is that we can add sections at the top and or above all content. (best would be both)

Hope that clarifies the situation.

kaldari added a comment.Via ConduitMay 16 2012, 2:07 PM

Ah, so you want to be able to post new sections to the top of the page. Why didn't you just say so :)

MZMcBride added a comment.Via ConduitOct 19 2012, 5:56 PM

This bug is related to bug 15494 ("Add new sections to the top of a page on a site-wide basis").

I'm going to mark this as easy. Bug 15494 is about the ability to change the &section=new behavior on a site-wide basis (via a configuration variable). This bug is about the ability to change the &section=new behavior on a per-page basis.

I think a magic word is the most logical implementation for this. Something like REVERSEPOSTORDER or something, maybe? That way it would just do whatever the non-default behavior is. Or you could take a more explicit approach and have ALWAYSTOPPOST and ALWAYSBOTTOMPOST and the implicit value would be whatever the site-wide default is.

Jdpond added a comment.Via ConduitFeb 19 2014, 12:55 PM

*** Bug 15494 has been marked as a duplicate of this bug. ***

gerritbot added a subscriber: gerritbot.Via ConduitMay 9 2015, 6:30 AM

Change 209853 had a related patch set uploaded (by Legoktm):
Have action=edit&section=new prepend if ALWAYSTOPPOST is set

https://gerrit.wikimedia.org/r/209853

gerritbot added a project: Patch-For-Review.Via ConduitMay 9 2015, 6:30 AM
Technical13 added a comment.Via WebMay 9 2015, 1:58 PM

The only question/concern about this is how is "top" defined for this patch? For AfC drafts, I can see top as defined as section 0; but for the WP:THQ, which is supposed to be top posting, top would be defined as the first section after the header which is section 1 on the page (don't think there are any header sections in templates).

Legoktm added a comment.Via WebMay 9 2015, 11:46 PM

The only question/concern about this is how is "top" defined for this patch? For AfC drafts, I can see top as defined as section 0; but for the WP:THQ, which is supposed to be top posting, top would be defined as the first section after the header which is section 1 on the page (don't think there are any header sections in templates).

top is defined as literally the top of the page, before any other content.

MZMcBride added a comment.Via WebMay 10 2015, 2:18 PM

Another possible approach might be having a __POSTBELOWHERE__ magic word or similar that could be placed in an arbitrary position on the page.

I'm not sure how I feel about creating new magic words these days.

Technical13 added a comment.Via WebMay 10 2015, 4:19 PM

Another possible approach might be having a __POSTBELOWHERE__ magic word or similar that could be placed in an arbitrary position on the page.

I'm not sure how I feel about creating new magic words these days.

That would certainly resolve the situation I mentioned.

Technical13 added subscribers: Ocaasi, Heather, Capt_Swing.Via WebMay 10 2015, 4:22 PM
MZMcBride added a subscriber: Rjd0060.Via WebMay 11 2015, 1:07 AM

Another silly idea: have a {{#post new sections:1}} magic word that can be used to specify per-page behavior of where new talk page posts should be posted. In this example, new talk page sections would be created in the 1st section (after the 0th) section. {{#post new sections:last}} or {{#post new sections:default}} or {{#post new sections:4}} could also be supported.

As @Rjd0060 pointed out to me in discussion of this feature generally, having individual pages behave differently with regard to post order may result in user confusion.

Glaisher added a project: user-notice.Via WebMay 11 2015, 3:50 AM
Glaisher added a subscriber: Glaisher.
gpaumier moved this task to Not ready to announce on the user-notice workboard.Via WebMay 14 2015, 10:58 PM

Add Comment