[Mike]

Not that I’m aware of – I checked the installed plugin list – didn’t see anything that would do page caching

[Mike]

With the upgrade, I can confirm the problem is fixed. Errors are now reported to the user as would be expected.

Thanks for all your help!
Mike

[Mike]

Started again with a copy of my current site – Here’s what I did

1. Installed & Activated Twenty Nineteen Theme

2. Deactivated all plugins except Simple Membership (I don’t use any caching plugin)

3. Registration Test – form does not report any error but does reposition focus on the field that is in error

4. Purged cache using the WordPress Admin Toolbar – refreshed page – repeated test – same result

5. Purged FireFox browser cache – shutdown & restarted browser – repeated test – same result

6. Repeated using Chrome browser – purged browser cache – shutdown & restarted browser – repeated test – same result

Thanks,
Mike

[Mike]

Hi,

Finally got power back!

As you requested, I installed and activated the Twenty Nineteen theme

Still get the same result – form does not report any error but does reposition focus on the field that is in error.

So it doesn’t seem related to the theme I’m using.

Did see something interesting though that may be a clue. I tried to cut & paste the filled in form into this email (which didn’t really work – didn’t show entered data), But, this is what I did get:

Members Only Registration
Username
* Invalid Username
Usernames can only contain: letters, numbers and .-_*@
Email
Password
* Password must contain at least:
– a digit
– an uppercase letter
– a lowercase letter
* Minimum 8 characters required
Repeat Password
First Name
Last Name
Membership Level Dues Paying Member 2021
I accept the Terms and Conditions
I agree to the Privacy Policy

So, it appears it realizes what the issue with the fields are but somehow the error messages are not getting shown to the user.

Any ideas?

Thanks,
Mike

[Mike]

Hi,

I’m not using the Woocommerce simple membership plugin. In fact, the way we use Simple Membership, there is no connection between memberships and making payments.

I do collect dues via WooCommerce separately (as well as from mailed in apps & hardcopy forms filled out at our library). All updates to the membership access database & levels is applied manually by an administrator sending registration instructions and manually applying renewals, etc.

To state another way, we only use Simple Membership to control access to members only content but not to collect and keep track of dues payments.

Hope that makes sense.

I’ll try a different theme but it may be a few days – we are having an ice storm and I’ve no power at home since 6 pm New Years Day – still thousands without (including me). I drove into town and stopped by a library to try to answer to some quick email but wouldn’t want to do all the other testing using a new theme from there.

Thanks,
Mike

[Mike]

I have the same issue. But, besides not reporting spaces in username, the form doesn’t appear to report any kind of error such as a no password entered, etc.

The form will reposition focus to whatever field is in error but no message is displayed.

After some experimenting, I found:

I disabled all plugins except Simple Membership – trying to go to the form, I got There has been a critical error on this website.

I next enabled the WooCommerce plugin – form now appears but still reports no errors.

Sp. there seems to be a conflict between Simple Membership & WooCommerce – What’s my next move?

[Mike]

I was just trying to explain what I was attempting to do – not a criticism.

I really have no problem with your concept – I just didn’t fully understand how it worked. Although it would be nice to force the picking of a membership level so it would not be possible to use it incorrectly (like I did)

It’s a great plugin – I just didn’t fully understand the ramifications of the member levels selection.

Now that I understand, I will try to avoid the situation.

Thanks for all your help,
Mike

[Mike]

Hi,

My Original Understanding

When a protected post is displayed, I thought that any user trying to access that post could only get one of two results:

1. A post displaying the restricted post message text which consists of the header and the restricted post message

or

2. The post is displayed normally consisting of the header and normal post content.

What is Actually Happening

However, if a member is logged in with a different membership level than checked in the post protection setting there’s a third possibilty – post is displayed with only the Header with no content at all

In other words, the user doesn’t get the normal content or a restricted post message – which would be totally confusing to the user even though your plugin treats it as a perfectly acceptable outcome.

I would have expected such a user should have received the restricted post message text (since the restricted content is not being displayed).

In my application, I only care whether you are logged in (don’t care about the level) so I can personally live with it by insuring a level is always checked.

No Membership Level Selected Case

As I said, in my case, I only need to restrict content based on whether the user is logged in – I don’t really care about what level. I only use levels to determine access expiration.

So, my assumption was markinng the post “protect this content” was all I had to do. I expected If you weren’t logged in and tried to access the post, you would receive the restricted post message. But, actually, I just get the post’s header – no content and no restricted content message.

But, if I’m interpreting you correctly, you are saying to get the effect I want, I must not just protect the content but also must mark all membership levels individually to allow access. Which means every time I add a new level, I have to go back to all my content and select the new level. Which I probably can do using the bulk update feature (if I don’t forget it is necessary).

However, this is very confusing – it basically says marking “protect this content” without checking a membership level is an error – if so, I would think you need to require at least one membership level be selected with an appropriate error message.

Or, for my case, it would be nice to have an “all levels” box in the Membership Levels with access list.

Thanks for your patience.

[Mike]

As you requested, I used 2 different browsers – one for the development and one as a normal nonadministrator user.

I created a test post – before any protetion, it displayed:

This is a Test Post

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud etc.

where “This is a Test Post” is a h1 header and Lorem, etc. is normal paragraph <p>

Next, as you requested, I protected it but did not select any membership levels. When I tried to access it w/o logging in, I got the normal must be a member page – which is what I wanted:

This is a Test Post

You must be a TCGHS member to view this content!

If you are a TCGHS member, please login.

Not yet a Member? Consider joining us!

Which is what I would of expected. Next, I logged in as a non-adminstrator user, I get:

This is a Test Post

but no content is shown. which seems odd to me – it showed me just the header – I would expect it to at show the entire page (preferred) or at least still show the “you must be a member” warning.

Out of curiosity, I went back and selected a membership level in the post but NOT the level of the logged in user. Received the same result – heading but no content:

This is a Test Post

I’m sure I would have expected the “you must be a member” display on that one!

Finally, I set the post to my user’s membership level and got:

This is a Test Post

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud etc.

which I think is correct.

So, in summary, I think it works correctly when the post is not protected or is protected with the logged in user’s membership level.

But, it seems incorrect to me for when it’s protected with no membership levels or with only membership levels different from the logged in user.

[Mike]

Thanks!

[Mike]

Bulk protection – question about Step 2 – General Protection – documentation says “This will protect all the posts (you selected) from anyone”

Does that mean that if I enable general protection (without any specific membership levels in Step 3) that literally ABSOLUTELY NO ONE can access the post – whether they are logged in or not?

Or, does it mean that ONLY LOGGED IN users can access it? No matter what membership level they are?

Sorry to seem so dense

Mike

[Mike]

Answers my question but for clarification –

If I would add a new level in the future, I have to go back to all the protected posts & pages and check the new level?

Or, is there some way to specify protection of a post for all membership levels – including any new ones added in the future?

Thanks for your help!

[Mike]

Please hold off looking into this – it may be an issue with some custom function code that was added. I’ll get back to you again if I find that is not the cause.

Thanks,
Mike

[Mike]

Not using the Form Builder.

I simply want to edit the wording.

Thanks,
Mike

[Mike]

It was there for me – any chance you haven’t applied most recent updates?

Mike

[Author]

Posts