Wikipedia talk:AutoEd

From Wikipedia, the free encyclopedia
Jump to: navigation, search

AutoEd with other scripts[edit]

I just installed AutoEd, however it doesn't seem to be doing anything other than adding an "auto ed" link to my vector skin that switches to edit mode and makes no changes. I tried disabling WikEd (through the gadgets panel in preferences) and got the same results. I use a number of other scripts as well (here's my common.js and I also use some gadgets). Is there something simple I seem to have missed, or should I start troubleshooting by disabling other scripts? I'm on Chrome 15 right now (won't have a chance to test on Firefox till later). —danhash (talk) 17:11, 31 October 2011 (UTC)

I got it to work. I missed some of the documentation on custom listing my modules and stuff. Currently everything is working, except for the dashes module. If I enable dashes.js, it seems to be the only module that does anything (whitespace etc. is not fixed, only dashes). Should I take this to GregU? —danhash (talk) 21:41, 10 November 2011 (UTC)
Posted to dashes.js talk (seems to be a problem with dashes.js). —danhash (talk) 20:10, 21 November 2011 (UTC)
Seems to be a problem with Chrome (more info at dashes.js talk here). —danhash (talk) 19:38, 26 January 2012 (UTC)

Remove spaces between ref tags[edit]

Could you add the functionality to remove spaces between ref tags? That is, change

</ref> <ref



Thanks --Decstop (talk) 23:12, 18 February 2012 (UTC)

That would be great. Other reference punctuation fixes like moving punctuation before a reference instead of after it and removing whitespace between punctuation and a reference would be very helpful. AWB does this, but to have the functionality in AutoEd would be helpful. —danhash (talk) 15:57, 27 March 2012 (UTC)

Also change </ref>{{dead link}} to {{dead link}}</ref> per Template:Dead_link#Examples Illia Connell (talk) 01:30, 23 May 2012 (UTC)

FYI: problem with pi article[edit]

FYI: an editor ran this tool on the pi article, and it introduced a problem into an important math forumla. I undid the change, but I thought the tool owners would want to know so they could research and solve. If you look in the rev history of pi; look at the article after the tool was run: you'll see a large red warning message in the middle of the article. --Noleander (talk) 12:53, 16 April 2012 (UTC)

Remove image captions without an image from infoboxes[edit]

Could you automate edits like this: [1]? Thanks Illia Connell (talk) 15:25, 19 May 2012 (UTC)

Not working?[edit]

AutoEd does not seem to be working for me right now. What is going on?  Liam987(talk) 08:07, 25 May 2012 (UTC)

It should ignore anything inside < syntaxhighlight > tags[edit]

i.e. programming code. It's making a real mess. - Richfife (talk) 20:07, 9 July 2012 (UTC)

AutoEd breaks redirects[edit]

It changes #REDIRECT to # REDIRECT and this breaks it. I doubt many people would use it on such pages but worth noting. --JetBlast (talk) 19:44, 26 August 2012 (UTC)

