WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#10258 closed feature request (wontfix)

Need for a "regenerate permalink" button

Reported by: xibe Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.8
Component: Administration Keywords: needs-patch
Focuses: Cc:

Description

As a follow-up to #10256, I'd like the core-devs to consider making an addition to the permalink edition section.

Currently, whenever I correct/update my post's title and want the permalink to reflect the update, I need to do the following:

  • double-click permalink OR click Edit button ;
  • delete content of textfield OR update text (a second time!) ;
  • click Save button.

I'd put my vote for a button (or link) on the left of the permalink's Edit button, named "regenerate permalink", that would make that whole process quicker.

Change History (8)

comment:1 follow-up: Denis-de-Bernardy5 years ago

Are you certain it gets saved and that this isn't merely a UI issue? Normally, as long as you don't explicitly edit and save a permalink, it'll remain blank until you publish.

For instance, if you take the title in your other ticket, and click save draft without bothering to edit the permalink, you should see the correct permalink when the page gets refreshed. Whereas, if you edit and save the permalink as you describe, you will need to change it -- because you had set it explicitly.

comment:2 hakre5 years ago

Permnalinks (for a post, better call that slug) - once set - need to be manually changed then afterwards. That change is independent from pressing the posts save changes button. Maybe that is the point: If the slug is once set and then changed, saving the post should save the (changed) slug as well.

comment:3 hakre5 years ago

  • Keywords 2nd-opininon removed

comment:4 in reply to: ↑ 1 ; follow-up: xibe5 years ago

Replying to Denis-de-Bernardy:

Are you certain it gets saved and that this isn't merely a UI issue?

Certain, nope. It might be a UI issue - which still needs fixin' :)

Normally, as long as you don't explicitly edit and save a permalink, it'll remain blank until you publish.

I guess you mean "blank in the database".

Replying to hakre:

Maybe that is the point: If the slug is once set and then changed, saving the post should save the (changed) slug as well.

Not sure about this: some people can prefer to have a full title and only have a couple keywords as a slug - or on the contrary, have the full title+a few more keywords as a slug, for SEO reasons. Hence, slugs should not be made to automatically match the titles.

Or maybe I misunderstood you :)

comment:5 in reply to: ↑ 4 hakre5 years ago

Replying to xibe:

Or maybe I misunderstood you :)

You misunderstood me. I was only talking technically and not about motivation.

comment:6 hakre5 years ago

  • Type changed from defect (bug) to feature request

Now I fully understand the reporters problem/Issue. This can not been easily done right away because there is no flag in the post-editor that takes care wether or not the title has been changed since the last time the post's slug has been generated.

Additionally there are some pitfalls: Changing a post's slug later on will leave links that were valid once result in a 404. If you correct a posts title fast or before publishing this is naturally not an issue but IMHO it is quite noteworthy.

As well it is noteworthy to say that automatic slug generation is (currently) latin-1 centric. Users with other charsets need to manually edit the slugs anyway, for example for german umlauts.

comment:7 scribu5 years ago

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

I think this is best resolved through a plugin. Reopen with a working patch for reconsideration.

comment:8 scribu5 years ago

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