Purple Redirects

purple hub summary whenever the slug of a post or taxonomy changes, we create a redirect in the purple hub to point the user to the new, changed item and prevent broken links on your site you can also create your own redirects or import them from a json file the redirect feature has its own settings page, which is used to create new redirects (or status codes) and also lists all the redirects created in your purple hub you can find the settings page in the menu in your purple hub under 'redirects' redirects are synchronized with the content cloud and are also available via the catalog api preconditions you can create or change redirects with any role in purple hub explanation redirects can be created in three ways 1\ automatically, on the content you want to redirect itself 2\ manually, by creating a redirect/status code on the redirects settings page 3\ by importing using the import functionality on the redirects settings page you can also update existing redirects automatic redirect created on the content itself when an existing (and published) slug is changed within a permalink on a piece of content, a redirect is automatically created pointing to the new permalink this works for articles (and all post types) and taxonomies how to create a redirect from an article (and any other type of post) by changing the url https //docs purplepublish com/editorial/change the url of an article how to create a redirect from a taxonomy (e g category) by changing the slug https //docs purplepublish com/editorial/change the slug of a taxonomy once you have created the redirects from content, your new redirect will automatically be listed on the redirect features page and will be executed as a 301 redirect manual redirect, created on the redirects settings page description of the redirects settings 1 content type defines the type of content for which you want to create a redirect generic no specific redirect is defined, can be used for any content type content for articles, pages, or any other post type taxonomy for tags, categories or any other type of taxonomy collection for collections 2\ redirect type to understand which redirect type is appropriate for your use case, read the explanation of redirect types here https //docs purplepublish com/editorial/redirect types explained 301 permanent redirect 302 temporary redirect 307 temporary redirect 410 status code removed 451 status code unavailable due to legal reasons 3 release type indicates the type of publishing status of your content for which you want to perform the redirect release to be selected if the content is already published preview to be selected if the content hasn't been published yet and is still in preview mode 4\ old slug used to map your redirect to the existing content, the current slug (permalink within the url) of your content must be entered here with a slash ('/') e g ' /kultur ' 5\ new slug used to redirect the content to its new location, the new slug (permalink within the url) must be entered here with a slash ('/') e g ' /lokales ' 6\ create or update redirects confirm and execute the above changes so that the redirect is created immediately the new redirect will be listed on the redirect settings page, below this button find the step by step guide on the manual creation of a redirect here if there is already a redirect with the same combination of content type and old slug, it will be updated instead of creating a new redirect import redirects redirect imports this feature is available from the redirect settings page in purple hub for example, if you have multiple redirects in your old system that you want to migrate to your purple hub, you can easily import them this is particularly useful for migration scenarios where you need to match numerous old url structures to new url structures to do this, create an import json file that contains the same values/properties that the manual redirect feature above requires when creating a new redirect/status code edit the json locally and upload it if you want to change the redirects, download the file, change it and upload it again to overwrite the old status if you upload a new file that does not contain your old redirects, only the new ones will remain, the old ones will be deleted 1 choose file used to upload your json file for mapping the redirects you can download and fill this example file with the redirects, which you would like to import example file https //archbee doc uploads s3 amazonaws com/ygr6ktt9qi r0u3uktjsm/tfu55kb xmsnsezc2mnnu imports json 2\ import redirects file confirms execution of the uploaded redirect import and converts the elements to redirects when executed, they will be listed below on the redirect settings page in the redirect overview example extract of a json file for importing redirects \[ { "identifier" "/oldslug", "target" "/newslug", "contenttype" "content", "redirecttype" "301", "releasetype" "release" } ] identifier defines the old slug, which you want to be redirected start the url path with a slash e g " / oldslug" target defines the new slug, which you want the old url to link to start the url path with a slash e g " / newslug" contenttype defines the type of content for which you want to create a redirect generic no specific content type is defined, can be used for any content type content for articles, pages, or any other post type taxonomy for tags, categories or any other taxonomy type collection for collections redirecttype defines the type of redirect or status code that you want to be performed for your redirect 301 permanent redirect 302 temporary redirect 307 temporary redirect 410 status code removed 451 status code unavailable due to legal reasons releasetype defines the type of publishing status of your content for which you want the redirect to be performed release if the content is already published preview if the content isn't published yet and is still on preview mode update an existing redirect to update an existing redirect, simply use the same function as to create a manual redirect use the initial source slug as 'old slug' and the new target slug as 'new slug' the target slug you defined for the previously created redirect won't be relevant any more bulk actions for redirects on the redirects settings page, you have the option to perform bulk actions, if you want to edit numerous redirects at the same time so that you don't have to touch the one by one bulk actions delete permanently (1) you can mass select the items on which you want the permanent deletion to be executed by ticking the box next to the item in the list of redirects (2)