It looks like a great hack but I'm still to afraid to install it.

it is a great hack.

just a few more tweaks, and its a winner!

I wholeheartedly agree!!!!

And Eikinskjaldi is really sticking with making it work! Thanks.

I've already said that it will display in the "last post" column in the forumbit on both forumhome and forumdisplay because hiding those was not something even the original did.

However, as far as placing all the threadbits into forumdisplay, private threads that one doesn't have access to will not display. I'm working on this, so that the hack can really be complete and surpass the original, but I also have other stuff going :)

that's cool. i don't mind that it displays. the problem is the preview. is there a way to just shut the preview off, so that the message preview does not display; i wouldn't care that the thread title displays, just kill the preview on the private messages?

thanks!

Can you possibly PM me a link so I can see this because I can't seem to get the same erro you are recieving. On my forum home it shows the forums last post stuff, but doesnt give any data, in forumdisplay when you view that forum a user who cant see a private thread shouldnt be able to know it exists, let alone hover there mouse over for a preview. This might be an error with the hiding code if this is going on.

ok, my bad. it only says 'go to first unread post in [thread name]' when you hover over it.

so, the security permissions are working well. the only way people know a thread exists (and who is posting in it), is via the known VBcpms and forumdisplay routes, as described above.

will be using this, but can't wait for it to be complete when the above is tweaked!

thanks!

-d

how about this... in forumdisplay, suppose one could modify the code to display the author as private instead of the authorname. that would solve the problem temporarily.

Well that was an idea I had, to Automatically change thread name and posted to 'Private' but I just don't think it would look good on the forum in general and so I am working on a work around.

not workarounds!!! :nervous:

workarounds always seem to bite you in the long run.