PMPro Network Membership (permissions issue)

Hi Grace n Ease,

This is usually a WordPress error and might not necessarily be associated with PMPro/PMPro Network Addon. However, if this is an issue with PMPro/PMPro Network Addon, we’ll definitely look into it. The first question I have for you is, did you configure the PMPRO_NETWORK_MAIN_DB_PREFIX (https://github.com/strangerstudios/pmpro-network-subsite/blob/master/pmpro-network-subsite.php#L15)? This is in place, in case your db prefix is not the standard wp_.

Secondly have you configured the Network addon: https://github.com/strangerstudios/pmpro-network/blob/master/pmpro-network.php#L16-L17?

Third, are you a Network Administrator (Super Admin) on your Multisite instance? If not, you may run into the permissions error.

If you’re still having trouble after addressing the above items, let us know and we’ll ask you for more details about your setup and try to replicate on our end.

Thanks

Thanks for your reply. Sorry for the delay. I didn’t receive an email about this update to the thread. I will keep a closer look to make sure I catch it next time.

Yes, I am Network Admin (Super Admin).
I am not wanting users to be able to create their own site so the pmpro-network.php file shouldn’t be needed (from my perspective). Unless it is required. I didn’t realize it is if it is.

I do have a multisite configuration which I am the only admin for all sites. I do want the members to be members of all sites and content be restricted based on the levels created by PMPro. I have the default wp_ prefix. Could this addon be written to automatically use the prefix if not default? I thought I saw where current plugins actually automatically detect the db prefix. I didn’t even think to check to see if this one didn’t.

I have been trying to test this on a local install, but if needed I can go to a hosted site to test it. Before putting it on my live site.

Based on what you have said, I don’t understand why the addon won’t work the way it is. I am using the default db prefix for the test site.

Edit –

I am using WP 3.8.1 and I am using the current version of PMPro.

Grace,

Sorry you ran into issues. Configuring multisite setups with PMPro or in general often requires a developer to work out the kinks.

That said, I’ll try to give you a little guidance based on what you wrote here. It sounds like you want to manage membership levels at the main site and restrict content across all subsites using those levels. (If that’s not the case ignore the advice below and let us know how you want to set things up.)

What you should do is:
* Install PMPro on All Sites
* Install PMPro Subsite Helper on all Subsites (but NOT the main site)

Unless I’m missing something, those permission denied warnings are a feature of the subset helper rather than a bug. When it’s activated, we don’t want the subsite to have it’s own PMPro settings/etc. However, you should still be able to access the PMPro settings from the “main” site which doesn’t have the subsite helper activated.

Let us know if this helps.

Okay. So I had it set up correctly. That is a relief. I will check the functionality.

The issue then isn’t that it isn’t working (based on this conversation), but that the Memberships Menu is showing up in the toolbar at the top on subsites when it actually shouldn’t be there.

I do see this remove_action('admin_bar_menu', 'pmpro_admin_bar_menu'); in the pmpro-network-subsite.php file. But it isn’t removing the toolbar menu. I guess that would be the real issue.

Personally, I would like to have the option to turn off the pmpro_admin_bar_menu altogether. But for now, when it is supposed to be being removed, it isn’t.

Thanks

Hey there,

Thanks for pointing that out! This is actually a bug in the code. When removing actions, the priority that was used to add the action has to be set as well. The correct line should read:

remove_action('admin_bar_menu', 'pmpro_admin_bar_menu', 1000);

I’ve tested on my dev server and this should work with everything configured properly.

I’ll let Jason know about this bug immediately, and hope that helps!

Thanks,
Jess

Hi @jessica O,

I will remember when looking at something like this in the future. The priority must match.

Yes, it helps and it fixed the issue. Now I’m not so confused.. lol

Perfect, Thank you

I’m marking this as Resolved.. Thanks again.

Hello, I am having this problem: I can see the page page=pmpro-membershiplevels and make changes but when I go to pmpro-pagesettings, I get “You do not have sufficient permissions to access this page.”, this only happens in my dev machine W8 running wordpress with app engine lancher 1.9.6, here is the log:
INFO 2014-06-26 17:37:48,884 module.py:639] default: “GET /wp-admin/admin.php?page=pmpro-pagesettings HTTP/1.1” 500 2973
I am a local admin in my machine and logged on into wordpress as an admin.

I resolved this issue by following instructions here: https://www.ads-software.com/support/topic/unable-to-access-the-settings-page-1

The root cause seems to be that Windows was using backslashes for directory path. In wp-includes/vars.php, it has the following line:-

preg_match(‘#/wp-admin/?(.*?)$#i’, $_SERVER[‘PHP_SELF’], $self_matches);

Problem solved by adding this line:-
$_SERVER[‘PHP_SELF’] = str_replace(‘\\’, ‘/’, $_SERVER[‘PHP_SELF’]);

Just before:-
require_once(ABSPATH . ‘wp-settings.php’);

In your wp-config.php.