WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 5 years ago

#7022 closed defect (bug) (invalid)

editing timestamp without modifying post URL not possible?

Reported by: mikafoobar Owned by: markjaquith
Milestone: 2.9 Priority: normal
Severity: normal Version: 2.5.1
Component: Canonical Keywords:
Focuses: Cc:

Description

When editing a post which has been published already, I can edit the timestamp using the "Published on:"-item within the "Publish Status" box, but then the URL of my blog entry (using the "Day and name" permalink structure) changes. So instead of keeping $DOMAIN/blog/2008-05-10/foobar as the blog entries URL it will become $DOMAIN/blog/2008-05-22/foobar instead; people linking to the old entry ("$DOMAIN/blog/2008-05-10/foobar") will get a 404 error then. :(

IIRC it was possible to edit the timestamp of a specific blog post without changing the "published on" property in earlier wordpress versions, that's the behaviour I'd like to get back. :)

So instead of modifying the URL of my blog entry when updating information inside an article I'd like to just modify the timestamp of it so people get an update of the post via RSS.

Thanks.

Attachments (2)

7022.diff (2.0 KB) - added by DD32 6 years ago.
7022.2.diff (2.1 KB) - added by DD32 6 years ago.
oops, Should've included updated PHPDoc for that diff

Download all attachments as: .zip

Change History (9)

comment:1 Viper007Bond6 years ago

To the best of my knowledge, that's never been possible. The monday/day/year in the URL has always reflected the post date.

Plus, I don't think most people's RSS readers will notice the update as the post's GUID won't have changed.

-1 to the permalink not changing.

+1 to a redirect being put in place, much like when you change the stub.

comment:2 DD326 years ago

  • Milestone set to 2.6

+1 to a redirect being put in place, much like when you change the stub.

Hm.. I thought that allready happened.

I've just made some small changes to the Canonical redirection code:

  • First, Do as usual, Look for a post that starts with the slug (ie. find future-post if only future-po was given in the url) refining with the date components if given
  • Else, if nothing found, Search again, But look for an *exact* match for the slug in ALL months, and redirect to that.

..I'm thinking this could be too redirect happy though, It might redirect to things that its not meant to (which is why it looks for an exact match).

DD326 years ago

DD326 years ago

oops, Should've included updated PHPDoc for that diff

comment:3 mikafoobar6 years ago

Thanks for the patch, I've tested it and it fixes my URL redirection (404) problem, thanks!

The post's GUID isn't modified, yes - but for example "pubDate" seems to be updated and I'm sure that I was able to provide updates to my blog readers using the "edit timestap" function. I'm reading/checking my blog's feed on my own using bloglines.com as RSS reader and I always got those updates.

IMHO this behaviour is important because it gives you the option to update a post and notify users about that update within the article itself, without the need to write a metapost like "hello, check out updated foo". Any chance to get that behaviour back as well? :)

Thanks!

comment:4 Denis-de-Bernardy5 years ago

  • Component changed from General to Canonical
  • Owner changed from anonymous to markjaquith

enforcing permalink history would fix this.

comment:5 follow-up: mikafoobar5 years ago

Ok, what does "enforcing permalink history would fix this" mean for me? :)

I just stumbled once again upon this issue (updating timestamp to send updates via RSS but old URL is non-existent anymore then). :(

Is this something which is already available or is this something which has to be implemented yet? Sorry, couldn't find anything about it, I just see "2.9" in the milestone property so I guess this is something not available yet, right?

Thanks.

comment:6 in reply to: ↑ 5 Denis-de-Bernardy5 years ago

Replying to mikafoobar:

Ok, what does "enforcing permalink history would fix this" mean for me? :)

basically, that it won't be fixed until that's done. It's on the todo list for 2.9.

I believe there's a plugin that takes of this, btw, you might want to google for it in the meanwhile.

comment:7 scribu5 years ago

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

Reasons for closing as invalid:

  • if a post has the url /2009/08/01/ it should actually have that publish date.
  • permalink history is already implemented in a plugin: Redirection
  • when updating a post, WP already notifies RSS readers, so you don't have to modify the timestamp
Note: See TracTickets for help on using tickets.