Page MenuHomePhabricator

Maintenance script to check if revision user exists
Closed, DeclinedPublic

Description

Author: dasch

Description:
Some imported pages have very different styled historypages

  1. http://www.wecowi.de/history/Dresdner_Striezelmarkt (Not existing users link to User:Contributios)
  2. http://www.wecowi.de/history/Berliner_Verkehrsringe (Not existing users link to Userpage)
  1. http://www.wecowi.de/credits/Dresdner_Striezelmarkt (this one is full)
  2. http://www.wecowi.de/credits/Berliner_Verkehrsringe (this is nearly empty, although there are more contributors)

Both pages are imported from german wikipedia.

I have the impression that somewhere between 27. Nov and 8. Dez the behaviour of import has changed. I hope somebody can build a maintaince script to rebuild the history so that not existing users are checked and the links are set correctly and create a proper credits list.


Version: 1.16.x
Severity: enhancement

Details

Reference
bz22386

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:50 PM
bzimport set Reference to bz22386.

dasch wrote:

I checked my database and the rev_user key is 1 in the first example and 0 in the second.

The script just has to check if rev_user_text is available in user user_name and set rev_user to 0 if it's not

dasch wrote:

another case is, when a user from another wiki signs up in the wiki a page was imported to, the history is not changed, the links are still in old style, like in the time he was not signed up in the wiki
it would be really useful to have a script to fix this

dasch wrote:

I checked wikipedia and there old entries are correctly, so there was used a script to fix the history, so why isn't this script given to other users? I think this could even be fixed with a simple SQL-Statment

dasch wrote:

Does anyone think about this problem? It's really sad, that nobody cares about rhe strange effects in my history :(

dasch wrote:

Is really nobody able to do this? That's really anoing
Does nobody else ran into this problem?

dasch wrote:

Seems like I have to care about this myself :(

dasch wrote:

fixed with SQL Query