The ability to create redirects via the Drafts API is welcome, but feels half baked w/o also having the ability to check for and create and otherwise manage resolvers. For a large percentage of redirects, we're having to add resolvers via the PB GUI and then use an API to create the actual redirect. So, its both development work, and digops type work.
As a developer, the worflow is terrible and would be vasly improved if we could check for and create/alter resolvers via an API.
As a digops or support person, the workflow is terrible as they need to check for update/create a resolver in the PB Gui and then get a developer to create the actual redirect.
Thanks for listening :-)
@see:
https://advancelocal.arcpublishing.com/alc/answers/1607/what-api-can-we-use-for-managing-resolvers
Craig Thomas
| Categories | User Workflow, Developer Tools, Developer Workflow |
| I need it... | Yesterday (let's go already) |
Thanks Richard! that seems to work. ( not sure why we didn't get notified of the comment until seeing it mixed in with the admin's today?) we've tested the content-api resolver on a few redirects and it sure seems like it will work out better than what we'd been doing.
Thanks to Kirti as well.
I would suggest the content-api resolver be added to the ARC Draft API documenation for redirects!
Thank you for the idea. We will not provide an API for managing resolvers but we definitely have a few initiatives to address and streamline this workflow in the future.
We are currently avoiding the need for specific redirect resolvers by combining our last "catch-all" resolver with a lookup to the content api. This allows for all previous resolvers to catch to process and pass on a request but then process the request before returning a 404 error for content not found.
Specifically we have our content by section resolver/content source last. If a URI is not resolved by looking up by section then we check the content-api before letting it trigger a 404.