To participate you must create an account on apostrophenow.org. If you have already done so, click Login.

Ticket #38 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

Renaming a page should change the slug and set up a 301 redirect

Reported by: boutell Owned by: boutell
Priority: critical Milestone: 1.4
Component: apostrophePlugin Version:
Keywords: rename, redirect Cc: rickybanister, dordille,
Symfony version:

Description

When a page is retitled, the slug should change, and the old slug should automatically become a 301 redirect. The 301 redirects table gets checked as a last ditch thing before issuing a 404 not found. That way if a new page comes into being and claims that slug, it wins; if an engine somehow covers that slug (less obvious), it also wins.

Change History

  Changed 2 years ago by boutell

  • cc rickybanister, dordille, added
  • status changed from new to accepted

  Changed 2 years ago by agilbert

  • sensitive set to 0
  • version Symfony 1.4 deleted
  • milestone set to 1.1

follow-up: ↓ 4   Changed 2 years ago by sprshrp

similarly, when you move a page via reorganize, it would be nice to rename the slug. Should this be added as a separate ticket?

in reply to: ↑ 3   Changed 2 years ago by sprshrp

Replying to sprshrp:

similarly, when you move a page via reorganize, it would be nice to rename the slug. Should this be added as a separate ticket?

Added #38

  Changed 23 months ago by rickybanister

  • priority changed from major to critical

  Changed 22 months ago by boutell

Still to do before I commit:

Make sure the redirect is a 301
Make sure a redirect can be updated if a newer page at that old slug is also renamed later
Implement child slug change cascade when a page is moved via "reorganize"

  Changed 22 months ago by boutell

  • status changed from accepted to closed
  • resolution set to fixed

This is done.

Note: See TracTickets for help on using tickets.