Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Done
Priority: High
Fix Version/s: Customer request, 2.3.0-beta1, 2.3.0-rc1, 2.3.0, 1.7.9, 1.13.5
Affects Version/s: 2.1.0, 1.13.2, 1.7.7
Component/s: Database related, Platform > Repository & Services (Public API impl)
Labels:
- migration
- urlalias

Sprint:
[2.4] - Sprint 1

Story Points:
1

Description

Currently, RegenerateUrlAliasesCommand (ezplatform:regenerate:legacy_storage_url_aliases command) doesn't keep historized Url Aliases, which makes it far less useful for the customers. Historized Url Aliases are important for example for SEO, and customers might depend on old URLs.
Therefore, RegenerateUrlAliasesCommand should keep historized Url Aliases, possibly also logging warnings for nodes/URLs that are corrupted (if any).

Attachments

Issue Links

blocks

EZP-29138 Backport RegenerateUrlAliasesCommand to version 5.4

Closed

is blocked by

EZP-29413 URL aliases are not historized properly for multilingual Content

Closed

EZP-27124 Second level URL alias redirects not working if you have translated and renamed content

InputQ

testing discovered

EZP-29386 Aliases for autowired API services exist in AdminUI only

Closed

Sub-Tasks

Broken URL alias history is not restored after regenerating aliases

Closed

Unassigned

100%

Activity

People

Assignee:: Unassigned

Reporter:: Jacek Foremski (Inactive)

Votes:: 2 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 04/May/18 2:30 PM

Updated:: 18/Oct/18 3:23 PM

Resolved:: 18/Oct/18 3:23 PM

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

Include sub-tasks