Done (using P365).

@Southparkfan status?

I was deploying the ALTERs to the wikis while RottenLinks was disabled (the ALTERs cannot be done live using pt-osc, unfortunately), but I forgot to re-enable RottenLinks. For now, I have enabled RottenLinks. The extension only needs to be disabled again (and the update scripts killed) if you are deploying the schema changes on databases.

In T6095#123471, @Southparkfan wrote:

@John it doesn't look like larger VARCHARs are possible. Even if you don't use the rl_id field, it does seem to be working fine at first glance, without fundamentally changing the schema (the current, old fields can stay). What do you think?

@John it doesn't look like larger VARCHARs are possible. Even if you don't use the rl_id field, it does seem to be working fine at first glance, without fundamentally changing the schema (the current, old fields can stay). What do you think?

While the change was committed, the change has not been applied to existing tables.

WikiLirik sözcüleri eleştirisel pozitif-negatif düşünce karşılaştırma
PyschoLyricWiki Attack Groups
Ben ötesi psikoloji

Thank you for the contribution and spotting issues that escaped testing for this particular extension!

The third point is linked to T5295.

RottenLinks is more of a maintenance-based tools. The current section therefore is appropriate.

Sorry for the bad classification.

The name “RottenLinks” is a noun and as such would not have another translatable alternatives.

The extension is built on standard MediaWiki code - the support for —wiki is through standard MediaWiki (as proven above).

I fully understand what you explain about the PHP magic constant __DIR__ - but shouldn't your script then at least support the given --wiki database name and use it? In all my tests, it does not.

You say;

Thank you for documenting your approach. Here is mine - using the unpatched script updateExternalLinks.php:

Can you please tell me HOW you tested it? As I already explained, my installations are like this:

OK!, but
$ w3m -dump https://abj.miraheze.org/wiki/Special:RottenLinks?stats=1

Status of external links

wfGetDB( DB_MASTER ) opens a database connection from the wiki where the script is being ran (namely the --wiki option, or whatever the value of $wgDBname is).

Hi John,
as I wrote in my initial message, the original PHP script does not recognize when run from e.g. /MYPATH/wiki/en/extensions/ - it then also checks all URLs in the IntactiWiki pool's database named intactiwiki, but not in the English Intactiwiki database, which is named intactiwiki_en. My patch fixes this for me.

This is found under statistics.

The script is fairly bandwidth intensive. It’s not reasonable to allow any user on a wiki to run it on demand - it would be a decision of the system administrators running the extension when to run it.

I am not saying "please update it for my wiki".
I am saying "please give users a way to update it without needing a Steward's help."