Significant known issues under investigation on Fandom wikis:
-
Achievements are incorrectly showing unparsed HTML, such as
<strong>and<br/>tags.
- Achievement leaderboard positions incorrectly don't go below position #50.
- We are aware that some wikis are not working properly for users on Russian and Chinese internet connections.
- This is partly due Russian internet authorities blocking the Cloudflare platform, and Chinese authorities may also be blocking some connections.
- We are investigating solutions, but this may not be something we can easily solve.
- Accounts with confirmed emails may see a message incorrectly stating the account email still needs to be confirmed.
- This error should go away after a few days, as the real issue is the young age of the account.
- We are working on updates to the error messages to reduce confusion!
- Non-English wikis may show a generic Fandom favicon on Google search results.
- This is due to Google ignoring language paths when looking for favicons. Unfortunately, this is outside our control.
- We are serving the correct favicon, which you can see in your browser when viewing the wiki.
- Not a bug: changing user rights via Special:UserRights now requires login re-authentication.
Editor issues
- The VisualEditor may lose image size data during some edits.
- We suggest temporarily using source mode if you are being affected by this problem.
- The VisualEditor might show a "Revision IDs returned by the server do not match" error.
- Pressing CTRL+F5 or clearing your browser cache should fix this. If not, making a small edit in source mode may help.
- Editing some very long pages using the VisualEditor may trigger a "No stashed content" error.
- We suggest using source mode on affected pages, while we continue to investigate this issue.
- Setting the "Edit area font style" preference to a non-default value may cause the editor text to become misaligned.
- We recommend setting it to the default choice ("Browser default").