![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 10 years ago
Last modified 5 months ago
#38067 new enhancement
New filter `wp_post_lock_status`
| Reported by: | sebastian.pisula | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Posts, Post Types | Version: | 2.5 |
| Severity: | normal | Keywords: | has-patch has-test-info needs-testing needs-unit-tests |
| Cc: | Focuses: |
Description
I have wp with one account for 5 people, employees. We make websites so 5 accounts for each website -> waste of time and difficult to maintain. We have big problem - if somebody edit page and I start edit the same page we have conficts and overwrite own changes. I can't see notice about that somebody edit this page because we use one account. My best idea! When user is logged in i create new cookie: wordpress_logged_in_unique_COOKIEHASH with unique hash -> user agent + wp_generate_password().
I save user hash if _edit_lock_hash was saved.
So I can't check that post is locked or. So I write filter for return value of wp_check_post_lock() and... this work!
I suggest add this filter (idea) to core or show me other way to resolve my problem.
Attachments (2)
Change History (10)
This ticket was mentioned in Slack in #core by sebastian.pisula. View the logs.
10 years ago
#3
@
7 years ago
- Keywords needs-refresh added
- Version → 2.5
He @sebastianpisula,
Thanks for this. Your filter request seems sensible. I do recommend using different user accounts, but I could see scenarios where a site would want to implement custom logic for post locking.
The patch needs a refresh against the latest trunk, though. Are you able to take care of that?
This ticket was mentioned in Slack in #core by sirlouen. View the logs.
9 months ago
This ticket was mentioned in PR #10306 on WordPress/wordpress-develop by @SirLouen.
9 months ago
#5
- Keywords needs-refresh removed
Trac ticket: https://core.trac.wordpress.org/ticket/38067
#6
@
9 months ago
- Keywords has-test-info needs-testing added
- Milestone Awaiting Review → Future Release
- Type feature request → enhancement
This hook has had no traction in 9 years. But I've been thinking on potential workarounds, and I can't think on a better workaround than this hook.
It's very ad-hoc though but after review, this patch should go in.
For testing Instructions, the ones provided by OP, he has provided a sample test plugin
if filter will be exists this is solution for my problem. I need only filter :)