Update paths of articles and other content

cedewey commented

2019-08-31 19:54:16 +00:00

(Migrated from gitlab.com)

Background

Articles in the previous site had a path alias pattern of /story/[title], /content/[title], etc. On the new site, articles are listed at /articles. We need to update the path aliases of articles to match, while preserving the original urls.

Work Required

Ensure automatic redirect creation is working
Bulk update articles to use the new path aliases

## Background Articles in the previous site had a path alias pattern of /story/[title], /content/[title], etc. On the new site, articles are listed at /articles. We need to update the path aliases of articles to match, while preserving the original urls. ## Work Required * [ ] Ensure automatic redirect creation is working * [ ] Bulk update articles to use the new path aliases

cedewey commented

2019-08-31 19:55:03 +00:00

(Migrated from gitlab.com)

changed the description

mlncn commented

2019-09-01 03:24:31 +00:00

(Migrated from gitlab.com)

To be clear, this is blocked until the final migration has been run.

Can be tested out earlier, and all the path settings can be defined and saved in config.

To be clear, this is blocked until the final migration has been run. Can be tested out earlier, and all the path settings can be defined and saved in config.

mlncn commented

2019-09-30 20:17:30 +00:00

(Migrated from gitlab.com)

A lot of old URLs also used 'content'. We will be replacing all of the old paths with paths based on the content type, or in the case of collections, the collection type vocabulary:

article/[node:title]
blog/[node:title]
gleaning/[node:title]
people/[node:title]
[node:field_collection_type ?? ]/[node:title]
and for pages and landing pages, just: [title]

cc @cedewey @FreeScholar

What has to be tested on the live site before final migration or locally is that redirects are properly created when pathauto is configured and bulk create run. The exact tokens to use and steps should be updated on this issue.

A lot of old URLs also used 'content'. We will be replacing all of the old paths with paths based on the content type, or in the case of collections, the collection type vocabulary: * article/[node:title] * blog/[node:title] * gleaning/[node:title] * people/[node:title] * [node:field_collection_type ?? ]/[node:title] * and for pages and landing pages, just: [title] cc @cedewey @FreeScholar What has to be tested on the live site before final migration or locally is that redirects are properly created when pathauto is configured and bulk create run. The exact tokens to use and steps should be updated on this issue.

mlncn commented

2019-09-30 20:18:38 +00:00

(Migrated from gitlab.com)

changed title from Update paths of articles to Update paths of articles{+ and other content+}

changed title from **Update paths of articles** to **Update paths of articles{+ and other content+}**

mlncn commented

2019-09-30 20:18:38 +00:00

(Migrated from gitlab.com)

changed the description

cedewey commented

2019-10-16 20:35:46 +00:00

(Migrated from gitlab.com)

assigned to @FreeScholar and unassigned @mlncn

cedewey commented

2019-10-16 20:36:04 +00:00

(Migrated from gitlab.com)

assigned to @cedewey and unassigned @FreeScholar

cedewey commented

2019-10-16 20:36:26 +00:00

(Migrated from gitlab.com)

assigned to @FreeScholar

cedewey commented

2019-10-16 20:45:31 +00:00

(Migrated from gitlab.com)

marked this issue as related to #19

cedewey commented

2019-10-16 20:45:47 +00:00

(Migrated from gitlab.com)

mentioned in issue #19

FreeScholar commented

2019-10-22 18:39:52 +00:00

(Migrated from gitlab.com)

Bulk update paths:

article/[node:title] (story>article)
blog/[node:title]
gleaning/[node:title]
people/[node:title]
[node:field_collection_type ?? ]/[node:title]
and for pages and landing pages, just: [title]

Bulk update paths: * article/[node:title] (story>article) * blog/[node:title] * gleaning/[node:title] * people/[node:title] * [node:field_collection_type ?? ]/[node:title] * and for pages and landing pages, just: [title]

cedewey commented

2019-10-25 19:42:02 +00:00

(Migrated from gitlab.com)

@mlncn @wolcen @FreeScholar ,

I tested this out locally and wasn't successful bulk updating the paths.

The path patterns are already properly set for the site.

I tried the following:

" Update the URL alias for paths having an old URL alias " - this did not change the paths of old articles and other content
"Regenerate URL aliases for all paths" - this did not change the paths of old articles and other content
Delete the aliases, then run the bulk update on paths - This did successfully change the old nodes to use the new path patterns. However, the old paths were not retained.

@mlncn @wolcen @FreeScholar , I tested this out locally and wasn't successful bulk updating the paths. The path patterns are already properly set for the site. I tried the following: * " Update the URL alias for paths having an old URL alias " - this did not change the paths of old articles and other content * "Regenerate URL aliases for all paths" - this did not change the paths of old articles and other content * Delete the aliases, then run the bulk update on paths - This did successfully change the old nodes to use the new path patterns. However, the old paths were not retained.

mlncn commented

2019-11-23 11:14:45 +00:00

(Migrated from gitlab.com)

@gnuget as you just did this for Find It Cambridge it seems, assigning to you for when you can get to it!

mlncn commented

2019-11-23 11:14:45 +00:00

(Migrated from gitlab.com)

assigned to @gnuget

cedewey commented

2020-02-04 22:05:53 +00:00

(Migrated from gitlab.com)

mentioned in issue agaric/proposals#166