Page MenuHomePhabricator

Some Phonos exceptions do not add the page to the tracking category
Closed, DeclinedPublicBUG REPORT

Description

What is the problem?

As per T316700, when a Phonos template has an exception it should add the page to the tracking category "Pages with Phonos rendering errors".

This does not happen in the cases when either $wgPhonosCommonsMediaUrl or $wgPhonosPath are invalid.

Steps to reproduce problem
  1. In LocalSettings.php, add $wgPhonosCommonsMediaUrl = "http://localhost"; OR $wgPhonosPath = '/tmp/directory-with-no-write-permissions'; (test them both individually)
  2. Add a new Phonos template to a page and publish/save the page

Expected behavior: The page should have the category "Pages with Phonos rendering errors" (categories are listed in the article just below the content)
Observed behavior: The page is not added to that category.

Event Timeline

This only can happen due to sysadmin misconfiguration (generally not a concern), but it is still fixable if we want to fix it. The categorization doesn't make a whole lot of sense though because every usage of Phonos is effected by the misconfiguration, not just the page you're viewing. The category I think is intended more for editors, not sysadmins (though there are probably other things sysamdins can do incorrectly that cause the pages to be categorized). Say the engine failed for whatever reason, the fix is usually to simply re-parse (i.e. purge the page); the categorization will signal editors attention to those pages and they can fix them themselves. MediaWiki misconfigurations however are not fixable by editors.