Search Results for:

We’ve all done it before — accidentally published a post before it was ready to go. With Edit Flow, you can minimize these accidents by hiding the “Publish” button for your in-progress custom statuses, and then only showing it when the post has reached the last stage of production.

First, read the introduction to extending Edit Flow. Once you’ve done so, you can modify the code snippet below to work for your needs. It will simply hide the “Publish” button until you’ve saved the post with one of the statuses in the array.

[sourcecode language=”php”]
/**
* Hide the "Publish" button until a post is ready to be published
* In this example, we only show the "Publish button" until the post has the "Pending" status
*
* @see http://editflow.org/extend/hide-the-publish-button-for-certain-custom-statuses/
*/
function efx_hide_publish_button_until() {

if ( ! function_exists( ‘EditFlow’ ) )
return;

if ( ! EditFlow()->custom_status->is_whitelisted_page() )
return;

// Show the publish button if the post has one of these statuses
$show_publish_button_for_status = array(
‘pending’,
// The statuses below are WordPress’ public statuses
‘future’,
‘publish’,
‘schedule’,
‘private’,
);
if ( ! in_array( get_post_status(), $show_publish_button_for_status ) ) {
?>
<style>
/** Classic Editor **/
#publishing-action { display: none; }

/** Gutenberg Editor **/
.edit-post-header__settings .components-button.editor-post-publish-panel__toggle { display: none; }
</style>
<?php
}
}
add_action( ‘admin_head’, ‘efx_hide_publish_button_until’ );
[/sourcecode]

Edit Flow is a free plugin you can easily download and install from the WordPress.org plugin directory or be found on GitHub.

In v0.7.2, we added the ability for users without the ‘publish_posts’ capability to use any of your custom statuses — not just “Draft” and “Pending Review.” If you’d like to enforce a more structured workflow, it’s now an easy thing to restrict access to specific post statuses based on user role, capabilities or user group relationship. If a user doesn’t have access to a given status, they’ll still be able to edit the post when it’s saved with that status.

If you haven’t already, please read the introduction to extending Edit Flow. Once you’ve done so, you can modify the example below to your needs. This particular example limits the post statuses available to a user with the “Contributor” role.

[sourcecode language=”php”]
/**
* Limit custom statuses based on user role
* In this example, we limit the statuses available to the
* ‘contributor’ user role
*
* @see http://editflow.org/extend/limit-custom-statuses-based-on-user-role/
*
* @param array $custom_statuses The existing custom status objects
* @return array $custom_statuses Our possibly modified set of custom statuses
*/
function efx_limit_custom_statuses_by_role( $custom_statuses ) {

$current_user = wp_get_current_user();
switch( $current_user->roles[0] ) {
// Only allow a contributor to access specific statuses from the dropdown
case ‘contributor’:
$permitted_statuses = array(
‘pitch’,
‘draft’,
‘in-progress’,
);
// Remove the custom status if it’s not whitelisted
foreach( $custom_statuses as $key => $custom_status ) {
if ( !in_array( $custom_status->slug, $permitted_statuses ) )
unset( $custom_statuses[$key] );
}
break;
}
return $custom_statuses;
}
add_filter( ‘ef_custom_status_list’, ‘efx_limit_custom_statuses_by_role’ );
[/sourcecode]

There are a few CSS classes wrapped around each post on the calendar by default. Customizing these further is just a matter of modifying the classes with the ef_calendar_table_td_li_classes filter.

If you haven’t already, please read the introduction to extending Edit Flow. Once you’ve done so, you can modify the example below to your needs. This particular example will add the post categories as additional CSS selectors.

[sourcecode language=”php”]
/**
* Modify CSS classes applied to posts on the calendar
*
* @see http://editflow.org/extend/modify-css-classes-applied-to-posts-on-the-calendar/
*
* @param array $post_classes Existing post classes
* @param string $week_single_date The date this post appears on
* @param int $post_id Unique identifier for the post we’re modifying
* @return array $post_classes Post classes after we’ve made any requisite modifications
*/
function efx_modify_calendar_post_css_classes( $post_classes, $week_single_date, $post_id ) {

$categories = wp_get_post_categories( $post_id, array( ‘fields’ => ‘slugs’ ) );
foreach( (array)$categories as $category ) {
$post_classes[] = ‘category-‘ . $category;
}
return $post_classes;
}
add_filter( ‘ef_calendar_table_td_li_classes’, ‘efx_modify_calendar_post_css_classes’, 10, 3 );
[/sourcecode]

