Issue: URL Replacements fail Exist Checks

When article names are tested against the article list, the parameter is sometimes already encoded (like the URL request, or a lazy user using the BB-Code). However this causes double-encoding problems with URL replacements if a find string also exists in the encoded string. The only way to correct the underlying issue entirely is to make $vault->article->fetch test both the encoded and unencoded versions, assuming the unencoded version if both exist.