Closed
Bug 686498
Opened 13 years ago
Closed 13 years ago
Update font URL in blog.mozilla.com wordpress theme
Categories
(Websites :: other.mozilla.org, defect)
Websites
other.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sgarrity, Assigned: nmaul)
Details
The theme for blog.mozilla.com is calling the Meta web font from .com rather than .org. This is breaking the font in some browsers. This also affects the theme for the Mozilla Privacy Blog as that theme inherits from the main mozilla blog theme. Fix coming...
Reporter | ||
Comment 1•13 years ago
|
||
Ok, this is fixed in trunk in r94996. This change needs to be push into production.
Assignee | ||
Comment 2•13 years ago
|
||
Completed. This will take a few minutes to be live in production. [root@mradm02 themes]# svn up U MozillaBlog-Nova/style.css Updated to revision 94996. Note that there are plenty of other themes still affected. Here's a list of files that are still affected, and how many times they contain the reference: 1 MobileBlog-Nova/css/editor-style.css 1 MobileBlog-Nova/style.css 1 MozillaBlog-Nova/css/editor-style.css 1 Releases-Nova/css/editor-style.css 1 Releases-Nova/style.css 1 Thunderbird-Nova/style.css 3 UserResearch-Nova/style.css
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to Jake Maul [:jakem] from comment #2) > Note that there are plenty of other themes still affected. Thanks Jake, I didn't realize that. The rest of these are updated in trunk in r94997. Can you do that push as well?
Assignee | ||
Comment 4•13 years ago
|
||
Excellent. Done. [root@mradm02 themes]# svn up U MobileBlog-Nova/style.css U MobileBlog-Nova/css/editor-style.css U UserResearch-Nova/style.css U Releases-Nova/style.css U Releases-Nova/css/editor-style.css U Thunderbird-Nova/style.css U MozillaBlog-Nova/css/editor-style.css Updated to revision 94997. I don't see any more instances of this, so I think we should be good now... at least for blog.mozilla.com. :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•