andyexeter

Hi @dgibb,

It sounds like you have added your pages to the protected list, not the locked list.

Protected posts are those which can still be edited, but cannot be trashed/deleted by non admins. Locked posts cannot be edited, trashed or deleted.

If you go to the plugin settings page, make sure the pages are in the Locked list (the top one), and not the Protected list.

Hey Marc,

The best solution I can think of would be to assign the user to a new role which has all capabilities of an administrator, then create a new capability for administrators only. Perhaps something like manage_options_and_kb_posts.

Once the new role and capability are created you would then use the postlockdown_admin_capability filter to use the new capability rather than the default manage_options:

add_filter('postlockdown_admin_capability', function() {
    return 'manage_options_and_kb_posts';
});

I have used the User Role Editor plugin for managing user roles and capabilities in the past and it seemed to work pretty well.

Let me know how you get on!

Hey shawfactor,

I just wanted to let you know that private posts/pages are now able to be marked as protected or locked in the latest version of the plugin! (2.0.3)

Hey shawfactor,

Thanks for your review and feedback.

I agree that private posts/pages should show up in the search and I will update the plugin to do that as soon as I have time.

In the meantime, you can modify the args that the plugin uses to get posts and pages for the search using the postlockdown_get_posts filter:

add_filter('postlockdown_get_posts', function($args) {
    $args['post_status'][] = 'private';
    return $args;
});

This isn’t tested but should work and pull through private posts/pages 🙂

Hi Robswaimea,

Sorry I haven’t replied sooner, I didn’t get a notification that you’d posted.

I had a look into the plugin in question and I believe you’re right, they appear to handle managing/deleting of events internally using their own custom capabilities.

If the plugin was to pass in the associated object_id with its calls to current_user_can, then you could get around this by filtering the capabilities Post Lockdown looks for with something like:

add_filter('postlockdown_capabilities', function($caps) {
    $caps['delete_events'] = true;
    $caps['edit_events'] = true;
    return $caps;
});

However, this won’t work right now because they’re just calling current_user_can('delete_events') with no context, so Post Lockdown can’t lookup the associated object_id and see if it is locked or protected.

It may be worth reaching out to the maintainers of the events plugin and asking if they can add the object ID into their calls to current_user_can.

• This reply was modified 8 years, 11 months ago by andyexeter.

Hey Sebastian,

Thanks for your message. I really like the idea, I’m a bit tied up with paid work at the moment but this is something I would like to implement.

Version 2 of the plugin has been in the pipeline for a while now, but I think I’m going to add this feature in before I release it.

I think icons are a better way to go than text, and I think I’ll make this an opt-in feature as some people who already use the plugin might not want to see any changes to their post/page lists.

Thanks again for the message, I’ll let you know when the new version is released 🙂