ping, still doing it in 2014. (tJosve05a (c) 10:40, 23 January 2014 (UTC)
Fixed. Thanks! Plastikspork ―Œ(talk) 22:54, 5 October 2014 (UTC)

Adding blank lines[edit]

See User talk:Gareth Griffith-Jones#Adding blank lines. Please amend AutoEd (which I don't use myself) so that it doesn't insert blank lines within bulleted lists, because this gives rise to MoS and accessibility issues. --Redrose64 (talk) 16:24, 2 September 2012 (UTC)

Whatever made those particular changes was not AutoEd, as far as I can tell. I just attempted to reproduce the edit, and I was not able to do so. Plastikspork ―Œ(talk) 16:42, 3 September 2012 (UTC)
It was wikEd. -- Gareth Griffith-Jones/GG-J's Talk
-- Gareth Griffith-Jones/GG-J's Talk 09:11, 13 October 2012 (UTC)


Hi, I use the Dashes script that calls Auto Ed. That script is unchanged but from late yesterday the script has stopped working and the tab now show "auto ed" and clicking the tab gets an error "AutoEd/core.js autoEdFunctions is undefined". Has there been some change to Auto Ed in the last couple of days that would cause this problem or could someone point me in the right direction. Keith D (talk) 17:46, 29 October 2012 (UTC)

I am also having this trouble on Firefox. Any help would be much appreciated. Thanks. Delsion23 (talk) 21:22, 30 October 2012 (UTC)

It changed from having a "–" link to an "AutoEd" one, but the link still does the job for me. I'm using Safari 5.1.7 on a MacBook Air running OS X 10.6.8. Interestingly, two AutoEd links show up, where there used to be two dashes links. Here's my commmon.js. David1217 What I've done 02:27, 31 October 2012 (UTC)
  • I ran Auto Ed basic here and it missed the dashes. — Crisco 1492 (talk) 05:43, 31 October 2012 (UTC)
From comments on the village pump it looks as though it may be just a Firefox problem. Keith D (talk) 13:34, 31 October 2012 (UTC)
TheDJ made this change which should fix the problem. Might require purging your browser cache. Keith D (talk) 18:09, 31 October 2012 (UTC)
Still works for me, but the link is back to "–". David1217 What I've done 04:36, 6 November 2012 (UTC)

Still functioning?[edit]

Is this still working? I haven't gotten it to install on modern, or on a virgin monobook with no other scripts. ~ Amory (utc) 19:08, 4 March 2013 (UTC)

As far as I know, it still works. I have seen some edit summaries citing it, although I haven't tried it recently. I will have a look this weekend. Thanks! Plastikspork ―Œ(talk) 13:26, 8 March 2013 (UTC)
  • My dashes still don't work. — Crisco 1492 (talk) 14:48, 8 March 2013 (UTC)
So I got off my lazy ass and actually took a look at this myself - it's all on my end. The code calls directly from http://en, and as a user of https all those calls are blocked as insecure. Loads perfectly if I'm using http. I'm willing to change the links in all the subpages to //en to be server-neutral, that won't bork anything right? ~ Amory (utc) 22:46, 17 March 2013 (UTC)
Nice! Thanks for figuring out the problem. I have changed the various scripts to check if the base protocol is https, and modify the importScript accordingly. So, it should work now. I'm not sure why we switched from importScript to importScriptURI, but we did make that switch some time ago for some specific reason. Thanks again! Plastikspork ―Œ(talk) 00:14, 18 March 2013 (UTC)
Beautiful, thanks! ~ Amory (utc) 00:30, 18 March 2013 (UTC)

Some problems![edit]

I'm interested in using this very cool looking script, but I'm having some difficulty. I added: ('Wikipedia:AutoEd/complete.js'); to my monobook.js page (I use the MonoBook skin); but when I Ctrl+F5'd and went to a page the tab wasn't there! Does anyone have an idea of what I did wrong? --Yellow1996 (talk) 01:40, 19 March 2013 (UTC)

...without importScript. Heh heh! Nevermind! (always look before you copy + paste.) :) --Yellow1996 (talk) 22:40, 19 March 2013 (UTC)

AutoEd made a tiny bad edit on R.A. Dickey[edit]

Subtle and small, but a significant error nonetheless. It appears that this edit using AutoEd placed a space between "R." and "A." in the {{Infobox MLB player}} "name" field, changing the name to "R. A. Dickey" which is incorrect. Names without spaces between abbreviations are uncommon so this probably won't happen very often, and I'm completely unqualified to comment on how scripts work, but could/should it be updated to ignore name fields inside template data entirely? --Threephi (talk) 17:28, 29 March 2013 (UTC)

That wasn't AutoEd. That was someone making further edits before or after running AutoEd. Thanks! Plastikspork ―Œ(talk) 22:47, 5 October 2014 (UTC)


Could you add this User:Gimmetrow/fixRefs.js? It's pretty simple, and works, but would be more useful as part of a larger package of tools. I might add it to my own, but if it could be added to the full one dodgy refs the wiki over will be sorted quickly. Jamesx12345 15:30, 13 August 2013 (UTC)


Good job. I only had to do this by myself. -- Magioladitis (talk) 13:08, 2 September 2013 (UTC)

Same here and in many other places. -- Magioladitis (talk) 13:18, 2 September 2013 (UTC)

