Reopen with community consensus for this change.

@Justarandomamerican Since this task will create a new protection level, some users might feel this is unnecessary, including me, so it would be good if community consensus is needed

Will do later today

fixed by running namespaceDupes.php

These appear to be pages that were created prior to TW being added as an alias for the Test Wiki namespace

This seems like a terrible idea: The suppressors have access to personally identifying information. No person who merely requested a right (without being appointed by the community or Stewards) should have access to such information.

@MacFan4000 please do it whenever you are free

Nice! Thank you!

I recreated the old account, which fixed it. It still showed the old username and main page title, but upon editing that was fixed. Lesson learned, is remove as publisher/subscriber before renaming the account.

if this also doesn't work I would request another rename request

Hmm.. try the following
UPDATE newsletter
SET author = 'TheAstorPastor'
WHERE author = 'Harvici';

It seems like it may be related to @Harvici being renamed on wiki. Not quite sure how to fix this Somehow it is pulling the old username from somewhere, and then failing when when attempting to query the DB with it.

Macfan assigned the new example account example rights.

Shouldn't his account be disabled, as a community banned user?

Per above comment.

It's OK now. This error isn't happening anymore.

Without it being reproducible, MacFan cannot fix it. Please detail what you did.

Hi, Username, I cannot reproduce this. Can you describe exact steps for the error to occur?

Done by pull request

As I have personally participated in the discussion linked, consensus needs to be determined by MacFan4000. Priority set to low as a controversial request with no clear consensus.

Reopen if issue still happens.

Is this still happening?

fixed

same with creating subpages

same thing has happened even after trying to use different names and ways to create.

There is community consensus for this action at the community portal, so boldly updating to high.