2017 wikitext editor/Feedback/2017/05
This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
Post your feedback about using the first iteration of the 2017 wikitext editor as a Beta Feature.
If you are reporting a problem directly on this page, please include your web browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook). Also, while editing to reproduce a problem, please try to append &safemode=1
at the end of the URL; if the problem disappears, you are using a gadget or script that interferes with the editor.
The Editing team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features. All comments are read, in any language, but personal replies are not guaranteed.
We are trying to keep the page tidy by providing links to relevant tasks while closing threads. You can help by adding {{tracked|T######}}. By all means, feel free to re-open a thread if you need to!
See also:
View open developer tasks – Complete workboard – Report a new bug in Phabricator – Join the IRC channel
Empty server response
[edit]RESOLVED | |
Now fixed. Sorry for the inconvenience. |
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Seems linked to VE, as there are many reports here of this error appearing. As such I don't know if it's relevant specifically to the 2017 editor, but I use/used the 2017 editor and got this error aswell today, so I had to turn it off for now. Sara4177 (talk) 18:26, 1 May 2017 (UTC)
- Thanks for this detail, will update the task accordingly. Appreciate your patience while we sort that out. Elitre (WMF) (talk) 13:40, 2 May 2017 (UTC)
I miss the old textarea-based editor
[edit]I enabled wikitext. It has a better interface (just like this one in Flow). It may have a lot of useful features in the future. But it breaks my source code reading and editing completely.
When I'm going to write or edit long text carefully, I prefer to do it in my Vim instead of the browser for more powerful features and easy-of-use. I have installed a browser extension to invoke my favorite editor to edit textareas. But it doesn't work for "contenteditable" HTML tags. And it can't, because they are theoretically not plain text.
I have to disable the feature to use the textarea based editor. It's not like VisualEditor which I can choose and even switch between it and the plain text editor. Maybe add another switch menu item? Lilydjwg (talk) 03:31, 6 May 2017 (UTC)
- Actually, you can do it by yourself, in js. I'm not so sure it can be done "officially", because then there is a need for a switching mechanism for three editors ("Do you want to continue in other editor or abandon the changes you did?"), and I believe it's hard to do. IKhitron (talk) 11:51, 6 May 2017 (UTC)
Reuse citation
[edit]I tried this and noticed that "reuse" citation was nonfunctional (greyed out). Am very happy about that as I do not want bad ref names like <nowiki><ref name=":0"/></nowiki> becoming even more widespread. Please do not enable that, until those dysfunctional ref names are eliminated.
I'll also note that I tried to type that ref name in Wiki-markup and this software interrupted me and demanded I add an actual citation. I was only able to get around that interruption and type what I just did, by typing " ref name=":0"/>" and then going back and adding the "<" at the beginning. So apparently manually re-using citations is not easy in this editor, whatever it is. Hm. ~~~~
And my signature doesn't work?
How do I preview?? Wow I have no idea how this thing works.
I use a Mac with 10.12.4 (16E195) and am using Chrome for mac 58.0.3029.96 (64-bit) and I am using the default skin, whatever that is. Jytdog (talk) 02:03, 10 May 2017 (UTC)
- The default skin is Vector, and you were probably using Flow's visual mode. Flow auto-signs and auto-dates all comments. Click the pencil icon to switch to Flow's wikitext mode. (Advantage of the visual mode: it automagically adds nowiki tags for you. [Also, you don't need to preview in this mode, because it's rich text.] Disadvantage: you have to be able to type the wikitext code before it can automagically add the nowiki tags. Work-around: Start typing your wikitext, and then press the Escape key when it offers to auto-convert the wikitext.)
- Another editor has asked to have the "Re-use citation" option enabled, but I'm not sure that it is feasible at all, and, at most, it's probably only possible for citations that have already been named (ideally with a more sensible/language-specific scheme). Whatamidoing (WMF) (talk) 16:51, 10 May 2017 (UTC)
- ...And phab:T164954 was declined, so your wish has been granted indefinitely. Whatamidoing (WMF) (talk) 17:29, 10 May 2017 (UTC)
- hmmmm. that is some kind of automagic undertanding of phab-speak, but i will believe you. :) Thank you for all the answers. Jytdog (talk) 01:18, 11 May 2017 (UTC)
Use shortcut to get out of preview
[edit]A very simple improvement suggestion: using Alt + P shows the preview page, so using the same shortcut on the preview page should also close the preview and return to the editor. This way I don't have to get my hands out of the keyboard every time I want to preview, and I can continue editing at the same position I was. Darkdadaah (talk) 12:53, 10 May 2017 (UTC)
- Thanks for this comment. I also hate moving my hands off my keyboard.
- As with all dialogs (or almost all) in this editing software, the Escape key closes the box. That way, you don't have to know the specific shortcut for each box just to make it go away. Is that good enough for your purposes? Whatamidoing (WMF) (talk) 16:59, 10 May 2017 (UTC)
- Also: Command-Enter on a Mac (probably Control-Enter on a PC) clicks the main button on most of them, so if you use a dialog to fill in a template, then you can finish up the box without scrolling over to the button and clicking it. Whatamidoing (WMF) (talk) 17:01, 10 May 2017 (UTC)
- Thanks, that make sense.
- Can we expect all shortcuts from the old editor to be usable in the new one? The only shortcut I can't use is Alt + b (to get to the edit summary). Darkdadaah (talk) 19:52, 10 May 2017 (UTC)
- Many do, but not all. The edit summary is in the "Save" (aka "Publish") dialog, so you trigger that with Alt-S. See VisualEditor/Portal/Keyboard shortcuts for most of them. Whatamidoing (WMF) (talk) 23:57, 11 May 2017 (UTC)
The new editor suddenly won't load for me.
[edit]RESOLVED | |
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I've had no problems using the 2017 WT editor, but today it simply won't load. When I press "edit source" I get the following message:
If I click the "reload the page"-link I get taken to the normal wikitext-editor. InsaneHacker (talk) 09:15, 12 May 2017 (UTC)The editor will now load. If you still see this message after a few seconds, please reload the page.
- On which page? Elitre (WMF) (talk) 10:48, 12 May 2017 (UTC)
- Please see if you can provide more details. I couldn't reproduce on Chrome on random and even big articles (and it looks like you may be experiencing other issues that are not related to NWE, so I'm guessing you may have an issue with your browser). (For a moment I thought I could see that, and then realized that the link from da.wp's homepage led me to a sv.wp article, where I don't have NWE enabled.) Elitre (WMF) (talk) 11:11, 12 May 2017 (UTC)
- I'm away from home and using a laptop with Chrome instead of the Firefox browser which had the problem, the editor works fine here. I'll take a look at my browser when I get home. Thanks! InsaneHacker (talk) 11:45, 12 May 2017 (UTC)
- I had problems loading the editor on both my talk page and the help desk page - it turned out to be because of the beta pref I had ticked - this editor in particular. I'm using Chrome on a Windows 10 desktop. Berek (talk) 12:03, 13 May 2017 (UTC)
- Reported today in Ukrainian Wikipedia as well (see here). The editor still works for me, but I'm frequently seeing that message as well. For instance, I receive it when I try to open some red link. Also today I've been completely unable to use HotCat to change categories – I tried to edit some categories on a page, got the message mentioned, and after clicking on the "reload the page" link, I ended up with a browser error message "This site can't be reached". Piramidion (talk) 18:52, 13 May 2017 (UTC)
Cannot disable the editor
[edit]RESOLVED | |
User figured it out! |
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
After first enabling the feature, I've been unable to disable it again. That includes hitting the "Restore all default settings (in all sections)" button, and ensuring that all of the features under the Beta section are unchecked. I still see "Edit Source" when I go to edit, and am prompted about the visual editor. Any ideas?
Browser: Firefox
OS: Windows10
Wiki Skin: Vector
Update: even more interesting! The "Edit Source" option has disappeared, and I am no longer prompted. Wiki highlighting isn't coming up. Seems like there was some kind of delay.
Update 2: Wiki highlighting still isn't coming up. Attempted to remedy by closing reopening browser and logging out/in of Wikipedia. Problem persists.
Update 3: Resolved! It looks like hitting that initial restore default also turned off the syntax highlighter gadget! How easy it is to take little things like that for granted. So, the only real issue was the delay between the disabling of the feature. Biochemistry&Love (talk) 03:57, 13 May 2017 (UTC)
- Thank you for the helpful updates. :-) Whatamidoing (WMF) (talk) 20:32, 17 May 2017 (UTC)
- My pleasure! (: Biochemistry&Love (talk) 21:10, 17 May 2017 (UTC)
- I reopen this subject as I have the same problem about being unable to disable this editor... I would like to do so for now, but the above workaround of restoring all settings is not acceptable to me.
- Browser: Firefox Quantum (57.0.1) - 64 bits
- OS: Windows 10 (latest insider version: 1709 - 17046.10000) - 64 bits
- WP skin details: Vector - no custom template (existing, but empty). Epok (talk) 18:19, 6 December 2017 (UTC)
- I had the same issue (Firefox Quantum (57.0.2) 64b @ Win10, wikistyle Vector).
- What worked for me was disabling all Beta features and the editor has immediately switched back to the old wikitext editor.
- May it will help someone. YjM (talk) 21:15, 17 December 2017 (UTC)
- @Epok, have you turned off all the Beta Features (the last tab), and then saved your prefs? Did that work for you? Whatamidoing (WMF) (talk) 19:57, 27 December 2017 (UTC)
- @Whatamidoing (WMF), Yes, it worked! I cleared all checks on the beta feature page, and saved, and it worked. I was then able to reactivate other beta features I wanted. Thanks! Epok (talk) 10:16, 28 December 2017 (UTC)
Clicking a red link shouldn't take me straight into editing with no way to back out
[edit]On the old wikitext editor, clicking a redlinked article that has previously been deleted gives me clickable information at the top including the deletion log for the page and a line I can click that takes me to a page showing deleted edits. On the new editor, clicking a redlink immediately goes into the full editing interface, with the "view X deleted edits" line greyed out and not clickable, and no mention of the deletion log. I can't figure out how to click the "X deleted edits" line without manipulating the URL, and would appreciate being able to see the deletion log. Samwalton9 (talk) 11:14, 14 May 2017 (UTC)
- Sam, are you still seeing this? (You can go to Help:Sample page#World literature and click the red link to test.) Whatamidoing (WMF) (talk) 20:30, 16 June 2017 (UTC)
- Nope, did the behaviour get changed? :) Samwalton9 (talk) 20:50, 16 June 2017 (UTC)
- I hope so. Unless it's the change that means that I can't hand-edit the URL to avoid the new wikitext mode (which copes very badly on <translate>d pages right now), in which case, I hope that they un-fix it and try a different approach.
;-)
- Thanks for the update. If it breaks again, then please come back and let me know. Whatamidoing (WMF) (talk) 07:16, 17 June 2017 (UTC)
- This is still funky. When I search for a deleted page and click the Redlink I get taken into the page editing interface straight away again. Samwalton9 (talk) 21:57, 26 June 2017 (UTC)
- I can't reproduce this at mw.org today, so I'm hopeful that this means it will be fixed everywhere as soon as the deployment train reaches all the wikis. Whatamidoing (WMF) (talk) 17:23, 3 August 2017 (UTC)
- This is still fixed at mw.org, and still broken at enwiki and other non-test sites (go to w:en:WP:RA/NS and click any red link to test). Whatamidoing (WMF) (talk) 03:39, 9 August 2017 (UTC)
Copy-paste with middle click on Linux does not work properly
[edit]Hi. I tried to copy-paste some text by selecting text and by clicking with the middle button to paste it at the position of the click. It works with classical wikitext editor but not with the 2017 wikitext editor. Indeed, the text is pasted at the position where the cursor is, not at the position of the click. Pamputt (talk) 01:43, 15 May 2017 (UTC)
Essential changes need on the new wikieditor
[edit]The New wikieditor is very good. It is intelligent also . I need some essential things missing with old wikieditor.
- The button to add my signature in articles - This is missing. In talk pages click of a button is faster than typing ~ 4 times . Must need a dedicated button on the bar
- Gallery and Reference list are more important than a heirogliph and musical notation
- The single click button to place a redirect is missing. It is a frequently used button in old wikieditor.
- Bold, Italic are frequently used buttons. We need dedicated buttons there also.
- Font problem. On source edit mode the text appear narrow and small - more pressure on eyes.
Find and replace is great. Expecting syntax heighlighting. Ranjithsiji (talk) 17:47, 19 May 2017 (UTC)
- There have been many requests for a signature button (for other pages/not for encyclopedia articles), especially for people who write in non-Latin languages. The button is in the Insert menu: Insert > More> Your signature. (On my keyboard, it's faster to type ~~~~ than to take my hands off the keyboard and click any button.) You might be interested in phab:T166494.
- There isn't enough space on a computer screen to make everything "important" be in the main toolbar.
- I filed a report about the font size at phab:T168092; you may have an e-mail message about that now. Whatamidoing (WMF) (talk) 20:21, 16 June 2017 (UTC)
- IF you can give some keyboard shortcuts then that will be Ok. I know that there not enough space to place everything.
- Request of Shortcuts for
- Place Signature
- Place a redirect on the page
- Also another requirement is to just rearrange the gallery and Reference before the hieroglyph and musical notation. Is that possible. Ranjithsiji (talk) 07:36, 17 June 2017 (UTC)
- I believe that the
<references />
item (to make the list) was placed at the end so that it would be easier to find ("all the way down" is easier than "somewhere in the middle"). - Does your wiki use galleries frequently? Whatamidoing (WMF) (talk) 22:12, 18 June 2017 (UTC)
- Yes. We use a lot of image galleries in almost all articles. They make articles more informative and beautiful. Ranjithsiji (talk) 15:12, 27 June 2017 (UTC)
- I checked 30 articles with Special:Random at mlwiki, and 10% of them had galleries. I've made a general request for the order of items to be reconsidered, and used galleries as an example of what should be considered. Whatamidoing (WMF) (talk) 19:44, 5 July 2017 (UTC)
- In the case of mlwiki the Special:Random will not give you the real situation. Because lot of stub articles with no image available are there(Malayalam is a small wiki with 50000 articles in total). Most articles translating from English to Malayalam articles are commonly using the images and galleries. The point is we are using galleries, references, redirect more frequently than hieroglyph and musical notation in our wiki. Ranjithsiji (talk) 03:21, 7 July 2017 (UTC)
- Yes, I agree that you're using that more than others. I did a proper search just now, and the gallery tag is used at 6% of articles at the Malayam Wikipedia, compared to 4% of articles at the German Wikipedia, 2% of articles at the English Wikipedia, and 0.5% of articles at the English Wikivoyage.
- I didn't check, but I suspect that galleries are used at all of these more often than hieroglyphics and musical notation. Whatamidoing (WMF) (talk) 19:10, 12 July 2017 (UTC)
- sorrjjj ja sam pricam hrvatsii? Savovidicmmm (talk) 09:09, 10 August 2017 (UTC)
- You can write in any language you want. Please start a new topic (the white box at the top of 2017 wikitext editor/Feedback). Whatamidoing (WMF) (talk) 20:20, 11 August 2017 (UTC)
Links to other wikis
[edit]There needs to be a "link to another wiki" tool that would add the proper prefix to the link (e.g. Wiktionary -> wikt, or even French Wiktionary: wikt:fr:).
Right now it is like the good old wiki code: you need to know and write the right prefix yourself.
Another small issue: Wiktionaries are case sensitive, so the capitalization of the first letter also has to be fixed manually when creating such a link (highlight text > make link). And even if I do change it, the final link has its prefix capitalized too (sure the link works but it's not a good habit). Darkdadaah (talk) 13:52, 23 May 2017 (UTC)
- If you just paste an external link to another wiki it will get converted to the correct notation. ESanders (WMF) (talk) 16:51, 26 May 2017 (UTC)
- One related bug has been solved: phab:T166593.
- But you may be affected by phab:T133535 or another problem. Whatamidoing (WMF) (talk) 20:26, 16 June 2017 (UTC)
Better, but still less usable than 2010 editor
[edit]I tried the actual vesrion and then I switched back to old wikicode editor. Why?
- sssslllloooowwww even if I have fast internet connection - 75%
- when using it, my user script for cosmetic changes does not work - 20%
- [save edit] button on the top is confusing for me - 5% JAn Dudík (talk) 13:04, 24 May 2017 (UTC)
- The unusably-bad time issue (Phab T154843) and incorrect/faulty preview engine (Phab T154843) have been identified by EnWiki consensus as issues that block deployment of this editor from Beta to actual use. Both of these issues are due to the decision to replace the wikitext editor with a new wikitext mode inside of Visual Editor. At this time there is no clear indication from the WMF that either of these issues can or will be fixed.
- The only answer for scripts is that the community would have to re-program each one individually, to work with the VisualEditor system.
- I don't recall any notable discussion regarding the location the save button.
- It would be appreciated if you could report your load times for:
- Those are two test cases where we have been collecting load time reports. Many reports for United States are around 30 seconds, and reports for the extremely large List of named minor planets can run upwards of two minutes. (If the browser gives a time-out error message for minor_planets, you can click to continue loading.) Alsee (talk) 14:13, 24 May 2017 (UTC)
- My times from cilck to [edit] to the end of loading page
- United States - 75 sec (normally 18 sec)
- List - 140 sec (normally 55 sec)
- for comparison
- https://en.wikipedia.org/w/index.php?title=Vidov - 6 sec (normally 4 sec) JAn Dudík (talk) 09:01, 26 May 2017 (UTC)
- Can you add to that what kind of PC you have, which browser you use etc ?? Without that those numbers are hard to interpret. —TheDJ (Not WMF) (talk • contribs) 21:15, 29 May 2017 (UTC)
- Also, what if you go to this version (might look weird) and then click edit source ? What's the time then ?
- If that version makes a significant difference, then the problem is likely somewhere in a userscript or gadget or something... —TheDJ (Not WMF) (talk • contribs) 21:23, 29 May 2017 (UTC)
- Acer Aspire, Win10 Home 1703, 8GB RAM, AMD 1,80 GHz / Opera 45
- USA is safemode - 130 sec (normally 14 sec)
- en is not my home wiki, so I have only my global scripts here. JAn Dudík (talk) 07:47, 30 May 2017 (UTC)
- I tried it again and again:
- - 40 sec, after 15 sec loading bar goes to 2/3 and then 20 sec no progress.
- - 65 sec, after 20 sec 2/3, then long waiting for loading Anthem and March player
- - 150 sec, waiting for player
- - 70 sec, player (i moved cursor after 60 sec)
- - 26 sec - i was moving cursor for whole time and player loads quickly
- So it seem there is some problem with loading player and editor is waiting for it (or for cursor moving?), but when i move cursor, loading quickly finish JAn Dudík (talk) 08:00, 30 May 2017 (UTC)
Feedback
[edit]Hello, thanks for this tool. I used it with the french wikipedia. Please pardon my basic level of english. I'm sorry if someone already told this but I won't read each post on this page :-/
- I'd like to sign my messages with only one button, not by typing ~ ~ ~ ~ each time.
- When I preview my changes before publishing, I'd like to see categories on the bottom and languages on the left
Anyway, you did a great job. Thank you again. El Funcionario (talk) 09:44, 25 May 2017 (UTC)
- Hey!
- For signature, you probably know there is a button for that (Insert menu --> More --> Your signature), but, you could also help us choose a shortcut for that! Task T166494
- The rest is covered by https://phabricator.wikimedia.org/T153534 .
- TTYS! Elitre (WMF) (talk) 14:32, 14 June 2017 (UTC)
- Also, it's okay to write in French on this wiki. This is a multi-lingual wiki. Whatamidoing (WMF) (talk) 20:08, 16 June 2017 (UTC)
Copy/Paste problem
[edit]When i try to paste something in the editor, it just make a newline.
Vivaldi, Ubuntu 64bit (it worked days ago) Leonekmi (talk) 12:06, 27 May 2017 (UTC)
- Can you please give a specific example of something you tried to paste, and where?
- Have you checked whether the browser needs to be updated? (These are the only reported issues with newlines in the editor so far.) Elitre (WMF) (talk) 10:27, 29 May 2017 (UTC)
- Simple text Leonekmi (talk) 15:13, 29 May 2017 (UTC)
- Does this happen if you copy a single word from the middle of a sentence, and paste it into the middle of an existing sentence, or only if you copy and paste the end of a pargraph? How many newlines do you get? (For example, one before and one after, or only one after the pasted text?) Whatamidoing (WMF) (talk) 19:12, 16 June 2017 (UTC)
- This happen in every case you mention. 1 newline Leonekmi (talk) 20:26, 16 June 2017 (UTC)
- I am having a similar issue. One workaround that might work for you is to copy paste twice, which works for me. Mvolz (talk) 08:24, 27 August 2017 (UTC)
- It turns out my issue was a chrome extension; have you tried turning off all your extensions and commenting out all your JS scripts in User:Username/Common.js? One of them may be the culprit. Mvolz (talk) 15:23, 28 August 2017 (UTC)
Missing: Option to easily add signature
[edit]The current wikitext editor seems to be missing an option to easily add signature to talk page discussions. It would be nice if it was enabled in some way. Two possibilities are:
- Keyboard shortcut
- Option in menu bar
Expecting one soon! Kaartic [talk] 05:20, 28 May 2017 (UTC)
- The keyboard shortcut is
~~~~
. - The option in the menu bar is halfway down in the Insert menu: Insert > More > Your signature. Whatamidoing (WMF) (talk) 19:08, 16 June 2017 (UTC)
- Yeah, but when I was mentioning about signature I had the signature added by the old wikitext editor (- -~~~~) in mind. I guess a keyboard signature to add would be useful for users who are in a situation to sign often. (Obviously, this isn't required if Flow is used in places requiring user interaction)
- Regarding the option, it would be better to show it more explicitly as a way of inducing the user to sign their posts in Talk pages and other pages where signature is required. Kaartic [talk] 08:16, 18 June 2017 (UTC)
- But for Me. I want to switch to engish keyboard layout from Malayalam first to get the ~ character. then press ~ four times is the only way. If i get a keyboard shotcut like Alt+Shift+S or something like that for this thing then it is a way better . If I am typing in english pressing a ~ four times is not a big deal. But changing the keyboard layout from Malayalam to english is a different scenario. Hope you understand.
- Now my keyboard short cut is
- Super+Space > Select English > ~ four times > Super+Space > Select Malayalam
- What I expecting is
- Alt+Shift+Somekey
- No changing of keyboard layout Included.
- Also I think lot of non latin people face this problem. Ranjithsiji (talk) 07:47, 17 June 2017 (UTC)
- That's right. Other language editors would be a great audience of this shortcut. Kaartic [talk] 08:18, 18 June 2017 (UTC)
Interferes with WP:RFPP (request for page protection) on enwiki
[edit]I enabled the new wikitext editor. It's mostly okay, but a bit slower to start up than the old one.
One problem I've had: it massively interferes with the workflow that admins use on English Wikipedia's RFPP (request for page protection).
The new editor does not show the editing notice that appears at the top of the page, which includes the "Administrator instructions" which you use to work out what RFPP template you include to basically say that the request has been closed (either successfully or not). Not being able to see this edit notice is a problem. If you then go and find the administrator instructions, the text you copy and paste then gets "escaped" in the editor (with code and nowiki tags).
This turns an otherwise simple administrative process into a rather long-winded one. Is there any way of turning off the new wikitext editor on specific pages (like RFPP or other admin/process pages) until these issues have been fixed? —Tom Morris (talk) 09:21, 28 May 2017 (UTC)
- Now, that's a username I hadn't read in a while. Thanks for stopping by to leave feedback.
- When I edit en:Wikipedia:Requests for page protection (not just a single section), I see both an edit notice that recommends following instructions (linked), and some commented example code at the top of the page to generate requests. If I open the linked instructions in a different tab I just land at en:Wikipedia:Requests_for_page_protection#Instructions. So if I copy the examples from there, or from the commented lines, and paste them, there are no nowiki tags added. (However, pasting with CTRL-SHIFT-V prevents any tags from being added). Elitre (WMF) (talk) 09:46, 29 May 2017 (UTC)
- (Hey Elitre! I'm still lurking around!)
- So, the page I'm looking at is Wikipedia:Requests_for_page_protection/Administrator_instructions
- . As an administrator, closing a request requires you to add an indented response using
- (e.g. "{{RFPP|s|one week}}" to say it has been semi-protected for a week). For the common ones, admins who frequent RFPP tend to know them (s for semi-protect, p for full-protect) but for the less commonly used ones like template protection (tp), extended confirmed (ec) and pending changes (pd) it is pretty common to look them up on the Administrator Instructions page above
- , which is helpfully transcluded into the edit page as an edit notice.
- When I tried to answer an RFPP request the other day, it took me about 5x longer than usual because the new editor didn't show me the edit notice, and when I copied the text from the Administrator instructions page, it came through with code and nowiki tags embedded.
- In general, I actually like the new wikitext editor, especially the integration with Citoid. Being able to just paste a link in and get a pretty comprehensive ref tag added is really nice. —Tom Morris (talk) 14:11, 29 May 2017 (UTC)
- Ah, "not just a single section". As an admin, responding to a request, generally I edit the single section so as to not edit conflict with other admins closing requests on RFPP. —Tom Morris (talk) 14:13, 29 May 2017 (UTC)
- The link to the admin's instructions could be added to en:Template:Editnotices/Page/Wikipedia:Requests for page protection: and if the examples there were formatted in plain text, like the ones at Wikipedia:Requests_for_page_protection#Instructions, you'd be fine, because the editnotice is visible even in section editing, so you can right-click to open it in different tab.
- I mean, the editnotice that says "Please ensure you follow these instructions before making a request. ..." is the only one I see also in the old wikitext editor when editing the requests page?
- (PS: I think that the section editing to avoid conflict thing has actually been a myth for years now, but that's something for later.) Elitre (WMF) (talk) 14:32, 29 May 2017 (UTC)
- The admin instructions (specifically https://en.wikipedia.org/wiki/Template:RFPP/codes) are transcluded in the edit notice you link to. See "RFPP administratior notation templates [show]". I'll happily change the formatting to plain text in that template, but there's still an issue here with the editnotice not displaying when editing a section using the new wikitext editor. It shows when you use the old one. —Tom Morris (talk) 10:42, 30 May 2017 (UTC)
- Not in my browser. However, we may be talking about https://phabricator.wikimedia.org/T154204 . That's a case I can reproduce. Elitre (WMF) (talk) 11:08, 30 May 2017 (UTC)
- Mere mortals like us see this:
- |Please ensure you follow these instructions before making a request. In particular, please place new requests AT THE BOTTOM.Please notify Wikipedia talk:Twinkle and Cyberpower678 of any proposed changes to section headers or your edit may mess up requests for page protection using Twinkle or archiving by Cyberbot I.
- |}
- But Template:Editnotices/Page/Wikipedia:Requests for page protection has some content that is only shown to admins, and I'm guessing that this isn't shown. @Tom Morris, is it failing to show the admin-only content? Whatamidoing (WMF) (talk) 19:06, 16 June 2017 (UTC)