You can also control how revisions are processed at the level. It is relatively simple to implement. It only needs to pass two parameters to the filter (wp_post object, indicating the number of revisions to be retained and the posts to be published as the target). The
In the summary tomer\/4d4e1b6ace5b 78412944 load, it is obvious that as long as a valid object is returned, the body of the function can be used freely to obtain the required post of a specific type. It is convenient for some users to turn off or restrict the post modification function, but it is not suitable for all users. This is especially true if the database space is limited, or if you do not need to simply save posts automatically. To completely close the modification, WP config. Add the following to the PHP file: Important Rae writes\/a1de23a7c87123fec6ea during loading, if you want to reactivate the modification, you only need to set the value to \
Alternatively, you can use numbers to limit the number of times a post can be modified. For example, the key point is to load WP config in raewrite\/4b3df52b684196d075b. After adding this line to the PHP file, each post can generate up to 10 revisions, and add 1 for automatic saving. If the latest version is saved, the old version is automatically deleted. If you think that the risk of using a revised version is purely helpful to the author and editor on the site website, there is almost nothing to hate under the concept of automatic activation of a revised version. The main knock on them came from the context of the performance on the live website. The
Each revision is stored in the database as a separate entry, so there is a risk that using it on a larger site will unnecessarily hinder the performance of the database. Although it is difficult to accurately and quickly show how much negative impact this will have on a single site, as the site grows, the priority of database optimization will be higher than ever before. With this in mind, we will move on to a few plug-ins that can be used to maintain the virtual house in order to minimize database impact. After using the plug-in to clean up the basic concept of a revision of WordPress, you will find that you need to clean up existing revisions on your site. The value of maintaining all modifications after the work has been completely edited is often vague. The
To wrap up, we will introduce you to four convenient plug-ins for deleting versions that are no longer needed. As with all plug-ins that may affect the database, ensure that the backup policy is working properly before testing these solutions. 1. optimize the database after deleting the revision. After deleting the revision, the database optimization plug-in provides a method to sort out the revision in a procedural way and maintain database size optimization. You can manually invoke the plug-in or set it to run on schedule, create your own log file for later analysis, and select multiple recent revisions that are excluded during cleanup. The
1. are you interested in database optimization after deleting the revision? details WP scan androg Lester Chan’s WP sweep performs a wider WordPress house Kipping function, but can also tame the revision. Plug ins are a useful way to keep your site clean by handling comments, drafts, and modifications at once. 2. interested in WP swepe? details Like WP optimize malewp swepe, WP optimize can remove a large amount of fat from the WordPress database and clean up overflow modifications during the process. You can freely schedule when to run a custom schedule, and use the plug-in to view unwanted draft posts, junk comments, etc.
