[wp-meta] [Making WordPress.org] #31: WordPress.org global footer link changes

Making WordPress.org noreply at wordpress.org
Tue Aug 13 20:13:11 UTC 2013

#31: WordPress.org global footer link changes
  Reporter:  devinreams   |      Owner:  iandunn
      Type:  enhancement  |     Status:  assigned
  Priority:  normal       |  Component:  General
Resolution:               |   Keywords:  has-patch

Comment (by Otto42):


 - I see that your diff moves the standard alignment classes into wp4.css.
 Is this safe? The problem with the wp4.css is that it is used across the
 whole site, including the make blogs and everything else. The reason I
 only added those classes to the blog-wp4.css is that only the news site
 was missing them. I presumed that the make sites would have those already,
 since they're inheriting them from the P2 theme.

 - When developing, handling the static caching server is a PITA. So it's
 best to not use the s.wp and best to not update the number for
 cachebusting, because it causes increases when we have to deploy, since we
 have to stage the CSS first, then do the cachebust separately.

 - Any place we're referencing url(http://s.wordpress.org) for anything in
 a CSS file willalso need to be updated to use the "no-static" trick. If
 you examine header.php, you'll see that if the site is being accessed via
 https, it adds the "no-static" class to the html element. You can use this
 to refer to the correct URL and avoid the SSL problem. Examine the uses of
 .no-static in the wp4.css to see how this is done. This is part of the
 ssl-all-the-things initiative, to allow everything to work properly over

Ticket URL: <http://meta.trac.wordpress.org/ticket/31#comment:20>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software

More information about the wp-meta mailing list