Sivel.net Forum

Thanks for getting back to me so quickly. I tried the development version as you suggested, but it still is not working. I tested it out on a page that is not affected by a different plugin (ex. the about page) and it works, just doesn't seem to work with pages affected by plugins like WPG2.

Here's a link to the blog. The page links are on the left. The only one that is supposed to be restricted is "Gallery".

Thanks again for looking in to this. My boss will be quite pleased once it is all worked out.

OK, I have a simple Hack that seems to work... Here's what I did...

I looked through the code in both plugins (Page Restrict and WPG2). I focused on the PR function: pr_page_restrict and noticed that's the function I needed... In the WPG2 file: "wpg2template.inc" around line 129 there is the following statement:

echo $g2data['bodyHtml'];     //Display the gallery content

So I modified the code to be the following:

if (pr_get_opt('version')) {
    echo pr_page_restrict($g2data['bodyHtml']);
}
else {
    echo $g2data['bodyHtml'];     //Display the gallery content
}

Then I modified the pr_page_restrict function in pagerestrict.php to include

<div class="pr_box" id="pr_box">

at the beginning of the output and of course

</div>

at the end of the output (this is so I could modify the stylesheet to help the display fit with my theme).

It works... Not sure if this is the best approach, but it works...

Any thoughts?

Last edited by penfil (2008-10-31 10:56:10)

@gsharp - It looks like you need to filter the output from your Profiler plugin through the PageRestrict plugin.

I haven't tested this as I have not installed the Profiler plugin... But I think this is what you need to do...

In the file: "profiler.php" (from your profiler plugin) you see the following 3 lines of code: (lines 615-617)

    echo '<div class="pfdirectory">';
    echo $output;
    echo '</div>';

These are in the function that displays the user directory. Try changing those lines to the following:

    echo '<div class="pfdirectory">';
    if (pr_get_opt('version')) {
            echo pr_page_restrict($output);    //Pass user directory through pagerestrict filter
    }
    else {
            echo $output;     //Display the user directory
    }    
    echo '</div>';

That should do the trick for what you are trying to do...

To cover some of the things you mentioned:

The profile directory page is not being replaced by the login required page even though its selected in the Page Restrict Admin.

That is because the profiler plugin is (without the hack) bypassing the pagerestrict actions. Since the page has some code in it (you can see it by opening the page in edit view in your admin panel) that calls the profiler plugin first before the pagerestrict plugin.

What's happening is that its displaying the page configured as restricted in Admin page AND the "login page" on the same page for both the online directory page and user profile page.

This happens because the profiler plugin bypasses the pagerestrict plugin for that page so the profiler content is still being displayed, then the pagerestrict plugin kicks in and recognizes that the page is restricted and posts the login form... That's why the hack is needed to filter the profiler output through the pagerestrict.

I am thinking its because of the extra "current_page_item" value"

The restriction has nothing to do with CSS and does not appear to be processed through JavaScript or by manipulating the DOM after the page is processed... So the ID, CLASS, or NAME of an element should not matter in this case.

Last edited by penfil (2008-12-01 10:19:24)

msturm wrote:

Thanks penfil!

I had the same problem as gsharp so I changed the php code as you suggested. It almost worked perfectly. It does hide the members directory but displays the PageRestrict restriction message twice separated by the page indicator <<1>> Do you think that has to do with the php code on what is now line 624-632 - see below. Thanks for you help!

    pf_directory_pagination($lastpage);
}

function pf_directory_pagination($lastpage)
{
    $page = round($_GET['page']);
    if($page < 1)
        $page = 1;
    $character = pf_directorypagi_url_char();

Hey msturm,

To answer your question, yes, essentially the issue is with that last line of the function making  a call to "pf_directory_pagination($lastpage)". I installed the profiler plug-in just because this was making me curious... Here's what I did to get it to work:

In "profiler.php" starting at line 615 to the end of the function (should be line 629) here is what I now have...

    echo '<div class="pfdirectory">';
    $show_pagination = 1;
    if (pr_get_opt('version')) {
            if (pr_page_restrict($output) == $output)
                echo $output;    // if they are the same then display the user directory else do not
            else
                $show_pagination = 0; // turn off pagination
    }
    else {
            echo $output;     //Display the user directory
    }    
    echo '</div>';
    
    if ($show_pagination == 1)
        pf_directory_pagination($lastpage);

I added some comments to help explain what is going on... It should be clear enough. Basically I added a variable called $show_pagination (bet you can't guess what that's for!) and set it to 1 (true). I change that to 0 (false) only if the results from the pr_page_restrict($output) call are different from the original $output (meaning that the PageRestrict was needed).

Also, instead of simply doing: echo pr_page_restrict($output) // which caused the double login to be displayed
I put in a conditional to catch it if the return value was different.

It's like 4:30am here so you'll have to forgive me if my writing is a bit sloppy.

I hope this is clear enough. I tested it out and it works for me.

Last edited by penfil (2008-12-14 03:36:23)

I'm having the same problem. I did try the development version, but that didn't work. Is there a work-around that doesn't involve modifying the other plugin (in my case a basic forum)? I'm concerned that an update to the other plugin will break the page restriction.

what can I do?