Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#24389 closed defect (bug) (fixed)

WordPress.org removed /extend/, so we need to update URLs

Reported by: nacin's profile nacin Owned by: nacin's profile nacin
Milestone: 3.6 Priority: normal
Severity: normal Version:
Component: Text Changes Keywords: has-patch
Focuses: Cc:

Description

On Sunday night, I deployed a change to WordPress.org that finally removed /extend/ to plugin and theme URLs. So http://wordpress.org/extend/plugins/debug-bar/ is now just http://wordpress.org/plugins/debug-bar/. We have various URLs in trunk to update.

Attachments (2)

24389.diff (18.4 KB) - added by JustinSainton 11 years ago.
24389.2.diff (15.7 KB) - added by nacin 11 years ago.

Download all attachments as: .zip

Change History (9)

@JustinSainton
11 years ago

#1 @JustinSainton
11 years ago

  • Keywords has-patch added

Ignored .pot files, but left changes to bundled core theme style.css files.

#2 @JustinSainton
11 years ago

Also, you didn't mention it in the original post, but I assumed you removed Mobile from /extend/ as well - and that appears to be accurate.

@nacin
11 years ago

#3 @nacin
11 years ago

Yes, /extend/mobile/ also became /mobile/. In my patch, I also rearranged some strings so future changes to URLs don't alter the strings themselves. I am not sure but it looks like I found a few more (while you caught the ones in wp-content).

#4 @nacin
11 years ago

In 24320:

Remove /extend/ from URLs to wordpress.org/plugins, /themes, and /mobile, as those are all now top-level. see #24389.

#5 @nacin
11 years ago

  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from new to closed

In 24321:

Remove /extend/ from Theme URI headers in default themes. props JustinSainton, fixes #24389.

#6 @nacin
11 years ago

In 24322:

Remove /extend/ from Hello Dolly.

Well, hello, Dolly
It's so nice to have you back where you belong

fixes #24389.

#7 @SergeyBiryukov
11 years ago

In 24327:

Use numbered placeholders. see #24389.

Note: See TracTickets for help on using tickets.