htz77

I write my own custom themes, built on underscores.me, and i know i didn’t have a meta-description tag in the template. I did have one in commented-out php, but i even deleted that entirely and the plugin still showed the warning. Eventually i just clicked the “fix it” button in the warning, and that worked — but i didn’t like that idea since i didn’t (and still don’t) know exactly how the plugin was going to “fix” a problem that doesn’t actually exist.

Same. My theme does NOT have a meta-description, but this plugin keeps throwing this warning incorrectly.

so what happened?

Why did you rate this 5 stars, if it broke your site?

What are the advantages of SuperCPT over ACF, in regards to Custom Fields? I love ACF – it’s my go-to Custom Fields approach. And as you said, it has image fields.

You can “map” your wp / members-plugin roles, to those used by bbPress. I have a custom role (created with Members plugin) called Student. I mapped this role to the “Participant” role in bbPress.

/**
 * FORUM - Role map
 * bbPress has its own internal ("dynamic") Roles, so we map our real wp roles to bbPress.
 */
add_filter('bbp_get_user_role_map','my_bbPress_role_map');
function my_bbPress_role_map($role_map){
	$role_map['student'] = bbp_get_participant_role();
	return $role_map;
}

Refer to https://bbpress.org/forums/topic/fix-for-users-of-s2member-and-bbpress-2-2/#post-120479

It may not be very relevant to you, but the context in which I encountered this issue of “hidden” capabilities was while troubleshooting problems resulting from a recent update of bbPress (a forum plugin from automattic). In researching it, I found some info about how WP handles Roles that I never knew, and it pointed my thinking in the right direction.
https://bbpress.org/forums/topic/roles-and-capabilities-in-bbpress-2-2/

Did you ever find an answer to this?

Did you ever find an answer to this?

@raam Dev – i’m trying out your fork for the CPT.. very nice work! Thank you for sharing it.

The issue i’m having is that my CPT has a different taxonomy than the standard Categories and Tags taxonomies used for Posts — and used by Postie, Any thoughts on how to connect Postie to a different Taxonomy (specifically called “portfolio_categories”, in my case). Thanks!

Hi Zack. Just wondering if this was addressed in the 3.3 / 3.3.1 releases? I didn’t notice it in the changelog.

Redirect does not work. When a user tries to view a page without permission, he gets the WP 404 message, instead of being properly redirected based on the settings in UAM.

Bummer, time to find a different plugin.

For me, users with permission to see a restricted page can see it correctly.

But users who do NOT have permission to see a restricted page, get the default WordPress 404 page (“This is somewhat embarrassing, isn’t it?..”) instead of being redirected based on the settings in UAM.

Yes, the fields/columns displayed on a front-end Directory should be controlled separately from those on the backend admin Entries list. They are different views in different environments for different users — we need to be able to control them differently. This seems like a pretty big flaw in the plugin.

@tmuka — Thanks, that basically worked for me. I just added that JS to my header.php file, and changed the “$” to “jQuery”, so it became

jQuery(document).ready(function(){
	jQuery('.entryback a').attr('href',function(i,href){
		return href.slice(0,href.indexOf("/entry"));
	});
});