WordPress.org

Make WordPress Core

Opened 4 years ago

Last modified 3 years ago

#24675 new enhancement

Reduce the number of clicks needed to update the permalink to match a changed title to just one click.

Reported by: pbearne Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.6
Component: Editor Keywords: needs-patch
Focuses: javascript, administration Cc:

Description

This a very simple patch but is solves a real annoyance. If you change you title the permalink becomes stale and to update you have the follow clicks

click edit
click in the input change or Ctl+a and delete content
click save

this is a pain

this patch adds a re-sync button which does all of the above.

I thought about having a check box / page option to lock the the title and the permalink to together until published syncing on blur but this would need more user testing so kept it simple and wanted to see if I could get this blessed first.

Attachments (2)

re-synic.patch (2.5 KB) - added by pbearne 4 years ago.
patch to add resyinc button
re-sync.png (17.6 KB) - added by pbearne 4 years ago.
Screenshot of new button

Download all attachments as: .zip

Change History (16)

@pbearne
4 years ago

patch to add resyinc button

@pbearne
4 years ago

Screenshot of new button

#1 follow-up: @pbearne
4 years ago

I have been thinking about if this button can just stay here or if we need to remove it after post/page published.

I can't see a reason to remove it yet

#2 @lchski
4 years ago

  • Cc lucas@… added

#3 @pbearne
4 years ago

I just copied the js/ajax in the patch but it could moved to a shared function with existing js/ajax function if this goes forward

#4 @sunnyratilal
4 years ago

  • Cc sunny@… added

+1

#5 follow-up: @mark-k
4 years ago

+1 to the idea

two comments

  1. I think "Re-Sync" is a bad name as it doesn't imply what is synched to what. Maybe "Use current title" is better but probably too long....
  1. There is a slug metabox for the JS challenged people ;) which you can show/hide with the screen options. It will be nice to have this functionality there as well, maybe by using a checkbox.

#6 in reply to: ↑ 1 ; follow-up: @SergeyBiryukov
4 years ago

Replying to pbearne:

I have been thinking about if this button can just stay here or if we need to remove it after post/page published.

For drafts, the slug is automatically synchronized on save. If the button is removed for published posts, then I'm not sure what's the use of it at all.

#7 in reply to: ↑ 6 ; follow-up: @pbearne
4 years ago

Replying to SergeyBiryukov:

Replying to pbearne:

I have been thinking about if this button can just stay here or if we need to remove it after post/page published.

For drafts, the slug is automatically synchronized on save. If the button is removed for published posts, then I'm not sure what's the use of it at all.

That not clear that is happening so much so I going to test it. Then I would propose that we add a graphic to so this is clear.
We can you the same graphic used to lock height and width together when scaling (line with locked 8 and broken 8 for unlinked)

#8 in reply to: ↑ 7 @pbearne
4 years ago

Replying to pbearne:

Replying to SergeyBiryukov:

Replying to pbearne:

I have been thinking about if this button can just stay here or if we need to remove it after post/page published.

For drafts, the slug is automatically synchronized on save. If the button is removed for published posts, then I'm not sure what's the use of it at all.

Thank you SergeyBiryukov I didn't know that.
That you are the first to point this out make the point that is not clear that is happening. Then I would propose that we add a graphic to so this is clear.
We can you the same graphic used to lock height and width together when scaling (line with locked 8 and broken 8 for unlinke)

#9 in reply to: ↑ 5 @pbearne
4 years ago

Replying to mark-k:

+1 to the idea

two comments

  1. I think "Re-Sync" is a bad name as it doesn't imply what is synched to what. Maybe "Use current title" is better but probably too long....

not tide to the name in any way

  1. There is a slug metabox for the JS challenged people ;) which you can show/hide with the screen options. It will be nice to have this functionality there as well, maybe by using a checkbox.

yes this is as much about get the thinking going as the finished code

#10 follow-up: @knutsp
4 years ago

I think it should be really annoying to change the permalink of a published post. Immediately after publishing, the permalink may be all over the internet, through automated pings and re-publishing mechanisms. May this lead to 404?

#11 in reply to: ↑ 10 ; follow-up: @nacin
4 years ago

Replying to knutsp:

I think it should be really annoying to change the permalink of a published post. Immediately after publishing, the permalink may be all over the internet, through automated pings and re-publishing mechanisms. May this lead to 404?

It would for hierarchical post types, yes.

#12 in reply to: ↑ 11 @pbearne
4 years ago

Replying to nacin:

Replying to knutsp:

I think it should be really annoying to change the permalink of a published post. Immediately after publishing, the permalink may be all over the internet, through automated pings and re-publishing mechanisms. May this lead to 404?

It would for hierarchical post types, yes.

its sounds like there is space to make it easier and also add warnings / make it harder

#13 @pbearne
3 years ago

Adding new comment to kick this a bit more as I still believe we can do better.

Since I created this I have learned that any URL(permalink) that is used and replaced after a Page/Post has been published are converted to a redirect this not indicated anywhere and so confusing to users.

So I would update the suggest to include that we should add the option to not do this and to list list all the URL's that point to this post with the ability to remove any of the old links.

This is that an URL can re-used if needed and we can see the history / alt's for the post.

Paul


#14 @iseulde
3 years ago

  • Focuses javascript administration added
  • Keywords needs-patch added; has-patch removed

I don't think something like a resync button is an option.

There is some room for improvement though, e.g. when I add a title for a new post and continue to the content, the slug is updated, but this does not happen when I change the title later and didn't touch the title in the meantime. No one knows this will update when you publish, in fact, it's confusing since something different got published than what I thought and was visible.

Patch for this is welcome.

Since I created this I have learned that any URL(permalink) that is used and replaced after a Page/Post has been published are converted to a redirect this not indicated anywhere and so confusing to users.

I don't think this is confusing. If you change the *permalink* of a post after it has been published, it makes sense that there is a redirect form the old post slug. You can definitely reuse the slug for another post and the redirect will disappear automatically.

Note: See TracTickets for help on using tickets.