![]() |
Anyone have any ideas on how to add a "This thread closed by (who ever closed it)" whenever a thread is closed?
Thanks, Parker |
yeah that would be a great addition... now that i have mods
|
until a hack is made for this, I would suggest just posting to a thread before closing it, and say why
|
yeah that's what i do...
|
In your showthread.php file look for:
if ($threadinfo[open]==1) { $replyclose="$replyimage"; } else { $replyclose="$closedthreadimage"; } and change this to: if ($threadinfo[open]==1) { $replyclose="$replyimage"; } else { $replyclose="$closedthreadimage"; $whoclosed = "This thread closed by $username"; } then in your showthread template put: $whoclosed wherever you want it on the page. Note: You will have to post the last message in the thread for the correct person to show up as to closed it as it lists the last person in thread as the closer. But this allows your mods to post the reason why it was closed and at the same time alert the author of the post who closed it. Parker |
No offense meant, Parker, but if the mod has to post the last post before closing the thread, he might as well say "this thread is closed by me because..." etc. Your hack doesn't shorten the procedure and therefore seems a bit redundent to me.
|
bira:
Yes, it is redundant but at the same time it puts at the top of the page who closed it. Members are lazy and gon't want to go down a long thread to see who closed something. This way they see at the top. I am still working on a way to get this to be automatic but I thought that I would throw this out to see if anyone could get any use out of it. Don't like it. Don't use it. Its that simple. Parker |
don't be discouraged on my account, Parker. I was merely hoping you could extend the hack further :)
|
Future Hackers of America
open postings.php and find: Code:
if ($threadinfo[open]==1) [sidenote] Is there a way to call newreply.php from inside postings.php so that one wouldn't actually have to anything other than insert the call right before the thread close? Code:
newreply.php?action=postreply&message=Closed%20Thread |
rangersfan -
Code:
//Set EVERY form generated variable here, including: |
ok,
That just went right over my head! :) No problemo bira. Like I said I was just trying to get something out there for a temporary fix until someone else came up with something that really worked. Parker |
Ed I think I tried that and it didn't work.
|
Parker - That was to rangersfan. He asked about calling newreply.php from posting.php :)
Umm... I think it should. Pretty sure I've seen it done before. The only reason it didn't work in Perl was because of the shebang line (#!/usr/bin/perl) I'm not sure how to repress what it returns (the page it returns I mean) though - that could be the problem. [Edited by Ed Sullivan on 08-18-2000 at 01:47 AM] |
Ermm well calling newreply.php is going to end up calling global.php again which is going to end up involving a cookie which is going to mean it is going to send header information and we can't at this point so we will at least get a warning message about header's already been sent..
|
Good point.
Your best bet is to ripout the posting code, and put that in a file called newreply.inc.php. Make sure you delete the redirect related stuff. Then just set the variables and "require" it in postings.php. |
I am really interested in seeing what you guys come up with for this.
Parker |
me too ... although i am more interested in a post and close thread hack :D
|
Any one want to take a stab at this hack still?
A pretty cool hack to. |
All times are GMT. The time now is 01:52 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|