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

[Princeton]

attached is how the archives will look like when completed (not allowed to read)

notice there is no link?
the second image is the content page ... when someone tries to go to the page directly via the address bar -- they see nothing

[mfarmerhi]

Unless I'm mistaken

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

should be:

To disable thread previews on forums that user cannot read content do the following edits:
FIND in functions_forumdisplay.php

Great hack and exactly what I was looking for. Installed.

Only problem is in attempting to view the Archives I get this error:

Parse error: parse error, unexpected T_ELSE in /home/totalli/public_html/forum/archive/index.php on line 324

I, er... am doing this all by hand... er... on Word pad... and am having a hard time counting down 324 lines

I've double checked and don't see the error I made. Anyone (with a proper php editor) have a clue where I might look?

Thanks ahead of time.

~ Mark

[Princeton]

LOL ... yep spelling error

the error states you did an erroneous copy/paste ... the only way to fix this is to check your file

[Princeton]

small typo in archive/index.php

FIND ALL INSTANCES OF: slash_method
REPLACE WITH: SLASH_METHOD

[mfarmerhi]

I'd love this hack, but it's conflicting with the Text Message User on PM hack I already have installed.

I believe the conflict is coming in the inclues/init.php changes. Specifically the change in this hack:

Find:	'canthreadrate'     => 65536,
	'isalwaysmoderated' => 131072,
	'canseedelnotice'   => 262144
);

Replace with:
	'canthreadrate'     => 65536,
	'isalwaysmoderated' => 131072,
	'canseedelnotice'   => 262144,
// ================================================= \\
// == [ ALLOW GROUP TO READ TITLE / NOT CONTENT - GTP BEGIN ]
	'gtpcanreadcontent'	=> 524288,
// == [ 00-00-2004 - GTP END ]
// ================================================= \\
);

conflicting with the change in the includes/init.php in "txt msg on pm":

$_USEROPTIONS = array(
	'showsignatures'    => 1,
	'showavatars'       => 2,
	'showimages'        => 4,
	'coppauser'         => 8,
	'adminemail'        => 16,
	'showvcard'         => 32,
	'dstauto'           => 64,
	'dstonoff'          => 128,
	'showemail'         => 256,
	'invisible'         => 512,
	'showreputation'    => 1024,
	'receivepm'         => 2048,
	'emailonpm'         => 4096,
	'txtmsgonpm'	  => 8192,
	'hasaccessmask'     => 16384,
	//'emailnotification' => 32768, // this value is now handled by the user.autosubscribe field
	'postorder'         => 65536,
);

If I change the includes/init.php file as directed in this "text message on pm" hack, it causes *everybody* (including those with access via masks) to receive the warning generated by the "allow users to read title but not posts" hack.

Anyone have a clue why the conflict is occurring; and more importantly how I could have both hacks working without the current conflict?

[Princeton]

the bitfields above have nothing to do with each other ... your problem is elsewhere

[mfarmerhi]

Originally Posted by princeton

the bitfields above have nothing to do with each other ...

Despite the fact that both "'canthreadrate' and 'postorder' are being assigned 65536?

Either hack works fine, when I remove the other hack.

But installing both together, causes both to stop working.

~ Mark

[Princeton]

take a look at the instructions and you will see that there are not the same thing ... I don't even know why you are looking at $_USEROPTIONS

[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.

[mfarmerhi]

Originally Posted by princeton

take a look at the instructions and you will see that there are not the same thing ... I don't even know why you are looking at $_USEROPTIONS

I'm looking at them because these hacks are clearly interferring with each other; because includes/init.php is the only thing that is changed in both hacks; because those are the only 2 changes I've made to includes/init.php (your hack and the other); because as a non-php/non-mysql trained person that's the only obvious thing that I see that appear to be using the same values; and finally, because both hacks work fine with the other is uninstalled.

Regardless, I admit that my conclusions that line is the conflict MAY BE WRONG.

So... any OTHER possible place to begin with in figuring out why your hack and the other hack conflict?

~ Mark