Allow Group to Read Titles / Not Content

Tested and working in 3.0.3 - 3.0.7

This hack will enable you to DISABLE SHOWTHREAD according to USERGROUP.This will allow all your members to view titles and topic counts found within a section. Think of it as "window shopping". Your members will be able to read all topics from the forumdisplay.php page but, will not be allowed to read it's content unless they have permission

The edits below will prevent anyone from viewing the contents of a post from within showthread, printthread, showpost, and archives.

This feature can be used on a per USERGROUP and /or per FORUM basis. You, as the admin, will have complete control.

You will need to modify:

• includes/init.php
• includes/adminfunctions_forums.php
• admincp/resources.php
• admincp/usergroup.php
• showthread.php
• archive/index.php
• printthread.php
• showpost.php
• archive.css

Add 3 new phrases.
MOD VERSION 1.05

• Fixed issues concerning the archives - eg. blank page was displayed ... now, thread links are viewable but not active (if not allowed).

MOD VERSION 1.01

• now with personal NOT ALLOWED message
• Easier to install
• now add the ability to allow users to view their own posts/threads (view below code)
• archive section changed to NOT display links to content that is not READABLE
• added a message to archive section if user cannot read content

[hr=blue]4[/hr]
Allow User To View And Post Into Their Own Threads:
If you want to allow users to view and post their own threads and have access to them ... use this code in showthread, printhread, and showpost.php:

// ================================================= \\
// == [ ALLOW GROUP TO READ TITLE / NOT CONTENT - GTP BEGIN ]
                 if (!($forumperms & GTPCANREADCONTENT)AND ($thread['postuserid'] != $bbuserinfo['userid']))
                 {
                     eval(print_standard_error('gtp_cannot_read'));
                 }
// == [ 00-00-2004 - GTP END ]
// ================================================= \\

NOTE: You may have to use "$threadinfo['postuserid]" on some of the pages.

[hr=blue]4[/hr]
Disable Thread Preview
To disable thread previews on forums that user cannot read content do the following edits:
FIND in functions/forumdisplay.php:

    // format thread preview if there is one
    if ($ignore["$thread[postuserid]"])
    {
        $thread['preview'] = '';
    }
    else if (isset($thread['preview']) AND $vboptions['threadpreview'] > 0)
    {
        $thread['preview'] = strip_quotes($thread['preview']);
        $thread['preview'] = htmlspecialchars_uni(fetch_trimmed_title(strip_bbcode($thread['preview'], false, true), $vboptions['threadpreview']));
    }

REPLACE IT WITH:

// ================================================= \\
// == [ ALLOW GROUP TO READ TITLE / NOT CONTENT - GTP BEGIN ]
    $forumperms = fetch_permissions($foruminfo['forumid']);
    // format thread preview if there is one
    if ($ignore["$thread[postuserid]"] OR !($forumperms & GTPCANREADCONTENT))
    {
        $thread['preview'] = '';
    }
    else if (isset($thread['preview']) AND $vboptions['threadpreview'] > 0)
    {
        $thread['preview'] = strip_quotes($thread['preview']);
        $thread['preview'] = htmlspecialchars_uni(fetch_trimmed_title(strip_bbcode($thread['preview'], false, true), $vboptions['threadpreview']));
    }
// == [ 00-00-2004 - GTP END ]
// ================================================= \\

[hr=blue]4[/hr]
Example Of How Hack Works:
I have a forum with (sub-forums) ... however, one of the sub-forums is private (for PREMIUM members only). Here's how the settings would look like.

In USERGROUP MANAGER (this is a global setting) set "Group can read content?:
UNREGISTERED - YES
REGISTERED - YES
PREMIUM - YES

The global setting will be transferred to all forums; but, we have a sub-forum that is only for PREMIUM MEMBERS so...

In FORUM PERMISSIONS MANAGER set private forum to:
UNREGISTERED - NO
REGISTERED - NO
PREMIUM - YES

[mfarmerhi]

Originally Posted by Lionel

I don't think he is following instructions. He is doing a search for : 65536 and is placing the code right after that. all 65536 are not the same.

Hi Lionel,

Thanks for suggesting a possible problem.

No. I did not "search for 65536" and place the code after that.

I performed the hack as instructed and had it working fine until I installed the other hack.

I HAVE only posted the parts of each hack that *appeared* to me to be conflicting, but you can see both of the hacks, in full, through the links I provided in my first post, to compare the full codes for other possible conflicts ('cause I sure don't know where or how they're conflicting...).

~ Mark

[mfarmerhi]

Okay... I'm thinking the problem is coming from "text on pm" redefining "hasaccessmask"

Prior to installing that hack, 'hasaccessmask' reads:

'hasaccessmask'     => 8192,

That hack redefines it:

'hasaccessmask'     => 16384,

If I'm not mistaken, "Allow groups to view titles" also uses the access masks feature, and I'm guessing that redefining hasaccessmask is causing the conflict.

That hack is using 8192 for a new permission: 'txtmsgonpm'. Can 'txtmsgonpm' be redefined to the 16384 or some other number, so that 'hassaccessmask' can remain 8192? Alternatively, is there a way to allow 'hasaccessmask' to be redefined and still work for this hack?

~ Mark

[mfarmerhi]

Alright. The more I explore, the more sure I am of the conclusion I came to in my last post above.

In the end, I've left both hacks installed.

Because the "Text on PM" redefines the bitfield for 'hasaccessmask', if you choose to use both hacks ("Text on PM" and "Allow Groups to read"); AND you've first installed the "Allow Groups" hack FIRST, THEN installed "Text on PM", you'll need to go back to all the users you've allowed to read the thread contents (in the forum(s) you've selected as your "Allow Groups to read" forum(s)) and:

1) Change each user first to "no" or "default"; THEN
2) Change that same user BACK to "yes"

YOU HAVE TO DO THIS EVEN THOUGH YOUR USER ACCESS MASKS WILL STILL SHOW THOSE USERS AS HAVING PERMISSION TO READ CONTENTS

Although I am not sure how it happens, it's my belief that by redefining 'hasaccessmask' with a new bitfield, it causes vB to "forget" whom could and could not read thread contents, requiring you to again re-define them.

Said another way, the variable that used to define who could read contents, has been changed. To restore that permission you need to again define those users.

Again, this *should* only apply to users who have FIRST installed the "allow groups to read" hack, THEN installed the "text on pm" hack.

~ Mark

[Princeton]

Did you try clearing all cookies / closing session / logging out / close browser before you did all the above? It could have worked; but, then again--maybe not. Anyway, you got the hacks working and that was the ultimate goal.

thanks for sharing your find...

[Marco van Herwaarden]

Am i missing something? What does a phonenumber got to do with this hack?

[jellybaby]

Does this work with 3.0.8?

[Princeton]

yea, it should work ...

in case you are not aware--this option is now built into vb 3.5

[jellybaby]

Thanks for the reply. I have 3.0.8 and I have installed it and I can see the options in admin and have set them but guests can still view!

[Princeton]

Have you set and saved each usergroup permissions?
If not, you must 'save' each usergroup permissions setting for it to work.

If you done the above take a closer look at the instructions -- you may have made an error while copying and pasting.

[jellybaby]

By save each usergroup permission do you mean select the usergroup chose yes or no and save? Sorry I am new at this