Rob Roy

Looks like it’s a conflict between Edit Flow and WordPress SEO, most recent versions of everything.

Disabling and reenabling caused the error when WSEO was turned back on – probably the Permalinks/Strip Category Setting but that’s just a guess.

Some more information:

The permalink section works fine when the story gets saved to a standard WordPress status (draft), but it clears and breaks when it’s saved to an Edit Flow created status.

It still does not explain the reason to require it to become part of Jetpack and to connect your site to wordpress.com’s services in order to continue using it.

Nevermind – it seems to be an issue with After the Deadline.

I believe the Subscribe button is for the article authors, not facebook pages, and links to someone’s personal facebook timeline, not a Page timeline.

It’s basically the subscribe button when you go to a stranger’s profile and Subscribe to their public updates rather than friending them.

Have you even installed the plugin? 90% of Jetpack’s plugins CAN’T be deactivated (as stated in the second sentence in the post you’re replying to). They’re just there.

If it’s so important to have “pretty math”, build it into WordPress.

Are you planning on fixing this issue? We will not be purchasing the plugin if it is coded incorrectly and causes conflicts with other paid plugins we use.

It’s ridiculous and only serves to tie you to Automattic’s crap. The only true purpose I can find is that it allows them to use Jetpack to track your site’s traffic. 90% of JP is bloatware full of shit you can’t disable and don’t need. Lets go through them:

WordPress Stats: It’s powered by Quantcast, so it isn’t something that WP developed on their own. It’s just a limited skinning of data you can already get by adding Quantcast’s tracking code to your site.

Comments: WordPress already has built-in commenting, why the need for a secondary system?

Subscriptions: Not necessary for the vast majority of people or sites. You want people to visit your site, don’t you?

Contact Form: Most themes include a contact form template and there are plenty of plugins out there that don’t require you to log into someone else’s site to use them.

Sharing: Most themes include social media and there are tons of plugins out there that don’t require you to log into someone else’s site to use them. BTW, isn’t Enhanced Distribution (below) the same thing as Sharing?

Gravatar Hovercard: One of the most useless pieces of shit on the planet and virtually impossible to remove from WordPress. I have a profile photo for virtually every social network, why do I need to create yet another one on another site that only works on other WordPress sites? 90% of readers don’t have gravatar accounts, so the fugly icon is used instead. Thanks Automattic.

Shortcode Embeds: WordPress and themes already does this.

WP.me url shortner: Most social media sharing plugins already do this (and wordpress has a built-in shortner already). Why do we need this?

Beautiful Math: Really? To whom is this a need?

Extra sidebar widgets: If this is so important, why not build it directly into the next version of wordpress? There’s also already plugins that do this.

Enhanced Distro: Sharing plugins do this. WordPress SEO does this. BTW, isn’t Sharing (above) the same thing as enhanced distribution?

Custom CSS: If someone’s changing their theme’s css, do they really need a plugin to allow them to do it? If they know how to code CSS, they’re doing it in a child theme or directly into the theme using ftp.

There are several threads on here that address this (non)issue with the plugin.

In the Titles & Metas, the “Force rewrite titles” is probably checked and your theme already handles page titles, so the plugin is duplicating.

Just uncheck the box and save, should work fine.

The best (and sometimes only) way to figure out what plugin is disabling all of your plugins, enable facebook, then re-add each plugin one by one, testing with the facebook debugging tool each time. Once they’ve been reactivated and show to not be the source of the problem, leave it on.

Eventually you’ll come to the plugin causing the conflict.

I looked really closely at the photos and found where it is being applied but for some reason being squashed into a 1px vertical line?

Here it is at 20% default setting, bottom right-hand corner: https://chicagophoenix.com/wp-content/blogs.dir/2/wppa/19.jpg

Here it is at 100% intensity, bottom right-hand corner:
https://chicagophoenix.com/wp-content/blogs.dir/2/wppa/18.jpg

Is your admin email address also included in a user group?

EF is more for organizational structuring than access allowances, it took me a bit to figure that out. The built-in user roles are for access (allow to submit, allow to edit, etc) as opposed to EF user groups (my sports writers, my photographers, etc).

There are some instances where you don’t want them synchronized (a writer who’s only freelance, for instance). You want him in the same user group as your other topical writers but not necessarily the same access to the WordPress admin as one of your staff writers.

Your contributors will always be able to edit their stories if you initially give them the ability to do so. It isn’t a plugin issue, it is a WordPress function.

WordPress roles & capabilities should not be confused with Edit Flow user groups.

WordPress R&C:

Super Admin – Someone with access to the blog network administration features controlling the entire network (See Create a Network).
Administrator – Somebody who has access to all the administration features
Editor – Somebody who can publish and manage posts and pages as well as manage other users’ posts, etc.
Author – Somebody who can publish and manage their own posts
Contributor – Somebody who can write and manage their posts but not publish them
Subscriber – Somebody who can only manage their profile

Giving someone a specific user group in EF does not change their WordPress R&C.

Yes, in the plugin settings under category tell it to only pull stories that match categories on the aggregator site.