Forum Replies Created

Viewing 15 replies - 121 through 135 (of 193 total)
  • If you can, you might want to try updating to v0.8 and see if that solves the scheduling problem.

    Also, what sort of plugins and theme are you currently using? There might be some issue with a plugin or theme that’s causing the Schedule button to disappear.

    As for deactivating it, there shouldn’t be any serious issue. I would recommend moving posts that are currently a custom status to a non-custom status (“Draft”, “Pending Review”, “Published”, etc) which would is likely the only major issue that could occur if you deactivate it (even then there probably won’t be much of an issue, if at all).

    There shouldn’t be any other issues, you’ll just lose things like the Editorial Comments and Editorial Metadata, user groups, etc, but if that’s not a problem then you should be good to go!

    Thanks, and sorry for the trouble!

    -CJ

    It shouldn’t be the case that deleting “Pending Review” throws everything out of whack (just did so locally and everything seems to be working fine).

    I’ll work on installing the plugins you mentioned and testing with those. What theme do you currently use?

    Thanks,
    CJ

    Interesting. Like the idea, have to think on it a bit more. One possible avenue if this is something you need like next week would be to leverage one of the custom meta fields and build a widget on top of that.

    Maybe you have a meta field called ‘Assigned’, and then you could build a dead simple widget on the admin page which queried posts based on that custom meta. WP_Query provides some capacity for doing this and you can check it out here. All you’d have to do is get the logged in user and query all posts with that meta field (‘assigned’) and see if the logged in user is the value of that field. For an editor, maybe you just get the five most recent posts with that metadata and display it in the widget.

    Just a thought. I haven’t tested or written anything at all but figured I’d lob out a possible avenue of approach if you need to get rolling on this asap. If you do get around to building it before we flesh it out a bit, feel free to submit a pull request for it! Would definitely like to see it in action.

    Hey,
    Sorry, just a few questions for clarification:

    1. Are you expecting to see “Documents” in the second select? That should be showing “Category” names. The Documents in WP Document Revisions are a post type, not a category
    2. When I installed WP Document Revisions I was seeing other users in the 3rd select. What kind of users are you expecting to see?

    Thanks!
    -CJ

    Hrm. Currently, when I set WordPress time from the “Settings” menu to “Chicago” it’s showing Mon 11/11/2013. What was the time in Chicago when you were seeing the problem?

    Are you currently seeing the problem now? (It’s 9:00pm EST, so 8:00pm CST? Should be showing Mon 11/11/2013).

    Also, what theme/plugins are you currently using? Might be having an effect on the time.

    I’ve tried testing this on the Edit Flow master development branch (https://github.com/Automattic/Edit-Flow/tree/master) in the following way:
    1) Create a custom post type called ‘books’
    2) Create a post of custom post type ‘books’
    3) Write a few lines and preview it. Save it as a draft and preview it. Preview it from the Manage Books” screen

    In all three cases I did not encounter a 404, so it appears to have been fixed. If you’re able to download it and test it, please do. If not, v0.8 should be out pretty soon, looking to finish up a few tickets and then roll it out.

    Thanks,
    CJ

    Definitely wouldn’t hurt. If they figure out what’s causing the issue, definitely post back here. I’d like to fix if possible.

    Odd. It may be theme related (I know another user was reporting an issue they were having which also involved the Made theme). Unfortunately, given that it’s a premium theme I can’t really work on triggering this issue. I’ll continue to try and debug on my end (I pushed a “fix” which just adds another check if any custom statuses exist, but I’ll take a stab and say the theme may be manipulating a filter or action dealing with terms that affects Edit Flow in some fashion, causing that bug).

    Thanks,
    CJ

    Hey,
    So I was messing around and something like the following should work:

    add_filter( 'ef_editorial_metadata_user_dropdown_args', 'efx_editorial_metadata_user_dropdown_args' );
    
    function efx_editorial_metadata_user_dropdown_args( $args ) {
    	if( $args['name'] == '_ef_editorial_meta_user_user-assigned' ) {
    		global $current_user;
    		get_currentuserinfo();
    		if( !in_array( 'contributor', $current_user->wp_capabilities ) )
    			return $args;
    
    		$contributors = get_users( array( 'role' => 'editor' ) );
    		$contributor_ids = '';
    
    		if( empty( $contributors ) )
    			return $args;
    
    		foreach( $contributors as $user ) {
    			$contributor_ids .= $user->data->ID . ',';
    		}
    
    		$args['include'] = $contributor_ids;
    	}
    
    	return $args;
    }

    I’ll walk through it real quick.

    Here we’re registering the filter for all editorial metadata that is the type user.

    add_filter( 'ef_editorial_metadata_user_dropdown_args', 'efx_editorial_metadata_user_dropdown_args' );

    The next part is the only part you will probably have to modify before placing in functions.php:
    if( $args['name'] == '_ef_editorial_meta_user_user-assigned' )

    In this snippet we’re checking which editorial metadata it is (in the event we have multiple editorial metadata’s that are of the type “user”). I gave my editorial metadata the slug user-assigned. If you gave your editorial metadata the slug users-are-cool, then yours would probably look like:

    if( $args['name'] == '_ef_editorial_meta_user_users-are-cool' ).

    Here we’re checking if the user is a contributor:

    if( !in_array( 'contributor', $current_user->wp_capabilities ) )
        return $args;

    *This doesn’t check capabilities, it checks the user role. This shouldn’t cause any bugs, but keep an eyeball on it.

    Lastly, we’re getting all the users that are editors, and we’re going to have our dropdown just show those:

    foreach( $contributors as $user ) {
        $contributor_ids .= $user->data->ID . ',';
    }
    $args['include'] = $contributor_ids;

    Hopefully this works! Definitely reply back here if you need any help!

    Strange. What sort of custom statuses do you have right now? Have you modified them in any way (maybe some don’t have a description, etc)? Just curious since it seems to be an issue with the custom status functionality.

    Hey,
    So the above issue (the one not related to core) should be fixed by the following commit: . If you can, feel free to download from GitHub and test it out.

    Thanks,
    CJ

    Heh, no on the strong tags. Meant to use those for clarification, guess they don’t show up correctly in code segments. I’ll try and mess around with it a bit more, but being a premium theme there’s not much I can do in terms of testing. Sorry bout that. If you figure it before I do, definitely post the solution back here. I’m curious about what the problem would be.

    Hrm, premium themes make it a little tougher to debug.

    When you pasted the above code into your functions.php, did you change book to whatever post type you use?

    So the above block of code (the only one you need to paste in) would look more like the following:

    add_filter( 'ef_story_budget_posts_query_args', 'story_budget_custom_post_type_filter' );
    
    function story_budget_custom_post_type_filter( $args ) {
    	$args['post_type'] = array(
    		'post',
    		'page',
    		'<strong>os_news</strong>'
    	);
    
    	return $args;
    }

    Was that how you pasted it in to functions.php?

    Odd. What other plugins do you have installed (other than WordPress SEO), and what sort of theme are you using?

    Interesting, what theme are you currently using (and what are the slugs of the custom post types you’re using)? Might be able to rewrite the above to work for it.

Viewing 15 replies - 121 through 135 (of 193 total)