Talk:PageRenameAuto-update — dev

Non-links are renamed

I noticed some false positives when I renamed w:c:tsto:A Rail of One City to w:c:tsto:A Rail of One City (event). Here's the corresponding diff: A Rail of One City (Expansion). Apparently all occurrences of the string were replaced on that page. — NoWay _{(talk · contribs)} 18:30, August 11, 2016 (UTC)

Is there a way the script could add a feature that renamed pages within the pages themselves? I mean, if I have a page with all of the information I need and (for some reason) I have to add a link to that page INSIDE the page itself, the script won't change that name and the script will take a lot of time to conclude the rename process (or won't finish at all). The reason why I'm asking this is because it would be a lot helpful when this happens within templates. See this thread for more information. Thanks in advance! Atenciosamente, Soul_Wade (Mural de Mensagens/Message Wall) 21:16, January 15, 2017 (UTC)

Update

This script needs i18n supports and a double-run protection to match the standard of this wiki scripts. leviathan_89 14:13, October 2, 2017 (UTC)

Issues on French wiki after moving to fandom.com

Hey! Here is my issue: my French wiki was just moved from "wikia.com" to "fandom.com". Before that, the script perfectly worked. But now it does not? First, when I'm on a page that I want to rename, I still click to "Rename & Update" but the script sends me to the English wiki (fandom.com/wiki/) while it should keep me on my French wiki (fandom.com/fr/wiki/). I added the "fr/" manually, but once I am on the rename page, the script keeps telling me "Page not linked on any pages." while it is clearly not the case per "Special:WhatLinksHere". So yeah... Might need some help here, please? :) Lady Junky 07:26, January 25, 2019 (UTC)

Thanks for the report, I've updated the script and now it's awaiting proper testing, submission and approval by staff. The script used a lot of relative urls which made it look in the English wiki instead of the current wiki being viewed, so the fix should go live after all those things happen (hopefully in order) -D 07:37, January 25, 2019 (UTC)

Thanks a lot! Really looking forward the update for this one :) Lady Junky 07:47, January 25, 2019 (UTC)

Flaw/Limit

Hi, when I've come to use the script to rename a page which has 67 links across the site, the page is auto renamed and the script doesn't process the changes.{{SUBST:User:Besty17/Sig}} 18:05, March 19, 2019 (UTC)

This might be related to a bug whose fix ~~is pending approval~~ has just been approved. Could you try again? (NB: It may take a few days for the relevant JS caches to expire. Thus, to ensure you're getting the latest approved version, you may need to tack on &debug=1 to the end of the Special:BlankPage URL that the Rename & update menu item directs you to.) puxlit (talk) 10:03, March 21, 2019 (UTC); edited 12:39, March 21, 2019 (UTC)

Rate limiter is ineffectual

It would appear that the current implementation of the rate limiter uses a setInterval with a default interval of 500ms. This translates to roughly 120 edits/minute, which exceeds the presently-configured maximum for logged-in users of 40 edits/minute. Increasing the default interval to 1500ms might address this matter, but it unnecessarily penalizes updates for pages with less than 40 dependants. Perhaps an adaptive approach could be taken, where we determine the target rate limit via /api.php?action=query&meta=userinfo&uiprop=ratelimits, save as fast as we can, then back off for an appropriate interval once we encounter a ratelimited? puxlit (talk) 16:42, April 7, 2019 (UTC)

Option to leave a redirect with the original page's name

This script has proven to be extremely useful to me and I want to thank the developers.

Do you think it would be possible to add an option to leave the original name's page as a redirect and not be deleted during the renaming process? Maybe by adding a checkbox where the user can decide whether or not they want to keep a redirect to the original page's name.

There are many occasions where one would be willing to keep the original page's name as a redirect. For example, let's say I have a page called "Akumajo Dracula" and I want to rename it to "Akumajō Dracula", and let the script update all its link iterations throughout the wiki. However, I would also like to keep the original name "Akumajo Dracula" redirecting to the new page's name to make sure that users that may type it on the search box with the original (and easier to type) name land on the correct page.

This would also be really useful for cases where a wiki in another language has a link to its counterpart on our end that is using the older name. That will surely save us the chore of having to go to the other language's wiki, investigate if the link exists, and manually update it. And the same would go for when they change pages' names using this script and we're still using their old ones without knowing they had already changed them.

I frequently have to manually recreate the original page's name as a redirect to the new one after using this script for these reasons.

I hope you can give this suggestion a thought and thanks for reading.

Regards.

--{{SUBST:LaVey (signature)}} 21:22, April 12, 2019 (UTC)

I second this. It would be very helpful in saving the time of having to go back and recreate the pages as redirects. ZioreRogue (talk) 00:17, 11 August 2021 (UTC)

Ditto, though I honestly thought it used to have that option (probably another script then). --Sammm✦✧(talk) 04:30, 7 October 2021 (UTC)

French

Hello,

I would like to translate the script so that it is also compatible in French, but what should I do?

Regards,

Louky (discussion) 11:59, September 30, 2020 (UTC)

CategoryRenameAuto-update

Hi, can someone explain what "Functionality merged into PageRenameAuto-update." means? When I saw it, I thought other than lack of maintenance, the wording "Functionality merged into" meant that PageRenameAuto-update (this script) could now be used to replace the deleted script, however when I attempt to use it on a CAT, the message I got was:

The page "Category:Blah" was unable to be moved to "Category:Blahblah" for reason: cant-move-category-page.

(Blah in the above was just an example). I mean, if you can't move CATs, that kind of just means there's currently no script functioning similar to en:CategoryRenameAuto-update, correct? Just trying to see if I'm understanding it right. (I suppose I can use MassEdit or MassCategorization, just that it'd have more steps than what the deleted script previously needed.) --Sammm✦✧(talk) 04:30, 7 October 2021 (UTC)

