User blog:DaNASCAT/Technical Update: June 12, 2017

Here are the latest technical updates on Fandom. Keep in mind that our system updates happen every Tuesday and Thursday - today's notes are for tomorrow's site update. Also note that we change hundreds of tiny details every week, so these are just the highlights.

New Features
The new page and article header design will be released! While many wikis won't need to make changes, as with any big release there are some important notes to be aware of:


 * Feature updates:
 * Admins will be able to set a custom color for the new page header that is separate from the button and link colors.
 * If a wordmark is narrower than 250px, the wiki name and local nav will slide over accordingly.
 * Community CSS and JS is no longer allowed to affect the page header area - but you are free to add such CSS and JS as personal code. Look out for an update to Help:Customization policy tomorrow!


 * Known issues:
 * Communities with custom CSS and JS may see broken elements in the navigation if they have, for example, a transparent background. Please feel reach out to the Community team for help or disable that custom CSS or JS to solve that problem if needed.
 * Some keyboard shortcuts will be temporarily unavailable.
 * Some wikis may see older community names displayed - this is because the previous name was still defined in ThemeDesigner, having previously been replaced by a wordmark. This text can be updated via ThemeDesigner - see "Community name" on the "Wordmark" tab!

Major Bug Fixes

 * When data is unexpectedly unavailable, WAM will no longer show a blank page.
 * We recently fixed an issue that was causing some newer wikis to not be listed in WAM rankings.

Other Notable Changes
Recent mobile app updates are listed on Apps Technical Updates, and detailed site CSS-related updates can be found at http://report.wikia.net
 * Some Chat messages will be added to the whitelist -,  ,  ,  ,.

Select Known Issues

 * Chat will be restarted in the hours after the code release, to push live some recent backend updates to that feature.
 * Our CDN provider had some technical problems in a few regions over the weekend that caused longer than normal latency while traffic was directed to alternate locations. Currently, the US East Coast is still experiencing these issues. This should be resolved shortly.

Questions? Comments? Feel free to leave them below. And if you have additional bugs to report, please send them to us via Special:Contact.