It also break the table in WOAA Senior AA Hockey League. (tJosve05a (c) 17:19, 26 February 2014 (UTC)
I'm not a code-' person myself, so I don't really understand how the script or how tables work, but in West Country dialects AutoEd breaks both tables. (tJosve05a (c) 17:34, 26 February 2014 (UTC)

The main problem is that instead of || valign=top | it should output | valign=top |. -- Magioladitis (talk) 09:09, 28 February 2014 (UTC)

Auto Edit Has disappeared[edit]

The the little drop down arrow it has gone walk about and I cant see it any more...any ideas/suggestions? -- MisterShiney 20:49, 11 October 2013 (UTC)

How to uncheck the "Watch this page" checkbox when using AutoEd[edit]

Is there a way to tell AutoEd that I want the "Watch this page" checkbox unchecked for AutoEd edits? I see the setting for checking/unchecking the "This is a minor edit" checkbox, but no corresponding "Watch" setting. Am I just missing it? – Jonesey95 (talk) 03:41, 13 November 2013 (UTC)

Answering my own question. Add this to core.js, just below the "minor edit" section:
// Uncheck 'Watch this page'
if( typeof( autoEdWatch ) == 'undefined' || autoEdWatch ) {
  document.forms.editform.wpWatchthis.checked = false;
Works for me, anyway. – Jonesey95 (talk) 23:26, 17 March 2014 (UTC)

Blank lines between headings[edit]

Looking at Running Man (TV series), I notice that BG19bot, running WP:CHECKWIKI, adds a blank line between heading lines.

AutoEd would remove that blank line.

WP:HEAD does say "Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window."

Blank line or no blank line, I think the bots should be consistent.

What do you think?

NYDirk (talk) 21:51, 23 January 2014 (UTC)

Done! At least AutoEd should no longer change them if it's 1 blank line or fewer. Thanks! Plastikspork ―Œ(talk) 22:45, 5 October 2014 (UTC)
NYDirk, AutoEd is back to removing blank lines after a section heading. See the message below this one. Cheers! {{u|Checkingfax}} {Talk} 01:10, 18 November 2015 (UTC)

Blank line after heading[edit]

It seems that AutoEd is removing blank lines after a section heading. According to the MoS section on section headings these lines are perfectly bona fide. Many editors prefer to have them. Please disable this feature of AutoEd. Thanks and regards, --EnOreg (talk) 06:50, 29 April 2014 (UTC)

Done! Plastikspork ―Œ(talk) 22:44, 5 October 2014 (UTC)
Plastikspork, AutoEd is back to removing blank lines after a section heading. Can you disable that again? Cheers! {{u|Checkingfax}} {Talk} 01:07, 18 November 2015 (UTC)
Checkingfax, Can you provide an example page where this is happening? I just tried adding a blank link after a section heading and my AutoEd did not remove it. Thanks! Plastikspork ―Œ(talk) 02:14, 19 November 2015 (UTC)
Hi Plastikspork. I'll get back to you the next time it happens. Usually does it in See also, and External links. I like your tool. I wish it did even more. Cheers! {{u|Checkingfax}} {Talk} 06:55, 19 November 2015 (UTC)

HTML entities[edit]

Calling to mind this passage from MOS:MARKUP:

An HTML entity is sometimes better than the equivalent Unicode character, which may be difficult to identify in edit mode; for example, Α is understood where Α (the upper-case form of Greek α) may not be.

I question whether it is a good idea to provide conversion of HTML entities for Greek letters to corresponding Unicode characters. I especially question lumping the letters that look identical to Roman letters (e.g. Α) with letters that are easy to distinguish from any Roman letter (e.g. Ω). Jc3s5h (talk) 15:24, 9 May 2014 (UTC)

AutoED not working[edit]

I've noticed AutoED is no longer working correctly. The option appears in the "More" drop-down menu, but it doesn't clean up the article automatically. Anyone else experiencing this issue? --k6ka (talk | contribs) 01:39, 9 July 2014 (UTC)

Pinging maintainers: @Drilnoth:, @Plastikspork: --k6ka (talk | contribs) 01:40, 9 July 2014 (UTC)
Also pinging @Krinkle: and @Nihiltres:, who made recent edits to the core.js script. – Jonesey95 (talk) 03:58, 9 July 2014 (UTC)
My edit there is probably unrelated to the bug, because it affected only the part that adds the tab, and shouldn't functionally change the script much if at all. I suspect that the changes in autoEdQueryString() may be causing the problem, so I decided to make another edit and replace the function entirely with use of mw.util.getParamValue()—no need for redundancy. Is the problem still present? {{Nihiltres|talk|edits}} 15:04, 9 July 2014 (UTC)
@Nihiltres: Yes it is. --k6ka (talk | contribs) 16:19, 9 July 2014 (UTC)
Since this fix is not urgent and the code was working before your changes, would you generous, amazing javascript programmers mind working in a sandbox rather than making changes to the live core.js script? Some of us use this tool every day to fix articles. Thanks. – Jonesey95 (talk) 18:11, 9 July 2014 (UTC)
Three days and still no fix. --k6ka (talk | contribs) 13:53, 12 July 2014 (UTC)


Update: AutoEd still works... sort of. You need to open the editor before clicking the AutoEd function. It should then clean up the article. This works at least on my end. --k6ka (talk | contribs) 14:19, 15 July 2014 (UTC)

I believe is likely a race condition since the code at Wikipedia:AutoEd/complete.js has a few calls to importScriptURI(...), which is not synchronous if I remember correctly, and Wikipedia:AutoEd/core.js calls autoEdFunctions which is defined only after the call to core.js. 15:35, 15 July 2014 (UTC)
It's absolutely a race condition. I don't use AutoEd, but I imported the complete.js through the console as an experiment, and got an undefined variable error on AutoEdUnicodify(). I immediately moved the call to core.js to the end of complete.js to ameliorate things, but it's not a true fix (won't prevent race-condition errors, just makes them less likely). I'd suggest that, since we must have everything loaded, we could make a loader function to avoid the problem. AFAIK user scripts can't use mw.loader.using() properly, so we get to implement something ourselves. Here's an idea: make the list of modules to be loaded an array, have the loader function load them and include a callback at the end of each module that checks if all the modules are ready. The catch is that we would then need to modify all the modules to include that callback function, not including any other necessary structural changes. Here's a 30s example (obviously not complete!) of what I'm thinking:
AutoEdModules = ["unicodify.js", "isbn.js", "etc.js"];
AutoEdWaitingCount = AutoEdModules.length;
function AutoEdLoad () {
    jQuery.each(AutoEdModules, function () {
        importScriptURI(AutoEd_baseurl + this);
function AutoEdLoaderCallback () {
    if (AutoEdWaitingCount === 0) {
        importScriptURI(AutoEd_baseurl + 'core.js');
This would let modules load asynchronously but only execute once everything was ready. As a bonus, we could do away with the awkward AutoEdFunctions() snippet by having modules add themselves automatically to a list of functions to be executed. The catch is that all existing modules would have to be adapted to fit this model. {{Nihiltres|talk|edits}} 16:51, 15 July 2014 (UTC)

AutoEd (?) breaking infoboxes[edit]

After running (what I think is a functionality controlled by) AutoEd on a biography with a person infobox (e.g., Frank McLaury), the infobox failed to display. I am referring to the function to "Fix caps in headers and lists". When executed, the initial characters of the parameters for the infobox are converted to initial caps, as in the following example:

{{Infobox criminal | Name = Frank McLaury | Image_name = Fmclaury.jpg | Image_size = 220px...

This breaks the infobox which requires lowercase parameters. If this functionality is not implemented by AutoEd, I'd appreciate a redirect to the correct script. Thanks.

btphelps (talk to me) (what I've done) 22:03, 5 October 2014 (UTC)

@Btphelps: Doesn't seem to be a problem with AutoEd. I just ran it on the McLaury article, and all it does is change some whitespace around the section headings. Do you have a specific diff for the edit showing the breakage? Plastikspork ―Œ(talk) 22:41, 5 October 2014 (UTC)
I caught the original issue before I saved it, so I created a new instance for you to review. Try selecting the entire article (CTRL + A on a PC) first, then click the "Fix caps in headers and lists" button. — btphelps (talk to me) (what I've done) 07:01, 6 October 2014 (UTC)
btphelps, Are you sure that's AutoEd? It sounds like WP:WikEd per this search. Good Luck! Plastikspork ―Œ(talk) 23:57, 6 October 2014 (UTC)
No, I'm not sure which script supports that functionality. Thus the (?) in my original post. — btphelps (talk to me) (what I've done) 01:48, 7 October 2014 (UTC)

Obsolete HTML[edit]

Please add change from obsolete HTML to replacement.

  • <big>...</big> → {{big}}
  • <center>...</center> → {{center}}
  • <tt>...</tt><code>...</code>
  • <strike>...</strike><s>...</s>

<font> is probably too difficult to revise. --  Gadget850 talk 17:05, 28 October 2014 (UTC)

Hello Gadget850, there is no consensus about this, please compare first WP:HTML5!? User: Perhelion 14:43, 29 October 2014 (UTC)
There is no official statement from Wikimedia "Wikitext is not HTML". For example the <big>...</big> is in the Wikieditor (it was suggest to WONTFIX). HTML4 was long before Wikipedia exists, but Wikimedia has decided to allow all this obsolete tags!?! Why? Because they are much more practicable as Wiki-syntax (against cryptic CSS)!? User: Perhelion 12:08, 12 November 2014 (UTC)
I am dropping this proposal. As I look deeper, much of the use of <center> is either redundant in that it is used to center elements that already have center styling or 100% width or the elements have parameters for center styling. --  Gadget850 talk 16:53, 12 November 2014 (UTC)
I have been updating WP:HTML5 with various methods for updating obsolete markup. --  Gadget850 talk 11:24, 8 December 2014 (UTC)

Obsolete installation guide?[edit]

AutoEd, for me, using Firefox, appears under the "More" drop-down menu, not on a tab "at the top of the article...between move and history". Is that true generally? Should the Installation Guide be modified to take that into account? Dhtwiki (talk) 07:26, 30 October 2014 (UTC)

Yes, that menu item changed sometime in the last year, from a bare triangle to a triangle with the word "More" next to it. – Jonesey95 (talk) 13:44, 30 October 2014 (UTC)

AutoEd incorrectly replacing dashes in DOI values?[edit]

This edit claims to have been done with AutoEd. I do not have a way of checking whether AutoEd or a manual change incorrectly converted a hyphen to a dash within a DOI value, but if AutoEd did it, that is a bug that should be fixed. DOI values use hyphens and will break if dashes are used instead. Thanks. – Jonesey95 (talk) 18:02, 7 November 2014 (UTC)

did not appear[edit]

I installed AutoEd but it did not appear on my toolbar. Anyone who can help? SparrowHK (talk) 01:54, 8 December 2014 (UTC)SparrowHK

SparrowHK, did you check at the top of the page in the "More" links next to View history and the page watch star? Plastikspork ―Œ(talk) 02:54, 8 December 2014 (UTC)

Yes, I did. SparrowHK (talk) 03:54, 8 December 2014 (UTC)SparrowHK

I moved it to your common.js for you. You should try moving the other stuff you put in monobook.js and vector.js to common.js. The common.js should work for all skins, while the vector and monobook ones are specific for only the vector and monobook skins. If it still doesn't work, you might want to try removing everything else from those files to make sure it's not tripping on errors before it gets a chance to load AutoEd. Thanks! Plastikspork ―Œ(talk) 06:25, 8 December 2014 (UTC)

Getting Errors[edit]

When attempting to use AutoEd, I am gettin the error: "Exception encountered, of type "BadMethodCallException"" Ormr2014 | Talk  23:14, 18 May 2015 (UTC)

NM it's working now... Ormr2014 | Talk  00:18, 19 May 2015 (UTC)


Does anyone know why AutoEd won't go off if I click it after editing a page? ThanksKeith-264 (talk) 06:36, 7 July 2015 (UTC)

How do you use it?[edit]

Do you just go on an article, pick the AutoEd option and then press save? I was recently reverted when I did this for nonconstructive changes.Rubbish computer 16:44, 4 August 2015 (UTC)

Could you be more specific? What was reverted and why? You seemed to have used AutoEd a lot recently. Of course, you are responsible for knowing what any (semi-)automated process you run is doing before you save. Dhtwiki (talk) 02:37, 5 August 2015 (UTC)
In response to a message in my talk page I posted an explanation to User talk:Rubbish computer#AutoEd as to why I thought that a specific edit was unsuitable. -- PBS (talk) 06:11, 5 August 2015 (UTC)
@Dhtwiki: The automatic preview wasn't working but I've been given some advice elsewhere on fixing this and will try that. Apologies for saving without checking what the changes were. Rubbish computer 13:00, 5 August 2015 (UTC)

Script removes necessary character escapes from Alt text[edit]

While most modern browsers might not have a problem, I understand it's recommended practice to escape symbols such as quotation marks and ampersands within alt text. The script currently doesn't recognise this, and instead replaces all instances of &quot; and other escaped entries, even in alt text strings where they are appropriate. --Paul_012 (talk) 03:36, 19 August 2015 (UTC)

Stub spacing[edit]

The other day I came across a discussion between two editors where one was blaming the other that they did not leave two empty lines before the (first) stub tag. We actually have a suggestion at WP:STUBSPACING saying "It is usually desirable to leave two blank lines between the first stub template and whatever precedes it." AutoEd will remove one of the lines, Diff of Bill Plaschke. Personally I'm a bit so-what, just thought I'd let you know. -- Sam Sailor Talk! 06:58, 14 October 2015 (UTC)

Sam Sailor, should be fixed now. Thanks! Plastikspork ―Œ(talk) 02:39, 19 November 2015 (UTC)
No, on the contrary I forgot my manners, it is I who ought to thank you for making such a script. Thank you. Sam Sailor Talk! 06:29, 19 November 2015 (UTC)

How do I make a custom regular expression replacement[edit]

I want to tidy up opus numbers on (classical) music pages -- these are often written "Op.123", which should be "Op. 123". So I need to be able to apply regexp replace on the page. Is there a simple way I can add my own script to Autoed so I can run this when required? I imagine that it's easier to use the functionality already provided to access the page text as a string, but can't see how to provide a tab/button/whatever to do things just when required (rather than a generalised "tidy" function; I need to be able to do a quick visual check before committing changes).

Can someone suggest how to do this, or if applicable the Completely Different approach I should be taking? Thanks. Imaginatorium (talk) 12:48, 15 November 2015 (UTC)

Here's one of my custom scripts: User:Jonesey95/AutoEd/unnamed.js. You are welcome to copy it into your user space and play with it. Post a note on my talk page when you get stuck. Note that I use my own version of the "core" file and do not do the standard tidying. – Jonesey95 (talk) 15:33, 15 November 2015 (UTC)

Not adding space before forward slash[edit]

AutoEd stopped adding a space before the forward slash in named references. See Charles Manson named ref: <ref name="bugliosi"/>

Also, there is major horizontal white space showing in ref #1 between the numeral and where the text starts, and minor extra horizontal white space showing in refs: 1, 7, 9, 12, 20, 26, 27, 29, 32, 35, 38, 39, 42, 43, 50, 52, 53, and so on.

Ping me back. Cheers! {{u|Checkingfax}} {Talk} 00:57, 18 November 2015 (UTC)

Checkingfax, I am not aware of any requirement to add a space before the slash. Is this a problem? Also, I'm not sure what you are talking about with regard to minor extra horizontal space. Thank you! Plastikspork ―Œ(talk) 02:16, 19 November 2015 (UTC)
Hi Plastikspork. There is no requirement to add a space before the slash but it is one of your advertised features and I like it. I thought you'd want to know that it's not working.
Look down in the reference section at the first reference on Charles Manson page (linked above) and you'll see a bunch of empty space after the [1] for the link and before the link text starts. It happens to a lesser degree on about 25 other links. Thought your tool could find the errant white space and nuke it because I sure can't find it. Ping me back. Cheers! {{u|Checkingfax}} {Talk} 06:52, 19 November 2015 (UTC)

Moving s to inside the wikilink[edit]

Hi Plastikspork, I notice AutoEd is moving the s to inside the wikilink so: ]]s becomes s]] as in: field]]s is changed to fields]]. You can see an example at Agriculture but I did not approve the change and I left it be. Also, since field and fields both have separate disambiguation pages would changing the wikilink from ]]s to s]] also require a DAB update for that wikilink? MoS encourages us to put s, ed, ing, etc. outside the wikilink.