Which wiki did you get that error on? It might be that you don't have permissions for moving category pages. -- Cube-shaped garbage can 09:12, 7 October 2021 (UTC)

w:c:harrypotter, I'm a content moderator there and I had no problem using the now-deleted script previously. --Sammm✦✧(talk) 09:20, 7 October 2021 (UTC)

Yeah, because the now-deleted script did not actually move the category, it deleted and recreated it. It seems like content moderators do not have the move-categorypages right that is required to move categories, but you can probably contact Staff to grant the right. -- Cube-shaped garbage can 17:26, 7 October 2021 (UTC)

Hi, yeah, I was under the impression that what the old script does, is actually obtaining all content categorized (as a list), then process said list, basically recategorizing them under the new name, also creating a new category and pasting the description from the old category. A lot of steps in one go, none of them particularly sounds like it needed additional rights. Any idea which Staff in particular I should be contacting? Thanks! --Sammm✦✧(talk) 03:41, 8 October 2021 (UTC)

The script still recategorizes all pages, the previous script just recreated the actual category page (because moving categories was not possible on legacy) whereas this one actually moves it. You can just send a request through Zendesk to ask them about granting content mods on that wiki the right to move categories. -- Cube-shaped garbage can 08:49, 8 October 2021 (UTC)

Personal JS doesn't work

This doesn't work under the personal global js. But it works when I put it into a wiki itself. Is there a fix? MettytheCutiefly (talk) 23:47, 8 August 2023 (UTC)

Looking at the edit history of your global.js, it looks like you were missing the MediaWiki: part for that script. (compare your OasisRevived import to your MarkBlocked import for example) --Sophie ♦ 00:01, 9 August 2023 (UTC)

Cheat the Badges

Hello. When an administrator uses this script to rename pages, images and categories, does it count towards its edits of articles, pictures and categories to achieve the badges? If this function adds points to them, then I believe that this is unfair to other users and falls under the violation of abuse of authority.—Preceding unsigned comment added by ModestyElyonLane (talk • contribs) . Please sign your posts with ~~~~!

If they don't do it with a bot, which they probably should for popular pages, they most likely do count towards Achievements. However, that is none of this script's concern. You should probably talk it out with the administrator in question, or simply ignore it — after some time, these badges kind of become meaningless. -- Cube-shaped garbage can 14:38, 13 August 2023 (UTC)

Slight interface change request

Is it possible for the box that holds the new name in the renaming form to be made around 50 pixels wider? It's a bit too short and most times I have to go back and forth within the small box to make sure I got the new name right. It would be a lot easier if it could be made a bit bigger. ZioreRogue (talk) 22:18, 25 February 2025 (UTC)

Contents