In v0.7, we changed the behavior of the calendar to display posts based on the sort order of your custom statuses. The idea here is that the earliest posts in your workflow are most likely the ones needing the most attention.

If this isn’t the case for you, you can hook into the 'ef_calendar_posts_for_week' filter to sort the posts however you’d like. If you haven’t already, please read the introduction to extending Edit Flow. The code snippet below sorts posts into chronological order; you may need a bit of PHP knowledge to modify it to a different approach.

[sourcecode language=”php”]
<?php
/**
* Change sort order of posts on the calendar
* Take the already sorted posts and sort them again
* based on our own criteria
*
* @see http://editflow.org/extend/change-sort-order-of-posts-on-the-calendar/
*
* @param array $day_posts An array of post objects for the day
* @return array $day_posts Our re-sorted array of post objects
*/
function efx_change_calendar_posts_sort_order( $day_posts ) {

// Load the posts into a temporary array by post_date timestamp for sorting
$tmp_posts = array();
foreach( $day_posts as $post_obj ) {
$post_date_timestamp = strtotime( $post_obj->post_date );
$tmp_posts[$post_date_timestamp] = $post_obj;
}
ksort( $tmp_posts, SORT_NUMERIC );
// Re-load the post objects onto our array of posts
$day_posts = array();
foreach( $tmp_posts as $post_obj ) {
$day_posts[] = $post_obj;
}
return $day_posts;
}
add_filter( ‘ef_calendar_posts_for_week’, ‘efx_change_calendar_posts_sort_order’ );[/sourcecode]

In v0.7, we reintroduced the ability to drag and drop posts on the calendar. It can work in one of two ways: you can drag and drop for scheduling purposes and not affect the publication date, or you can change the publication date.

Users can drag and drop a post if they have permissions to modify the post. This closely how core works: contributors can modify their own unpublished posts, authors can modify their own unpublished and published posts, and editors can modify everyone’s content. You may not want to allow every user to drag and drop posts on the calendar though.

First, read the introduction to extending Edit Flow. Once you’ve done so, you can modify the code snippet below to work for your needs. Basically, what’s happening is we’re removing some code for users who don’t match our criteria.

[sourcecode language=”php”]<?php
/**
* Only allow specific users to drag and drop posts on the calendar
* The easiest way to do this is just removing the class that makes them sortable
*
* @see http://editflow.org/extend/only-allow-specific-users-to-drag-and-drop-posts-on-the-calendar/
*
* @param array $post_classes A list of the classes to be printed for each item
* @return array $post_classes The possibly modified post classes
*/
function efx_restrict_calendar_drag_and_drop( $post_classes ) {

// This takes a whitelist approach; only user logins appearing in
// the $permitted_users array will be permitted to drag and drop
$permitted_users = array(
// ‘daniel’, // Add whichever usernames you’d like as pieces of the array and uncomment
);
// Unset the ‘sortable’ class if the user isn’t in our whitelist
// The ‘sortable’ class is used by jQuery to determine whether a post can be moved
if ( !in_array( wp_get_current_user()->user_login, $permitted_users ) ) {
foreach( $post_classes as $key => $post_class ) {
if ( ‘sortable’ == $post_class )
unset( $post_classes[$key] );
}
}
return $post_classes;
}
add_action( ‘ef_calendar_table_td_li_classes’, ‘efx_restrict_calendar_drag_and_drop’ );[/sourcecode]

With a bit of PHP knowledge, you can easily modify the snippet to blacklist users instead of whitelisting them (e.g. if ( in_array( wp_get_current_user()->user_login, $blacklisted_users ) ), or handle access based on user capabilities (e.g. if ( !current_user_can( 'publish_posts' ) ).