Quantity can change type. PHP has no problems with this code$ Foo= \
$foo=array (\
This flexibility is useful, but functions that pass variables of the wrong type can cause errors. Functions written to predict arrays may have errors passing strings. Consider the following features: Function slug_display_status ($post){
Echo $post->post\u status;
}Unless $post is an object of the wp\u post class, and the public attribute $post\u status is disabled or changed to a non echo type, it will work completely. Technically, all objects can use the magic\u get() method to return the public attribute or ecotype of $post\u status. Yes, it has become more metaphysical here. But this is a problem we need to worry about in terms of verification. In a more realistic annotation, the function is likely to pass the post Id rather than the object. So here is a simple change to check the input. Function slug_display_status ($post){
If (is_numeric ($post)){
$post = get_post ($post);
}The
If (is_object ($post) & & isset ($post->post\u status)){
Echo $post->post\u status;
}The
}In this case, we not only guarantee that $post is an object with the public attribute of post\u status, but also provide an opportunity to convert the most likely type of invalid input to valid input. The same principle applies when everyone receives data from HTTP requests together. So now, I want to synthesize everything we have discussed so far. We will use the different parts shown so far to create a request consisting of a post ID, an array of data to save, and a temporary item. Verify that the request has been approved, that the required data exists, and that the format is correct. In addition, information or error data of the affected posts will be returned. Before you start, if you are a beginner, please remember the following two points: First, conditional statements are evaluated from left to right. In other words, there are two conditions. One can only be evaluated safely when the other passes. If the order is correct, it doesn’t matter. For example: if (is_array ($bats) &&isset ($bats[\
}If $bats is not an array, PHP is only valid if $bats is an array, so the second conditional statement will not be reached. Conversely, if the order is reversed and $bats is not an array, a problem occurs. Another thing to remember is that statistically, my syntax ensures that errors occur in older versions of PHP that many people may be using. Please be kind and stop. First, make sure the request is approved. The first bit of this code is very similar to the code described earlier. However, if validation fails, set the status header to display errors and exit. If (isset ($\u post[‘\u wponce’]) & & wp\u verify\u nonce ($\u post[‘\u wponce’]){
If (current_user_can (‘some\u capability’){
\/\/Has the request been approved?
}Another{
Status_header (‘403’);
dice
}The
}Another{
