natebot

I’ve made a suggestion in the related Github issue.
https://github.com/Automattic/Edit-Flow/issues/230#issuecomment-73563996

The short version is, since you have DB access, you can replace any custom status slugs in wp_posts.status with a core status of your choice.

I experienced this too.

The template tags the_author() and get_the_author() are both filtered by CAP when the filter coauthors_auto_apply_template_tags returns true. Thus these functions will output co-authors. Specifically, this happens in the filter function CoAuthors_Template_Filters->filter_the_author() and therefore when the_author() is called outside of the loop it will express any co-authors in the first post in the loop.

Instead of using the_author() in my header of my author.php template, I did something like this:

echo esc_html( get_the_author_meta( 'display_name' ) );

Not sure how bulletproof a solution that might be.

My pull request is at:
https://github.com/Automattic/Edit-Flow/pull/197

It assumes that the conditional does good work and just needs to be more sensitive to changes in the title. However I don’t see the reason for having the conditional, why not just do the work to update permalink every time. Performance?

Pull request sent.

I think i found it. I need help understanding the logic though.

In fix_editable_slug() there is a check for “! empty( $post->post_name )” on line 1391 custom-status.php which prevents the slug from being updated ( because in the case above we do have a post_name but the title has changed ).

I don’t understand the need for this check. When the post is not published it should be malleable, right?

Our editors recently made this request, namely to add quickly ideas and drafts via the calendar. They are Google Calendar users to they like the idea of adding a headline to stub out future posts. I can get you in touch with our managing editor if you’d like to hear more of a use case. Also if you’ve already know what direction to go here and need development help let me know.