Scott Bressler

Support for custom post types is now available in Edit Flow v0.6.1: https://www.editflow.org/2011/01/10/v0-6-1-custom-post-type-support-and-minor-improvements/. Check it out and let us know how it goes.

Hi Ganesh,

The ‘Pending Approval’ status is built into WordPress and allows contributors to write posts but not publish them. Then, an editor or above can publish those posts. This is something limited by Roles and Capabilities in WordPress, not directly by Edit Flow. See here for more: https://codex.www.ads-software.com/Roles_and_Capabilities.

If you think that the issue you are encountering is directly related to Edit Flow, please explain the exact steps to reproduce the problem you are encountering so that we can further assist you.

Thanks,
Scott

Hi, thanks for your interest in Media Credit. So that I can investigate further, can you please list which version of WordPress as well as which version of Media Credit you were using? Also, were you using any other media-related plugins? How did you install the plugin, and does this error output appear on every page or solely when you try to active the plugin?

Thanks,
Scott

Thanks for the request! We have already added support for pages for editorial metadata (see here) and will work on support for CPTs in our next major release.

Hi David,

Thanks for your feedback and feature request. The difference in display is because the editorial metadata CSS is only loaded on the ‘post’ page.

We’ve already worked page support into Edit Flow for the next version (likely v0.6.1). If you can, hang tight for our official release, or take a look at this change to see the other changes needed to add support for pages to editorial metadata. You can download the latest here.

If you do test the latest, please let us know how it goes and/or if you find any issues with page support.

Thanks!

-Scott

This will be fixed in the next release of Edit Flow.

There are currently a few issues with the calendar, which we are refactoring in a coming release. Sorry for the current bugs, but we’ll be sure to squash them soon!

For future reference, in version 0.5.1 we added the ability to disable the calendar entirely in the Edit Flow settings. You can also filter the roles that can access the calendar by filtering ‘ef_view_calendar_cap’ in your theme’s functions.php file.

If you need help with this, feel free to ask and I’d be happy to whip up an example of filtering the roles.

Hi ThePLD,

It looks like the empty paragraph happens regardless of alignment or location in the post of the image. It happens when there is text immediately surrounding the media credit shortcode. Try putting the media in its own paragraph (i.e. separated by two paragraphs above and below) and let me know if you still see the extra paragraph tags. Hopefully this will serve as a temporary fix, and I’ll look into ways of avoiding this totally going forward.

Thanks!

-Scott

Are you sure you are running PHP 5? This type of error occurs with servers running PHP 4.

Ih you wouldn’t mind mucking with the code a tiny bit, try changing the lines around 246 to:

$default_status = $this->ef_get_default_custom_status();
$defaults = array(
		'slug' => $default_status->slug
);

This should fix your issues, regardless of the version of PHP you are using.

Also, please start a new thread if you have any further issues, as this thread is about i8ln.

Thank you,
Scott

This happened because rewrites are turned on for the custom taxonomies that AD is registering (and I assume because the taxonomies are being registered before the ‘init’ action is called). At the least, adding ‘rewrite’ => false to your register_taxonomy args should fix this.

Hi Chip,

I’m sorry to hear that you’re having trouble with Edit Flow.

Are you running PHP 5? You can call phpinfo() in any PHP page to find out the details of the server. Let me know and I will try to continue troubleshooting.

Thanks,
Scott

Cool, thanks for letting us know! My head was exploding a bit trying to get past the diff to style.css… ??

Thanks for all your feedback, Andrew! So I’ve concluded along with Mo who originally coded the settings page that the settings page in EF needs a good bit of work. The settings should be combined into one option field and there should be some sanitization. I already fully leverage the Settings API in my Media Credit plugin, but EF needs some similar refactoring. Thanks for the nudge.

We’ve decided for this new capability not to offer any modification to the default roles to which we add the cap. I added a filter for which capability is actually checked against to view the calendar, but the only UI option we’ll offer is turning on/off the calendar. EF will likely offer many more cap-specific features in the future, at which point we may re-evaluate, but for now we’re just going to recommend installing a role plugin rather than trying to implement rudimentary role management.

Thanks again for all your help!

Thanks for the head’s up about the checked method. I’ve used selected before, but forgot about it for this. Do I need to escape anything here? (Clearly I haven’t done too many forms.) I’m just showing one 6 checkboxes, one of which is based on an option (calendar_enabled) and the other 5 of which are based on capabilities. What could/should be escaped?

Since the role-related checkboxes need to add/remove the capability from those roles, I’m not sure how I can piggyback, particularly given the haphazard usage of the Settings API for this page. Here’s the code (without any of this new stuff). I tried adding a validation method on line 143, but the data coming into there wasn’t an associative array, I assume because of the naming of the inputs in the form, and/or the half-baked use of the Settings API.

So do I have to use nonces and load-$pagenow? If so, can you explain a bit more how I’d do that? I’ve used $pagenow to check which page I was on before, but never hooked into that filter.

Thanks!

-Scott