Alternatively, use the free Lite version in the word press plug-in repository. Wpdatatables does not limit the number of data structures, columns, or rows, and supports many data types and various editor input types. Certain types, such as attachments or datetime. You can also use a spreadsheet editor, such as an inline editor or excel, to edit data through the pop-up form editor. The
If you still think WordPress needs to build a custom crud system, you need to prepare serious coding to do this. If you think there is no plug-in suitable for starting the new word press plug-in, please create it yourself! It may not be as terrible as it was at first sight. Read and start this wonderful tutorial to learn how to create a WordPress plug-in from scratch. Of course, this is WordPress Codex. When creating plug-ins (including the crud system of WordPress plug-ins), the first initial step is to configure the file correctly. The usual method is to place the default project crud point file in the root directory of the plug-in and prepare multiple subfolders. The
Assets – all JavaScript, stylesheets, fonts, images, and other static assets required by the crud system. Source – a folder of \
If you use an external dB, you must use a separate PDO connection or use the built-in PHP MySQL function (if the DB engine is MySQL). In this step, you need to prepare a set of classes and methods, accept data in the format expected by the front end, check and delete validation (deleting all inputs is a very important security measure for all crud systems), and then perform the following operations: Insert, update, and delete operations on the database. As described in the previous step, these \
After preparing the front-end interface to create (HTML, JS, PHP) database management classes and methods, the plug-in needs a front-end interface, and users can use the new crud system of WordPress. The best solution is to prepare the template set in the new plug-in file and output it in short code as needed. It is recommended that HTML templates always be separated from code (MVC mode) and prepare template files that are logically separated. For example: \
Here, you can read the excellent Codex articles of the WordPress shortcode API. Ajax call (JS) can not only connect the front end and the back end, but also submit simple forms and refresh pages in \
We recommend that you learn how to use ax. In the plug-in, both the administrator and the front end have excellent Codex articles on how to use ajax. The
You can put the JS code into the \
The server accepts or rejects. Stateless persons androg stateless limit the types of requests that can be submitted between consumers and servers. In fact, it is the request that initiates the client service communication, where the request contains all the information required for the server response. The purpose of the cache request is to instruct the server to specify a label for whether the cache can cache the response, so it is not necessary to submit the same request twice. Therefore, the cache reduces the constraints or restrictions generated by statelessness. Uniform contract prohibits the use of multiple independent interfaces within an API or API. Rest adheres to the principle of uniform contract. Therefore, a rest interface is shared through hypermedia connections. Layered system a layered system uses multiple independent layers to develop and extend interfaces. Since the hierarchies are not visible to each other, you can insert new requests and middleware that have no impact on the initial commands and client server functionality. Optional: on demand code client server, cache, stateless person, unified contract and hierarchical system are required for restful applications, but code on demand is not required. However, code on demand can keep the logic in the client independent, so it can be updated independently of the server logic. End your thinking about crud and rest crud is accompanied by necessary operations in a static data repository or database, such as manual recording or object processing. By default, crud operates on default data. Rest relies on representing resources through unique URLs. Where resources are object abstractions, for example, user descriptions can be resources. Similarly, rest is accompanied by records or exceptions in the annotation table. Rest is about the relationship between records and user resources and the posts \/ comments associated with related records. Rest is a high-level API style for interacting with complex systems. Of course, this report is not a complete tutorial. Because it takes 20 pages to create one. However, if you have a few questions or want to see examples of specific steps, please let me know. I hope it can help in any way. Thank you for reading! Image source: http:\/\/www.tyseo.net
