WordPress.org

Ready to get started?Download WordPress

Make WordPress Systems

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Konstantin Obenland 12:09 am on February 24, 2015 Permalink |  

    We’re launching the new theme directory this week, and it comes with some URLs redirects.

    Most importantly, wordpress.org/themes/ will be served from the WordPres.org MU going forward, so themes will be just a site on that network.

    Trailingslash all request without a query,
/themes => /themes/
/themes/tag-filters/ => /themes/
/themes/search.php?q=[term] => /themes/search/[term]/
/themes/[themename]/stats/ => /themes/[themename]/
/themes/[themename]/developer/ => /themes/[themename]/
/themes/about/ => /themes/getting-started/
/themes/contact/ => /themes/getting-started/

    We don’t have a specific date/time for the switch yet, but it will be on 2/25 or 2/26.
    Posting here to give you a heads up and some time to get it prepared.

    /cc @seanosh, @otto42

     

    • Dion Hulse 12:42 am on February 24, 2015 Permalink | Log in to Reply

      FWIW, there’s a bunch more URL changes than just these that apply to themes.

      • The links in the sidebar under Themes, /themes/mine/ /themes/about/ /themes/contact/ (I guess these are pages you haven’t yet created?)
      • Tags – /themes/tags/custom-background
      • RSS Feeds – /themes/rss/(forum|tags|view|browse)/*
      • /themes/browse/(popular|new|updated)

      • Konstantin Obenland 4:49 pm on February 24, 2015 Permalink | Log in to Reply

        • Mine is going to be /author/[login]/ going forward, so not something we could recreate, I imagine. I wasn’t sure whether letting 404 would have merit here.
        • About and Contact are now part of Upload. The reason I haven’t mentioned it yet is that the WPTRT has not made up their mind yet about what the upload experience should look like, so I wanted to hold off on that one until we know.
        • Yes, tags need to be tag, I updated the post, thanks.
        • In terms of RSS, let me try it on the WP level first.
        • Browsing URLs are going to continue to live on.

  • Andrew Nacin 1:11 am on February 19, 2015 Permalink |
    Tags: deploy wporg-web   

    Can I please have the wporg-web role updated after r5929 and r5930? It pipes deploys to Slack. Pretty clever IMO, in terms of how it detects what revision is getting deployed. This only affects sandboxes (the deploy script itself).

     

  • Andrew Nacin 6:58 pm on February 17, 2015 Permalink |
    Tags:   

    Requesting a sandbox for Kelly Dwan (@ryelle). She should have a public key at Automattic (where she is @ryelle33) to use. I’ll handle SVN access — just needs the sandbox. Thanks!

     

    • seanosh 2:48 pm on February 18, 2015 Permalink | Log in to Reply

      All set, here are the details of the sandbox:

      User Name : wporgdev
Host Name : ryelle33.dev.wordpress.org
IP Address: 66.155.40.190

  • Konstantin Kovshenin 4:17 pm on February 16, 2015 Permalink |
    Tags:   

    Hi! Can we please remove the following server blocks from wordcamp-web.conf?

    server {
    listen 80;
    server_name 2006.wordcamp.org 2006.sf.wordcamp.org;
    ...
}

server {
    listen 80;
    server_name 2007.wordcamp.org 2007.sf.wordcamp.org;
    ...
}

    Thanks!

     

    • Konstantin Kovshenin 4:21 pm on February 16, 2015 Permalink | Log in to Reply

      Also this block from wordcamp-redirects:

      server {
    listen 80;
    server_name wordcampsf.org wordcampsf.com *.wordcampsf.org *.wordcampsf.com;
    ...
}

      Thank you!

    • Andrew Nacin 1:13 am on February 19, 2015 Permalink | Log in to Reply

      I presume these sites will all still work after these rules are removed, just some other way?

      For the non-wordcamp.org domains, I presume the idea will be to handle the redirect elsewhere as they don’t have SSL certificates?

      • Konstantin Kovshenin 8:31 am on February 19, 2015 Permalink | Log in to Reply

        Correct, we’ve migrated the legacy code into themes that are now running inside the main WordCamp.org network as opposed to secondary WordPress installs in a different root. This allows us to retire the secondary installs and proceed with the URL format change for WordCamp SF sites, which are the only ones left right now.

        Re. SSL, actually I’m not sure yet. I thought about forcing SSL on WordCamp.org via nginx, but that would break year.city.wordcamp.org subdomains which will not be covered by the wildcard certificate, so I thought of handling it with PHP instead, where we already handle year.city.wordcamp.org redirects to city.wordcamp.org/year, so I think additional domains can just follow the same pattern.

  • Konstantin Kovshenin 4:34 pm on February 11, 2015 Permalink |
    Tags:   

    Hi! Can we please remove the following redirects from WordCamp.org’s nginx config?

    server {
        listen 80;
        server_name newyork.wordcamp.org;

        rewrite ^(.*)$ http://2009.newyork.wordcamp.org$1 permanent;
}

server {
        listen 80;
        server_name utah.wordcamp.org;

#       rewrite ^(.*)$ http://2010.utah.wordcamp.org$1 permanent;
        rewrite ^(.*)$ http://2011.slc.wordcamp.org$1 permanent;
}

    Thanks!

     

  • Ian Dunn 11:05 pm on February 5, 2015 Permalink |
    Tags: , zip   

    ZipArchive on WordCamp.org 

    Could we please have ZipArchive installed on WordCamp.org?

    It’s needed for #262-meta, where we want to automate the generation of Gravatar badges for WordCamps.

     

  • Andrew Nacin 10:19 pm on January 22, 2015 Permalink |
    Tags:   

    I have an nginx fix for a fun issue that’s breaking Jetpack integration.

    https://make.wordpress.org/support/xmlrpc.php isn’t being rewritten to /xmlrpc.php because /support/xmlrpc.php exists (it’s a bbPress file). /support/ is a physical directory that is bypassed for all subdomains, which means we end up rewriting it to index.php and thus a 404 results.

    The simple fix appears to be this:

    
	# make.wordpress.org/support/xmlrpc.php needs to hit /xmlrpc.php.
	# Without this, it targets /support/xmlrpc.php (a bbPress file)
	# which is then denied and we end up with a 404.
	location ~ /xmlrpc\.php(?:/|$) {
		include conf.d/php-config;
		rewrite ^ /xmlrpc.php break;
	}

    This should go into conf.d/wporg-make.wordpress.org around line 60. I’m happy to commit this but I wanted review first.

     

    • seanosh 1:58 am on February 5, 2015 Permalink | Log in to Reply

      I’m OK with this (barring any other objections). Let me know if you need help rolling it out.

    • Andrew Nacin 5:53 am on February 5, 2015 Permalink | Log in to Reply

      I’m not positive the include conf.d/php-config.php + rewrite is correct, whether anything is missing, etc. It works and I can’t find side effects, but this is a bit out of my area of expertise.

    • Barry 7:39 pm on February 11, 2015 Permalink | Log in to Reply

      Maybe @pyhhak can take a look at this.

    • pyhhak 9:59 pm on February 11, 2015 Permalink | Log in to Reply

      You don’t need the php-config, just need to use normal rewrite (without break). Also your regex location would rewrite /whatever/xmlrpc.php to /xmlrpc.php, which is useless and more of a pain to maintain in future.

      If you only need /support/xmlrpc.php my suggestion is this:

      location = /support/xmlrpc.php {
	rewrite ^ /xmlrpc.php;
}

      I sort of tested it, and it seemed to work. Can you run your tests and commit it?

  • Andrew Nacin 3:43 am on January 22, 2015 Permalink |
    Tags:   

    Can johnbillion please be given a sandbox? I can set up commit access and such.

     

  • Konstantin Kovshenin 9:07 am on January 16, 2015 Permalink |
    Tags:   

    Hi! Can we please remove the following redirect from the conf.d/wordcamp-redirect nginx config?

    server {
        listen 80;
        server_name raleigh.wordcamp.org;

        rewrite ^(.*)$ http://wordcampraleigh.com$1 permanent;
}

    Thanks!

     

  • Dion Hulse 3:00 am on January 12, 2015 Permalink |  

    Can I please have wporg-web role updated for these changes please?

    Future iterations will retire some older stats crons.

     

    • Barry 3:09 am on January 12, 2015 Permalink | Log in to Reply

      • The comment in the script called by r5797 is incorrect. Could you please update it for clarity?
      • For redirects you shouldn’t use rewrite but instead return It’s faster and cleaner. Also, I am not sure why we are returning 302, seems like it should be 301. At least you didn’t use if :)

        • See r5763 for an example.

      • Dion Hulse 3:19 am on January 12, 2015 Permalink | Log in to Reply

        updated the comment in r9417-dotorg

        For redirects you shouldn’t use rewrite but instead return It’s faster and cleaner.

        Ah, right. I followed the same examples which were already in there (rewrite for where $request_uri is wanting to be kept, and return for static redirects).
        I see I could’ve used return 301 https://wordpress.org$request_uri; instead, would you like me to update it?

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel