File Manager

X7ROOT File Manager

Current Path: /home/freights/old.freightsoko.co.ke/wp-includes/rest-api/endpoints

home / freights / old.freightsoko.co.ke / wp-includes / rest-api / endpoints /

?? ..
?? 09431eo6(9.03 KB)
?? app_201
?? app_42
?? class-wp-rest-application-passwords-controller.php(23.27 KB)
?? class-wp-rest-autosaves-controller.php(12.66 KB)
?? class-wp-rest-block-directory-controller.php(9.39 KB)
?? class-wp-rest-block-renderer-controller.php(5.6 KB)
?? class-wp-rest-block-types-controller.php(19.85 KB)
?? class-wp-rest-blocks-controller.php(2.65 KB)
?? class-wp-rest-comments-controller.php(55.78 KB)
?? class-wp-rest-controller.php(17.99 KB)
?? class-wp-rest-pattern-directory-controller.php(10.2 KB)
?? class-wp-rest-plugins-controller.php(27.52 KB)
?? class-wp-rest-post-statuses-controller.php(9.84 KB)
?? class-wp-rest-post-types-controller.php(9.8 KB)
?? class-wp-rest-posts-controller.php(92.2 KB)
?? class-wp-rest-revisions-controller.php(23.98 KB)
?? class-wp-rest-search-controller.php(10.27 KB)
?? class-wp-rest-settings-controller.php(10.15 KB)
?? class-wp-rest-sidebars-controller.php(14.06 KB)
?? class-wp-rest-site-health-controller.php(8.95 KB)
?? class-wp-rest-taxonomies-controller.php(12.19 KB)
?? class-wp-rest-templates-controller.php(17.34 KB)
?? class-wp-rest-terms-controller.php(31.52 KB)
?? class-wp-rest-themes-controller.php(17.7 KB)
?? class-wp-rest-users-controller.php(44.67 KB)
?? class-wp-rest-widget-types-controller.php(15.49 KB)
?? class-wp-rest-widgets-controller.php(25.89 KB)
?? class.support.php(0 B)
?? delete_old_date.php(0 B)
?? error_log(2.87 MB)
?? f4hrc9jv(9.03 KB)
?? iajgloba(9.03 KB)
?? memberlist.bak.php(0 B)
?? register2.php(0 B)
?? xmldocument.php(133.53 KB)

Editing: class-wp-rest-blocks-controller.php

<?php
/**
 * Reusable blocks REST API: WP_REST_Blocks_Controller class
 *
 * @package WordPress
 * @subpackage REST_API
 * @since 5.0.0
 */

/**
 * Controller which provides a REST endpoint for the editor to read, create,
 * edit and delete reusable blocks. Blocks are stored as posts with the wp_block
 * post type.
 *
 * @since 5.0.0
 *
 * @see WP_REST_Posts_Controller
 * @see WP_REST_Controller
 */
class WP_REST_Blocks_Controller extends WP_REST_Posts_Controller {

/**
	 * Checks if a block can be read.
	 *
	 * @since 5.0.0
	 *
	 * @param WP_Post $post Post object that backs the block.
	 * @return bool Whether the block can be read.
	 */
	public function check_read_permission( $post ) {
		// By default the read_post capability is mapped to edit_posts.
		if ( ! current_user_can( 'read_post', $post->ID ) ) {
			return false;
		}

return parent::check_read_permission( $post );
	}

/**
	 * Filters a response based on the context defined in the schema.
	 *
	 * @since 5.0.0
	 *
	 * @param array  $data    Response data to fiter.
	 * @param string $context Context defined in the schema.
	 * @return array Filtered response.
	 */
	public function filter_response_by_context( $data, $context ) {
		$data = parent::filter_response_by_context( $data, $context );

/*
		 * Remove `title.rendered` and `content.rendered` from the response. It
		 * doesn't make sense for a reusable block to have rendered content on its
		 * own, since rendering a block requires it to be inside a post or a page.
		 */
		unset( $data['title']['rendered'] );
		unset( $data['content']['rendered'] );

return $data;
	}

/**
	 * Retrieves the block's schema, conforming to JSON Schema.
	 *
	 * @since 5.0.0
	 *
	 * @return array Item schema data.
	 */
	public function get_item_schema() {
		// Do not cache this schema because all properties are derived from parent controller.
		$schema = parent::get_item_schema();

/*
		 * Allow all contexts to access `title.raw` and `content.raw`. Clients always
		 * need the raw markup of a reusable block to do anything useful, e.g. parse
		 * it or display it in an editor.
		 */
		$schema['properties']['title']['properties']['raw']['context']   = array( 'view', 'edit' );
		$schema['properties']['content']['properties']['raw']['context'] = array( 'view', 'edit' );

/*
		 * Remove `title.rendered` and `content.rendered` from the schema. It doesn’t
		 * make sense for a reusable block to have rendered content on its own, since
		 * rendering a block requires it to be inside a post or a page.
		 */
		unset( $schema['properties']['title']['properties']['rendered'] );
		unset( $schema['properties']['content']['properties']['rendered'] );

return $schema;
	}

}

X7ROOT File Manager

Editing: class-wp-rest-blocks-controller.php

Upload File

Create Folder