This is because in addition to setting the status, the second problem is caused. The following is an example of using the \
Male call_to_action = $call_to_action;
}The
\/**The
*Add filter
*\/The
Public function add\u hook(){
Add\u filter (‘the\u content’, [$this,’ filter\u content’]);
}The
\/**The
*Delete filter
*\/The
Public function remove\u hook(){
Remove\u filter (‘the\u content’, [$this,’filter\u content’]);
}The
\/**The
*Add CTA to content publishing
*The
*@Param string $content
*The
*@Return string
*\/The
Public function filter_content ($content){
Return $content$ This->call_to_action;
}The
}Each method in this class has a concern. In this sense, we follow the single responsibility principle that all functions or classes must have a task. However, according to the same definition, this class is not a class because it interacts with the plug-in API and adds it to the post content. I like this design. It keeps the entire system as a single device. The system can be reused in other contexts_ You do not need to use content filters at the same time. See the following example: Male post\u content = $appender->filter\u content ($post->post\u content);
Wp_update_post ($post);
}The
The same code is being used in order to apply the same changes when saving the generated post. This example shows how this class can survive when the plug-in API is completely disconnected. According to Tom McFarlin, the single responsibility principle is: \
