Redirect an HTML attachment's URL in Whitehall
HtmlAttachments belong to an Edition of a Document. When an Edition is unpublished or withdrawn, there is an option to add a redirect to the URL. This redirect should also be applied to the Edition’s HtmlAttachments, and the new URL sent to the PublishingAPI.
This process does not always work successfully, and HtmlAttachments for unpublished Editions remain accessible via their original URL.
Redirect an Edition’s HtmlAttachments
A Rake Tasks exist in Whitehall to quickly redirect all HtmlAttachments for an unpublished Edition. The tasks takes the Edition’s Document’s content id, and the desired redirection URL.
There are two interfaces for dry and real runs, to ensure the correct HtmlAttachments are being targeted before redirecting.
The Rake task will search for most recent Edition belonging to the Document. The task will throw an
EditionNotUnpublishederror if the Edition is not
withdrawn. The task will throw a
HTMLAttachmentsNotFounderror if the Edition has no HtmlAttachments.
$ bundle exec 'publishing_api:redirect_html_attachments:dry[document_content_id,redirection_url]'
This attempts to locate the HtmlAttachments for the latest unpublished Edition of the Document, and if found, report to the user the HtmlAttachment’s slugs and where they would have been redirected to.
$ bundle exec 'publishing_api:redirect_html_attachments:real[document_content_id,redirection_url]'
This will actually request that the PublishingApi redirects the selected HtmlAttachments.
Republishing the Edition will cause all redirects to be removed, and the HtmlAttachments will again be accessible via their original URL’s, as linked to in the Edition.