Delete View - Plugixa FAQ for WordPress

Delete View - Plugixa FAQ

DELETE /plugixa-faq/v1/views/{id}

Delete a view. The default view cannot be deleted.

Any signed-in user with the plugixa_faq_delete capability or WordPress’s edit_posts (Contributors and up, by default).

Note. Shortcodes and blocks that use the deleted view’s slug are not changed. There is no existence check: an id that matches nothing still answers 200 with the success message, and nothing changes.

Request

DELETE https://your-site.example/wp-json/plugixa-faq/v1/views/2

Path parameters

Name	Type	Description
`id`	`integer`	The view’s id

Responses

`200` OK.

{
  "success": true,
  "message": "View deleted successfully",
  "data": null
}

Field	Type	Meaning
`message`	`string`	A human-readable confirmation, translated to the site language

Errors

Status	Code	When
`403`	`rest_error`	It is the default view. Make another view the default first.
`500`	`rest_error`	The database refused the delete.

Plus the errors every endpoint can return.

Examples

curl -s -X DELETE "https://your-site.example/wp-json/plugixa-faq/v1/views/2" \
  -u "admin:$WP_APP_PASSWORD"

<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-faq/v1/views/2');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST  => 'DELETE',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_USERPWD        => 'admin:' . getenv('WP_APP_PASSWORD'),
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

const response = await fetch('https://your-site.example/wp-json/plugixa-faq/v1/views/2', {
  method: 'DELETE',
  headers: {
    'Authorization': 'Basic ' + btoa(`admin:${process.env.WP_APP_PASSWORD}`),
  },
});
const { data } = await response.json();