Page MenuHomePhabricator

Wikis stay subscribed to items after sitelinks are removed
Open, Needs TriagePublic

Description

I have noticed that wikis are listed as being subscribed to items even after the sitelinks have been removed and the wiki is not making any other use of the item.

Example: https://www.wikidata.org/w/index.php?title=Q22941194&action=info (which will probably get deleted soon) lists svwiki and cebwiki as subscribers, even though both sitelinks were removed. The svwiki page was edited to be about another item and then the sitelink was removed from Wikidata. I turned the cebwiki page into a redirect and then remove the sitelink from Wikidata.

Another example: For https://www.wikidata.org/w/index.php?title=Q22950526&action=info, I also edited the cebwiki page to turn it into a redirect and then removed the sitelink from Wikidata and it still lists cebwiki as being subscribed.

It seems that in other situations, the subscriptions are being removed:

Event Timeline

It does look like this is the case:

mysql:research@analytics-store.eqiad.wmnet [svwiki]> select * from wbc_entity_usage where eu_entity_id = 'Q22941194';
Empty set (0.00 sec)
mysql:research@analytics-store.eqiad.wmnet [wikidatawiki]> select * from wb_changes_subscription where cs_entity_id = 'Q22941194'
    -> ;
+-----------+--------------+------------------+
| cs_row_id | cs_entity_id | cs_subscriber_id |
+-----------+--------------+------------------+
|  95636079 | Q22941194    | cebwiki          |
|  94606404 | Q22941194    | svwiki           |
+-----------+--------------+------------------+
2 rows in set (0.02 sec)

So what is being displayed on the info page actually seems to be incorrect / old.
This could also affect dispatching? not sure off the top of my head if wb_changes_subscription plays into that.

I also tried removing the sitelink before turning the page into a redirect for https://www.wikidata.org/w/index.php?title=Q49126841&action=info and that still lists cebwiki as subscribed too.

This could also affect dispatching? not sure off the top of my head if wb_changes_subscription plays into that.

This will affect dispatching