Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature branch includes minor adjustments to links in several of the templates/content twig files (so that they can still be routed to the handler) as well as an update to the pathauto configurations for items, collections, and several taxonomies (Corporate bodies, Events (Conference), and Persons (Family, Person)).
Import the following configuration files and clear the cache. Additionally, the sitemap file can be purged at this time - to confirm that the new sitemap's urls would be the friendly urls.
Import the config/sync files
To purge the previous sitemap file,
drush sql-query "truncate table simple_sitemap;"
The new pathauto patterns use the tokens:
While the previous patterns should stay intact (while the system prefers the above patterns, it will still handle these routes):
While the agent links are all set to a pre-canned search GET url for that agent, these entities do still have core Drupal routes set up for them such as http://localhost:8000/people/pannabecker-virginia - which were previously set up with default route that looks like this: http://localhost:8000/taxonomy/term/54. We may want to add these core paths to the sitemap.
Look for ./view, ./metadata links on image, digital document item pages. Look for ./members on complex object parent item pages. Look for ./metadata on all other item pages. Additionally, test that the routes for a collection and an item still work when using the [node:nid] route.