WordPress.org

Make WordPress Core

Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#2001 closed defect (bug) (wontfix)

Permalink options page lacks syntax or formatting instructions

Reported by: h3h Owned by:
Milestone: Priority: normal
Severity: major Version: 2.0
Component: Administration Keywords: has-patch 2nd-opinion
Focuses: Cc:

Description

The Customize Permalinks page has 4 options. The "Default" setting leaves the "Custom structure" box blank, but the box stays blank if one chooses the "Custom" radio button.

There are no syntactical or formatting instructions anywhere on the page as there are in WP 1.5.

The user has no easy way (opening the Codex in a new window and looking up variables is *not* easy) of knowing that the "Custom structure" box should contain something like "/%postname%/" unless he/she incidentally clicks on one of the other radio buttons, and then it's only by a means of reasoning.

This needs to be spelled out as it is in 1.5, giving an example of a "Custom structure format" directly above or below the box itself, making clear that one should start with "/..." and not "http://mysite.com/..." as well as the most common variables (%year%, %monthnum%, %day, %postname%, etc.).

I'll create a patch if no one else is willing.

Attachments (3)

options-permalink.php.diff (1.2 KB) - added by thechris 16 years ago.
options-permalink.php.2.diff (2.3 KB) - added by thechris 16 years ago.
Updated patch
2001.diff (2.4 KB) - added by robmiller 16 years ago.

Download all attachments as: .zip

Change History (14)

#1 @h3h
16 years ago

  • Milestone set to 2.0

#2 @technosailor
16 years ago

If you're volunteering, write the patch. :-)

#3 @thechris
16 years ago

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

This is my first patch, I think this is what is asked for. Adds the following instruction above the 'Custom Structure' box:

Custom structure has to begin with /, some common variables are %year%, %monthnum%, %day, %postname%

#4 @h3h
16 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

That's a good start, but not newbie friendly enough IMO.

Don't close tickets until the patches have been checked in. Usually the person checking the code in will close the ticket.

@thechris
16 years ago

Updated patch

#5 @thechris
16 years ago

Thats my second attempt, I think its more newbie friendly - its definently more detailed than before. Its difficult to decide exactly how much information to give, but as a relatively new user of Wordpress thats the kind of information I would have appreciated.

Sorry about closing it, that was my bad.

#6 @matt
16 years ago

  • Milestone changed from 2.0 to 2.1
  • Priority changed from high to normal

@robmiller
16 years ago

#7 @robmiller
16 years ago

  • Keywords has-patch 2nd-opinion added

Tried to make it more user-friendly, added internationalisation support and hid the message unless a custom permalink structure was selected. I'd appreciate a second opinion, though.

#8 @davidhouse
16 years ago

-1. If the user wants to play with their own custom structures, then requiring looking at the Codex is reasonable. Also, having the information just in the codex means we can update it quickly when things change.

#9 @Nazgul
15 years ago

-1 as well. Same reason as dividhouse, and if we start doing this here, we'll have to do it everywhere. (Date and Time formats for instance)

#10 @matt
15 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

#11 @Nazgul
15 years ago

  • Milestone 2.1 deleted
Note: See TracTickets for help on using tickets.