Page MenuHomePhabricator

Anticipate and prevent publishing issues due to abuse filters
Closed, DuplicatePublic

Description

When users try to publish a translation sometimes the abuse filter is triggered because of an external link from the source article was transferred to the translation (example report). The issue is hard to spot for the user since the problematic content was not created explicitly.

Currently, we are showing an error when the user tries to publish (with a cryptic debug message). We can consider better approaches for (a) communicating the issue and (b) nor preventing publishing content.

For example, we can highlight the problematic content (e.g., the external link) for the user to fix. If the issues is not fixed when the user tries to publish, a warning informs the user that the content will be published without the problematic elements. In this way, most of the translation can be published instead of getting blocked because a small piece of content.

Event Timeline

Pginer-WMF raised the priority of this task from to Needs Triage.
Pginer-WMF updated the task description. (Show Details)
Pginer-WMF added a project: ContentTranslation.
Pginer-WMF subscribed.
Pginer-WMF renamed this task from Prevent or anticipate publishing issues due to abuse filters to Anticipate and prevent publishing issues due to abuse filters.Oct 21 2015, 7:56 AM
Pginer-WMF added a project: Design.
Pginer-WMF set Security to None.