[2.0.20] Topic Permissions

[djdadevil]

reinstall it

Well, I did something else, I took from my backup (cause before adding any mod, I always make 1 Backup of all files before applying a new one (so with 37 Mods installed now, I got 37 different back-ups of the file's and database....)) 'functions_post.php' and applied by hand the specific section of this mod for functions_post.php. Guess What, it solved all my problems!!! EasyMod problaby f*cked it up somehow... but now done it by hand and all is solved... thanks anyway, Great Mod!!!

(...) Removed the problem wich allan had, it's not appliable anymore, solved!

Your sincerrely,

djdadevil

[allan1956]

djd

If you replace the line with the one I posted as 'it should look like this' then that will give you a correct sql statement

[djdadevil]

djd

If you replace the line with the one I posted as 'it should look like this' then that will give you a correct sql statement

H!, I already knew, didn't quite understand what was standing there in first place, but then I watched the differences, and saw that the admin part by me with easymod also was misplaced, so I fixed it manually, and all works fine (so I've edited my previous post!).... it's not a problem anymore, and it's just working fine!!!

So the error I don't have to show anymore, cause it is solved, fixed it, putted on the site, but since my database connection was lost untill a few moments ago, I couln't check it, now I did, and there are no more errors.... So all went fine, thank you all! And good luck in the future for whatever reason

Your sincerrely,

djdadevil

[allan1956]

would be nice to hear from author about validating the reported bugs

[ycl6]

MOD Updated to version 1.3.6
See first post for Download Link

[Fayo]

I have found this on your forum, Swizec, and I wonder what does it really do. Is it a solution to the problem? Or does it do something more drastic to the MOD? Pls reply.

There were some persons in this thread complaining about getting the error message "user not logged in to topic" while trying to read topics after installing this mod. Since I personally don't care about that feature, I just removed the following lines from posting.php and the problem disappeared:

Code:
if ( is_array( $userdata['log_topics'] ) )
{
if ( array_search ( $topic_id, $userdata['log_topics'] ) === FALSE )
{
message_die ( GENERAL_ERROR, $lang['not_topiclogged'] );
}
}
else
{
message_die ( GENERAL_ERROR, $lang['not_topiclogged'] );
}

[Swizec]

It appears that it simply does not complain about not being logged into the topic... which means that topic banning and topic password protection don't really work...

[PastisD]

Hi,
In this (viewforum.php):

Code: Select all

$log = ( $userdata['user_allow_tlogin'] || ( $board_config['allow_guestlogin'] && $userdata['user_id'] == ANONYMOUS ) ) ? $lang['Rules_tlog_can']: $lang['Rules_tlog_cannot'];

$lang['Rules_tlog_cannot'] and $lang['Rules_tlog_can'] are not declared in language files.

EDIT : Where is the update from 1.3.5 to 1.3.6 ? o_O

[jesus_army]

The file in the 1.3.6 zip package that is named topic_permissions_1.3.6.mod is actually topic_permissions_1.3.5.mod

Just open it and read it in a text editor and you'll find it says

## MOD Version: 1.3.5

[Swizec]

I probably just forgot to change the version number, happens a lot

[jesus_army]

The contents of the zip appear to be the same as the 1.3.5 version on your site

The revisions quoted in the mod only take us up to 1.3.5, so I did wonder

## 2005-04-17 - Version 1.3.5
## - finally got around to fixing the bug with all guest topics being passworded (or rather just the notice being shown)
## - and made the install smoother with other mods
## - in code comments made better
##

[Swizec]

*thinks*

Something must've changed...

run a diff on the files if all else fails... I'd check but I'm at work right now and can't

[ptheyser]

i'm thinking this is a problem on my end rather than your mod, but i'm getting this error,



can this be fixed by changing from TEXT to VARCHAR(255)?

[Swizec]

You could fix it that way, but it would seriously hinder the ability to visit several topics per session.

A much better solution would be to... hmm... what version of mysql are you using?

[ptheyser]

MySQL 4