Describe the bug
When capturing 404 errors, it doesn't capture the language slugs created by TranslatePress plugin, although still captures the language slugs that are not defined in TranslatePress.
For example:
- TranslatePress defines two languages: Vietnamese (
/ ), and English ( /en/ ).
- 404 Monitor doesn't capture 404s that has
/en/ slug.
- 404 Monitor does capture 404s that has other slugs, like
/ja/.
There was a similar issue that reported to be fixed. But at this time, I confirm this issue is still going on.
To Reproduce
Steps to reproduce the behavior:
- Go to a non-existing URL, like
example.com/en/article-one → It will return 404.
- The 404 Monitor captures that 404 as:
/article-one (lacking the /en/ part).
- Go to another non-existing URL, like
example.com/ja/article-one → It will return 404.
- The 404 Monitor fully captures the 404 as:
/ja/article-one.
Expected behavior
404 Monitor should captures all languages created by the TranslatePress plugin.
Screenshots