Checkingfax, it should only move the s inside if the link text is different from the link. I have not seen the MOS page which encourages moving the s outside, unless it would simplify the link. For example, [[dog]]s is shorter than [[dog|dogs]], but [[Field (agriculture)|Field]]s seems the same as [[Field (agriculture)|Fields]]. This feature was imported from one of the older parent scripts. Plastikspork ―Œ(talk) 00:52, 1 December 2015 (UTC)

Did you ever see the extra white space at Charles_Manson#References in for example ref [1]? UPDATE: Looks like WMF fixed it on the backend. It was all the repetitions of the named ref that were not showing up.

No, I never saw this. Plastikspork ―Œ(talk) 00:52, 1 December 2015 (UTC)

I notice AutoEd is now converting: /> to: / > as advertised. I like it!

I'm not sure where it is doing it, but I guess if it's correct, then great. Plastikspork ―Œ(talk) 00:52, 1 December 2015 (UTC)

Finally, AutoEd is not always creating an Edit Summary. Why is that? Ping me back. Cheers! {{u|Checkingfax}} {Talk} 23:09, 25 November 2015 (UTC)

It may fail if there is already a long edit summary, but it should always work if there is room to add an edit summary. There may be conflicts with other scripts, if they are modifying the edit summary. Thanks! Plastikspork ―Œ(talk) 00:52, 1 December 2015 (UTC)

