[websydaisy]

You will not remove the login page — you will need to remove caching from the login page. If you are using a caching plugin of any kind, it should have a way to exclude certain pages from caching. If not, your host probably has their own caching going on and you need to contact them and ask them to not cache the login page — whatever link people go to to enter their username and password so they can access the protected content. My host was WPEngine and they took care of it. I also had them not cache my protected pages (the pages only logged-in members can access), just to be safe.

To clarify, it is not certain files, it is certain pages. Go to wherever your members log in, and copy the link from the browser address bar. Then tell your host not to cache that page. If you have a caching plugin, try disabling it, clear your cookies, and test to see if that fixes it.

[websydaisy]

Ok, they disabled their caching on the protected page and on the login page, and for now it APPEARS to be fixed. I could not reproduce it at least. Fingers crossed!

[websydaisy]

Ok, I will contact them now — but FWIW, I have kept caching turned off on this site because I have seen it cause issues on membership sites before.

[websydaisy]

I had typed out a long reply this morning and submitted it and now I see it is not here any more! ARGH. In brief, I already did all troubleshooting steps.

Everything worked fine on my staging site with same theme, plugins, and settings.

I would be happy to provide a login. Client is getting upset. Please help!

[websydaisy]

I have already done troubleshooting steps.

What seems to happen is the first time you login, it works just fine. After logging out and logging back in, then it does not redirect — it stays on the login page and gives the member’s info like this:

Logged in as
websycase
Account Status
Active
Membership
Caseworkers
Account Expiry
Never

And if you then try to go to the protected page, it goes there, but says you need to login instead of showing the content.

SO I created a whole new member, and it worked correctly when I logged in. Then I try to log out, and it takes me to the home page — which I figured out means it did NOT log me out. I can go back to the protected page without logging in. Other times it would log me out. And then sometimes it would work correctly. Others it would revert to the old broken behavior. Sometimes the only way I could log out was to clear my cookies.

Sometimes I would get logged out and then try to log in as a different member. It would then give me the membership details for the original member — not the one I just logged in as. I even checked to make sure I was really logged out. It just keeps saying I am the old member. I have to clear history and cookies for it to actually login as the new member — at which point it takes me to the correct page and shows me the protected content.

It is erratic and I can’t find the rhyme or reason to it.

Note that on my staging site: [http://bearesources.staging.wpengine.com/] same theme, same plugins, same settings, it all works. I pushed the live site to staging so I could see if I could reproduce it and try disabling plugins there. But I can’t make it not work on staging. Only on the live site. [http://bearesourcehouston.org/]

I have debugging on but the debug file is always empty.

[websydaisy]

Yep, in Membership Levels:

https://www.dropbox.com/s/0ton9onwm1k5sie/Screenshot%202016-10-13%2023.49.34.png?dl=0

[websydaisy]

I turned off content protection for the page, saved it, and then turned it back on and now it is working.

[websydaisy]

Yes, that’s where I got the php I used to see if someone is logged in. And I see things telling me how to get the user’s membership level, but I don’t know how to make my conditional statement say IF they are in Level 2, for example, then show this. That does not appear to be addressed.

[websydaisy]

I put it in my page template where I call the custom fields. Like this:

<?php if(SwpmMemberUtils::is_member_logged_in()) { ?>
<?php the_field(‘my_custom_field’); ?>
<?php } ?>

[websydaisy]

Thanks! So I am able to get partway there by putting this around the section that contains my custom fields:

<?php if(SwpmMemberUtils::is_member_logged_in()) { ?>
<?php } ?>

But since I have two different membership levels, I need to have it look to also make sure they are in a certain level. I am not great at figuring out php on my own — what can I add to this to have them also look to make sure they are in a certain level to display that content?

[websydaisy]

Yeah, this does not do anything different for me than before. When I create my custom fields, there was already a place to to click the buttons to protect them — but on save, they go right back to “No, Do not protect this content.” being selected.

I need to protect Custom Fields, not Custom Post Types.

Looks like this question has come up before: https://simple-membership-plugin.com/forums/topic/protecting-advanced-custom-fields/

If there is no way to protect custom fields, I will have to abandon this and look for a different plugin. Unfortunately I already paid $40 for the Form Builder Add-on.

A LOT of people use Advanced Custom Fields. Surely there must be some way to make this work?

[websydaisy]

This appears to be for Custom Post Types, not for Custom Fields?

[Author]

Posts