Originally Posted by Zurual (Post 1605628)

There's something iffy with the Display Order and Force Read order. For instance: If I create a thread I want visitors to read and Force Read it, marking it as #2 on the force read order, it inherits the usergroups from the Force read #1 thread..even though they are two seperate entities in the Force Read thread admin area. Basically, in a nutshell, Add two threads via the adminCP to Force Read, they inherit the usergroup listing of those threads created before it with force read.

Something isn't right. Using Vbulletin 3.7.0. Screenshots below confirm I've only chosen the Warhammer Rank to be forced to read this thread. But if you look at the other screenshot, you'll see it also is forcing visitors and Users waiting on Email Conf. to view it as well because the other, completely separate entry, forces those two ranks to read another thread. I'm a bit of a noob so if it's an easy fix, that's fine. But I've wracked my brain on why it would be doing this. My only conclusion is it's something to do with the Display Order (oddly).

Originally Posted by SteveKerrison (Post 1615174)

I'm finding this too.

I go to add a new thread, leave the display order at its default (previous + 10), set the thread ID, usergroups and forum coverage, and when I create, it has inherited the groups of those above it.

I wonder what the issue is.

Originally Posted by Abe1 (Post 1457690)

Zip file updated (again). admincp/force_read_thread.php file updated to fix error of not adding the force read.

Originally Posted by Abe1 (Post 1457693)

Fixed. Search "force read" and removed the edit around it.

Originally Posted by mc0676 (Post 1457698)

OK a find it sorry:

Is only this ?

<!-- Start Abe1 Force Users to Read a Thread -->
<div><label for="ao_mfr"><input type="radio" name="do" id="ao_mfr" value="forceread" />$vbphrase[manage_force_thread_reading]</label></div>
<!-- End Abe1 Force Users to Read a Thread -->