Showing 1-2 of 2 unresolved posts
2
Can I please have the following SQL commands run against the Codex Mediawiki database?
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporgmake', 'http://make.wordpress.org/$1', 1, 0);
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporglearn', 'http://learn.wordpress.org/$1', 1, 0);
This is designed to allow us to create external links and redirects to handbooks, which (will) live in WordPress on make.wordpress.org and learn.wordpress.org.
Hey, I am trying to login to the Unit Tests Trac, so that I can reply to a ticket there, but /login redirects to https://core.trac.wordpress.org/log/tests.
Was this by design? I would prefer to reply to active tickets there until we migrate the conversations to the core trac.
The merge of unit tests to core was on purpose. @nacin can give more info about it 
Thanks, @stankea.
Hm, judging from this comment it sounds like we still should be able to login/comment on tickets.
@nacin, am I reading this right?
Yes.
There was a bug in config – /login wasn’t expected to be redirected. Fixed it now.
But anything regarding how the tickets should be handled – in which trac – should be answered by @nacin
If i go to unit-tests.trac.wordpress.org/login directly, I get the login prompt, but if I just go to unit-tests.trac.wordpress.org and click the Login link, it doesn’t display the prompt and just refreshes the current page.
We’re merging design.trac and unit-tests.trac into core.trac (but keeping separate SVN repos), taking advantage of Trac 0.12′s multi-repository support.
Everything is set up on Trac’s end, I just need two commands run:
trac-admin $ENV repository resync "tests" trac-admin $ENV repository resync "design"
… where $ENV would be the path to trac-environs/wp-core.
I then need two post-commit hooks, one on the unit-tests.svn repo, and the other on design.svn, both pointing to the wp-core environment:
trac-admin $ENV changeset added "design" $REV trac-admin $ENV changeset added "tests" $REV
design.trac (which has no tickets, etc.) can be killed off with this. unit-tests.trac should remain operational, as it has existing tickets. I’ll make it read-only like what we did with WordPress MU’s Trac once this is done.
I don’t *think* anything needs to change with core.svn’s post-commit hook.
Also, I am pretty sure that “design” and “tests” for the post-commit hooks can likely be their full SVN paths instead, so the same as core.svn’s post-commit hook.
I can set up svnnotify after.
Done by @stankea! Including svn notify for both. (Design is now also piped to wp-svn, like tests.)
Awesome.
Hey @barry and @stankea. Can you set up an email address (not a box, just an alias) of meetups@wordpress.org and have it forward to me at jane@automattic.com? At some point we’ll probably want to set up a supportpress instance or something, but for now I just need an active address to satisfy the meetup.com contract. Thanks.
Done.
Many thanks!
Last night I updated bbPress.org’s pinned bbPress external to trunk, and now none of bbPress’s custom rewrite rules are working.
Back during the initial 1.1 to 2.x conversion, @stankea had to do some rule tweaks in nginx. Does this need to be updated too, or is this an issue on my end?
Appears to have just silently fixed itself.
Only broken rule now is: http://bbpress.org/forums/users/johnjamesjacoby/topics/
Ends up redirecting to a topic in the forums. Looks like the specific topic is not the root cause; I changed the post_status of it, and it still redirected to a different topic.
Looking.
Definetly not nginx rewrites as they aren’t there anymore. Probably something in WP itself – maybe cache?
Talked with @nacin via Skype. Came to the conclusion that rewrites being broken was a cache issue. We think the one remaining broken rewrite rule (for user topics) is a query string conflict in bbPress trunk using ‘topics’ as a chunk (though ‘replies’ works fine.)
Was traveling to Vancouver all day yesterday with no on-plane WIFI, so will look at this today.
My fork: https://github.com/nacin/TracDuplicates. Tarball: https://github.com/nacin/TracDuplicates/tarball/master. easy_install handles this, as previously.
Deploy rev 3813 includes the trac.ini changes necessary for this and needs a deploy.
Rev 3814 is additionally required to make this work.
All done
seems like @stankea is incharge here, but stankea i couldn’t find any other online presence of yours! thanks! could you guys list the systems you are running code of course, nginx, trac, wp, irc-server? jabber? what else?
Can I get a deploy on deploy svn r3809? It’s a bunch of templating updates to the core Trac environment.
Also revision 3811.
Thanks, @stankea. Marking as resolved.
Post highlighting the changes: http://make.wordpress.org/core/2012/09/10/trac-updates-and-design-refresh/
The $host = make.wordpress.org conditional also needs some lines from the location / block, prior to the rewrite for index.php pulled from @404-extend in http://make.wordpress.org/systems/2012/07/17/problem-with-nginx-rewrites-i-think-conflict-between/#comment-247.
Specifically:
stankea, and 1 other are discussing. 
hummvee,
# uploaded files
rewrite ^/([_0-9a-zA-Z-]+/)?files/(.+) /wp-includes/ms-files.php?file=$2 last;
rewrite ^/core/handbook/files/(.+) /wp-includes/ms-files.php?file=$1 last;
# add a trailing slash to /wp-admin
rewrite ^/([_0-9a-zA-Z-]+/)?wp-admin$ /$1wp-admin/ permanent;
rewrite ^/core/handbook/wp-admin$ /core/handbook/wp-admin/ permanent;
I suggest the various /core/handbook/ rules be pulled out into their own location block once make.wordpress.org moves to its own server block.
Moved out make.wordpress.org to a seperate file and added in the rules.
I think you broke something make/support redirects to the forums, and apparently no one can log in to the forums. Minor ish.
Can’t replicate either of these things. Are you still having trouble?
Not sure about the logging in part, but the redirect was fixed by @stankea. This change included a fix for this.
By the time my comment was approved, this was fixed.
Problem with nginx rewrites, I think. Conflict between the new make.wp.org/support and the support forums.
http://make.wordpress.org/support/2012/07/hello-world/
Incorrectly redirects to:
http://wordpress.org/support/2012/07/hello-world/
The make site is currently set to default permalinks to work around this for now. Can the nginx rules be modified to handle this case?
Inside the $host = make.wordpress.org conditional, it should end with rewrite ^. /index.php last;, which is what ends the @404-extend block. This will prevent rewrites designed for ^wordpress.org from causing problems elsewhere.
learn.*, make.* and future subdomains should probably end up in their own stripped down wporg-wp.wordpress.org config file, as the relevant subdomains here run a mostly stock WP network, but I’ll leave that to @barry and @stankea.
We are starting a new code sprint today to re-do our existing unit-tests framework. In order for this to be successful we need to raise the visibility of the unit tests commits, which we’d like to do by pushing them over the same wire as core commits.
1. Can I get a deploy on deploy repo revision 3744, which switches Trac notification emails from wp-unit-tests@lists.wordpress.org to wp-trac@lists.automattic.com?
2. Can svn notify commit emails for unit-tests.svn.wordpress.org be re-routed from wp-unit-tests@lists.wordpress.org to wp-svn@lists.automattic.com? (There is no need to continue to send to both lists.) Can the -P subject prefix argument for svn notify please be set to -P [Tests]?
Revision 3747 adds tracrpc.* = enabled to trac.ini, to enable XML-RPC. This is already done for core trac.
@nacin, I think it would be a good idea to send it to both lists. I’m sure there are people, who’d like to follow the unit-tests list differently than the core one.
Probably few people, but you are right. I’ve been thinking about this all weekend. Merging them is good, but not also sending things to wp-unit-tests could scare away some people who don’t want the full firehose but might be really excited about unit tests.
Perhaps systems has an idea for how to implement this.
I’ve did the first part of the request and the -P [Tests]
I’m not sure what to suggest for the notify. I would prefer to have different list for each so that i can control the flow of emails, but i am not sure what is the best for the developers.
The rest of this has been sorted out:
If you are subscribed to all three lists, you won’t get duplicate threads (assuming your mail client isn’t stupid).
Thanks, @stankea.
Andrew Nacin 9:23 pm on January 31, 2013 Permalink | Log in to Reply
Implemented by @stankea. Confirmed as working: http://codex.wordpress.org/Automated_Testing?redirect=no.