Dirty Bill

With no word from the Dev, reverting is the only option.

Ok, have tried to work on this one for awhile – the capabilities rules in the advanced tab do not appear to work at all. According to the examples and documentation I can find, this:

[ Moderator Note: Please post code or markup snippets between backticks or use the code button. ]

publish_posts=publish_weather_entries&edit_posts=edit_weather_entries&edit_others_posts=edit_others_weather_entries&edit_post=edit_weather_entry&delete_post=delete_weather_entry

Should yield a custom post type that has a granular permission that I can assign with User Roll Editor. None of the capabilities show up. I’ve used URE (User Roll Editor) with other plugins, custom plugins I’ve done, etc. – always works. This seems to indicate that the Capabilities field on the advanced tab possibly isn’t registering the entries properly.

I’m not sure, but it currently means I have to give publish capabilities for posts to writers who should NOT have that capability when what I need them to have is the permission to publish a custom post type.

deleted the tw app, began again – all fields – still getting the expired token message.

The dev site runs nothing that uses oAuth. Some custom post types components, but that’s about it. Besides, if it doesn’t work with the few components that are plugged in, there’s something wrong with your plugin. All of the ones on Dev are in use on Production without conflicts.

Could it be a problem with the new Twitter API?

Same issue. I’m running this on a development system with no other Twitter plugins, no facebook plugins. Token is invalid or expired.

Same problem. Insert a shortcode, change your mind, go to insert another, but editor comes up blank. Is this becoming abandonware?

Reposted – forgot to set the current version.

Sry – didn’t see the resolved tag. Will re-submit.

I have the same trouble. I self-host, emails from WP from contact forms, etc. all go through. Editorial responses do not go through. Even crazier, they never make it to the server. I’ve been running test and looking at the exim4 logs – contact form emails I can see functioning, no Edit Flow emails.

Now to find and revert what they did with the correct “Source Permalink” for previewing feed articles. We curate our feed and since this went away it’s a real hassle.

Was simple enough. Heres what I did in case it helps:

First I deleted the few existing wp_postmeta records I had with this custom field in the meta_key. Then inserted.

INSERT INTO wp_postmeta (meta_id,post_id,meta_key,meta_value) select NULL,ID,'custom_field_name','custom_field_value' from wp_posts where post_type='custom_post_type' and post_status = 'publish';

Actually all I need to do is update the value in the existing records for the newly required fields…(all!). Good idea tho, I’ll try updating the db directly.

While we’re on feature suggestions – the ability to extract a single type definition (and it’s fields) to move to another existing system and ADD it in instead of replacing would be very welcome.

As would an add-on plugin that could take stripped records from an existing definition and insert them as new records into a separate installation.

bummer, the screencast link 404’s.

I have this same issue sometimes as well. It’s a terrific plugin btw – nice job getting it this far.

Was just a feature suggestion.