Hi Plastikspork, Can you code autoEd to move apostrophe s to inside the wikilink if it is a piped wikilink? Like:
[[Apple Inc.|Apple]]'s would become [[Apple Inc.|Apple's]]? Cheers! {{u|Checkingfax}} {Talk} 09:30, 14 December 2015 (UTC)

In the first case, on the Apple is linked, and in the second case, the entire string is linked. Since they don't produce the same output, this case was excluded. Thanks! Plastikspork ―Œ(talk) 13:38, 31 January 2016 (UTC)

Name on drop down tab[edit]

Hi Plastikspork, On the drop-down tab AutoEd is named: auto ed

Should not that be AutoEd? Just sayin'. Cheers! {{u|Checkingfax}} {Talk} 10:07, 3 December 2015 (UTC)

nbsp being removed and replaced by plain space[edit]

Greetings Plastikspork or any (talk page stalker), autoEd is removing {{nbsp}} templates and replacing the {{nbsp}} template with a plain space. I know some editors go to a lot of trouble inserting the nbsp templates only to see their efforts go poof. I had to stop using autoEd Face-sad.svg because it was undoing the previous editors' additions. Ping me back. Cheers! {{u|Checkingfax}} {Talk} 10:40, 31 January 2016 (UTC)

Hi Checkingfax. Can you provide an example of an article where this is happening? Thanks! Plastikspork ―Œ(talk) 13:40, 31 January 2016 (UTC)
Hi Plastikspork: Rats. I bumbled that call. It is: User:Ohconfucius/script/MOSNUM dates (not autoEd) and I saw it on Mary, Queen of Hungary. That date script is a good one but I cannot use it if it is going to delete templates recently placed by other editors. Sorry for the false alarm. I just double-checked and MOSNUM dates for sure, cross my fingers hope to die, nukes the nbsp templates and replaces them with plain spaces which is odd to me. Cheers! {{u|Checkingfax}} {Talk} 13:56, 31 January 2016 (UTC)

