Redirection handling

[chachasikes]

Sort our redirection capabilities & decide on data structure desired by headless pipeline.

See if we can expose redirection plugin data to headless in order to give a redirection UI to site admins from wordpress for additional redirects not accommodated by page renames. (Also check how redirection captures page slug renames)

Note: Aaron did some work on this already

[chachasikes]

Hey @aaronhans - Can you update us on the status of this system? What tasks are remaining?

[aaronhans]

Completed:

• Script to create redirects on S3 runnable here https://github.com/cagov/cannabis.ca.gov/blob/f77faec75d1f2f58be5f06ed46e379c109355d2f/package.json#L9 this uses a redirect json file manually exported from the WordPress plugin and writes redirect files that work on S3.

Remaining:

• How should we move the set of redirects managed in WordPress to the frontend repo when it changes?
• The redirects get blown away by the normal deploy action so the redirect creation script should be run after every deploy targeting the appropriate bucket.

[aaronhans]

Open ticket assigned to @wrendo to help prioritize the how will we synch wordpress and git repo redirect set here: https://github.com/cagov/cagov-design-system-headless-wordpress/issues/3

[chachasikes]

This is a duplicate of https://github.com/cagov/cagov-design-system-headless-wordpress/issues/3 Closing & archiving

[chachasikes]

Never mind, reopening!

[aaronhans]

depends on https://github.com/cagov/wordpress-to-github/issues/50

[aaronhans]

Thanks for volunteering to publicly expose the endpoints that let us retrieve the list of existing redirects @chachasikes

We can use this ticket for that work:

Plugin's REST documentation: https://redirection.me/developer/rest-api/

Endpoints we need to hit without authenticating:

https://live-drought-ca-gov.pantheonsite.io/wp-json/redirection/v1/export/1/json or https://live-drought-ca-gov.pantheonsite.io/wp-json/redirection/v1/export/1/csv

I'll complete the additions to wordpress-to-github and the headless repo on the https://github.com/cagov/cagov-design-system-headless-wordpress/issues/3 ticket

[xjensen]

@aaronhans It turns out I'm already working on cagov/wordpress-to-github#50. The PR is at cagov/wordpress-to-github#91. See this comment for details.

[chachasikes]

(pre-merged example: https://github.com/cagov/drought.ca.gov/blob/odi-engineering-32/restore-redirects/src/redirects/assign.js)

Updates on this:

• I will try to expose get the JSON (not CSV as discussed yesterday on Slack) - it will align with the other work we are doing. (The plugin extension I need to write extends a package that was designed for AJAX API usage & isn't directly exposable without changing permissions in the wrong way, but I think I can create an extension.

• ISSUE: There are some structural issues with the way the plugin is constructed that lower my confidence in success here, but I came up with an idea yesterday to load the main class & create our own endpoint with the data using their pattern and adding a new role.

• The redirection plugin keeps track of slug changes, not system wide WordPress changes.

  • There is also a "settings" API function that could probably include any replacement patterns, but this has some issues: it's an experimental feature of redirection, and we don't need to recommend that CAWeb change the post path structures at a system level anytime soon. If there are route changes, I recommend generating a CSV of the changes & adding them to the redirect table so the data is accessible through one input that we can focus on making great.

[chachasikes]

Is duplicate of #56

Closing this one & keeping one main thread for redirects.