WP Manifestindependent plugin directory
manifest / content / wp-post-locking

Post Locking for Frontend archived

Drop-in post locking for WordPress on the frontend

by Scott Kingsley Clark · github.com/sc0ttkclark/wp-post-locking · website

15stars
2forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/sc0ttkclark/wp-post-locking/archive/refs/heads/master.zip

Declares an update source (https://github.com/sc0ttkclark/wp-post-locking), so updates arrive through the plugin's own updater.

From the readme

Post Locking for Frontend Drop-in post locking for WordPress on the frontend This plugin works for Pods, ACF, and Gravity Forms out of the box. Example (singular) Example (list) FAQ When does post locking update? When a person goes to the singular page that has locking support (calls skcpostlockfrontendnotice( $postid )), the lock is set as active for the current user if the user is logged on. Every 15 seconds, the browser will check the lock status and refresh it. After 150 seconds of inactivity, the lock is considered inactive and other people are given the chance to start editing. If the page becomes active again in the browser, the lock will become active again (unless someone else has taken control). You can customize the inactivity limit by filtering the wpcheckpostlockwindow filter: If you wish to disable setting the lock as active, simply set the second parameter as false like this: skcpostlockfrontendnotice( $postid, false ). What if someone else takes control? The notice will be displayed that someone else has control already. If you are using the form on the singular page and someone else takes control from the WP Dashboard area (/wp-admin/), the notice will b

Read the full README on GitHub →

Releases

TagPublished
0.1 Jun 25, 2018

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.