Whitespace after Wikilinks[edit]

Might I suggest you move the call to autoEdWhitespace to be after autoEdWikinks instead of before it (in "formatter.js" and "complete.js")? With the current order, whitespace inside of a link is moved outside of it and preserved, even if it results in a space at the end of a line. (See the link to "Псыж" in this diff, which was using "formatter.js".) If you switch them, that doesn't happen. - dcljr (talk) 06:28, 26 August 2016 (UTC)

Adding a "Rules of use" section[edit]

I've been encountering editors using / abusing AutoEd more frequently, including making controversial mass edits and inconsequential changes using AutoEd. I'd like to suggest that a set of rules be added to the page, mirroring the following "Rules of use" at WP:AWBRULES

  1. You are responsible for every edit made. Do not sacrifice quality for speed and review all changes before saving.
  2. Abide by all Wikipedia guidelines, policies and common practices.
  3. Do not make controversial edits with it. Seek consensus for changes that could be controversial at the appropriate venue; village pump, WikiProject, etc. "Being bold" is not a justification for mass editing lacking demonstrable consensus. If challenged, the onus is on the AutoEd operator to demonstrate or achieve consensus for changes they wish to make on a large scale.
  4. Do not make insignificant or inconsequential edits. An edit that has no noticeable effect on the rendered page is generally considered an insignificant edit. If in doubt, or if other editors object to edits on the basis of this rule, seek consensus at an appropriate venue before making further similar edits.

Any thoughts on this proposed addition? Alansohn (talk) 20:21, 19 December 2016 (UTC)

I support the concept, but I think it doesn't make sense to post the same set of rules in two places, from which they will inevitably diverge. Let's just say on this page that all of the AWB rules apply. That way, if the AWB rules change, the AutoEd rules change with them. – Jonesey95 (talk) 08:50, 20 December 2016 (UTC)