I’m building a private group journal that will be shared between my wife and her sisters. I’m adding the members-only code to each page of the journal. I’ve tried adding the if-then code shown in the manual to the top of the pages, just beneath the php include line. When I’m logged in, I see the page and the correct example text from the manual appears along the top of the page above my content. When I’m logged out, it shows the correct “logged-out” text along the top of the page, but I still see the full page of the journal.

Since the code seems to be triggering the correct text, I’m guessing I’m screwing something up. Any idea why the pages still show with the members-only code on the page?

Are you putting the “restricted” content inside the tags where the “logged in” text is?  What you’re doing is wrapping your content with those tags.

I was just adding the tag at the top, Chris. I’ll give this another shot. Thanks!

Hi Chris

I’d like to add a wrinkle to the above question. I’m running a public and a private blog. I can get the permissions tags (for members only) working fine when I login on the public page and then go “direct” (ie., in Safari - keying in the private page’s URL) to the private page. It will display the private info.

However, when I try to go from my login page (after the “you are logged in” messages page) to a page created outside of pmachine using a link statement in the messages page, the page where I should have unrestricted access now says I need to login.

I’ve included the*** <?php include(“pm_inc.php”); ?>*** statement at the top (and also added the permissions tags) to this restricted page (that is in the same directory as the other pmachine generated pages), this new page doesn’t recognize the login and tells me I’m restricted.

So—after that convoluted description—if one creates php pages outside of pmachine, adds the “include” statement at the top, and restrictions tags (if one wants) and places them in the same directory as the pmachine pages on their server, will those pages interact properly with the pmachine generated pages. - ie., properly show that one is logged in or allow one access to the full page if they have the proper admin. privileges, etc.? (My pblocks, etc. work fine on these pages but the access privileges don’t. Even though I logged in earlier, the login information seems to be ignored or reset when I get to a ‘non-pmachine page’).

Is there something I could be doing or adding or missing that is causing this problem?

> will those pages interact properly with the pmachine generated pages

Yes, they should.

The first thing I would suggest is to make sure you have the $cookie_domain variable set in your “config.php” file.  i.e. set to “.yourdomain.com” with the period in front.  That’s very important since otherwise “www.example.com” and “example.com” are considered to be two different sites as far as the cookie is concerned.

So, once you have that variable set make sure you log out and remove your pMachine cookies.  Then try logging in again and see if that fixes things for you.

Providing a link to your site (and a temporary testing account username/password) so that we can observe this behavior would be useful, too.

Thanks Chris

I’ll check out your suggestion and report back.

Chris

All I can say is “OMG”. I won’t tell you how many hours I have spent going over everything on the site to try and solve the above problem. Your suggestion has solved it within 30 seconds of making the config.php alteration. Thank you Thank you. It works splendidly as I had hoped.

Now, because I’m one of those people who used to love to say to clients RTFM, is this tip in the help files somewhere? If not, should be.

Thanks again. I’ll upgrade to EE soon.

Just a quick note to say thanks for your patience and explanation for my original post here, Chris. The members-only content code works great. It escapes me why I always seem to do this stuff late at night when my brain is fried.