Portlets
Update a custom content tool
Changed onReplaces the name, base types, content types and data view mode of an existing custom content tool. Refuses, with 404 and no change, an id that is not a custom content tool: tools shipped with the product cannot be rewritten this way. Requires an authenticated back-end user with access to the roles, tools or tools-beta portlet, or the CMS Administrator role.
put/api/v1/portlet/custom
Request
- Base URLhttps://docs.anzworldline-solutions.com.au
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Response
Updated; the entity carries the stored portlet id under "portlet"
Changes
- info
api tag
Portletsadded - info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the success response with the status
- info