vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   Dead Thread Bumping (https://vborg.vbsupport.ru/showthread.php?t=225702)

Speysider 10-21-2009 03:22 PM

Dead Thread Bumping
 
I'd like to know what the stance is on bumping dead threads on vBulletin.org. Recently, I reported a thread that was bumped after it had died a long time ago. And I got warned for it.

So, how many days, months will it take to consider a thread dead? I think after a year it would definitely be dead, but I was thinking after a month?

Princeton 10-21-2009 04:22 PM

there's no official rule on bumping "dead" threads

note: what you consider "dead" may still be "live" by another

whenever we consider a thread "dead" we will close it; there's no need to report

Speysider 10-21-2009 05:53 PM

That doesn't really help Princeton. Sorry.
Sorry, but you are wrong, read the rules, it states "don't bump threads"

I will quote it in a sec.

Quote:

8. No "Bumping" (Other’s threads/posts): Before replying to a thread, take notice of the last post date. Try and avoid replying to posts more than 6 months old. If you have a similar question and cannot find the answer, create your own thread. Generally speaking, due to the progression of vBulletin development, a post more than 6 months old is more than likely going to be for an older version of vBulletin.

Marco van Herwaarden 10-22-2009 03:01 AM

This rule does not disallow bumping older threads, it only request to "Try and avoid replying....".

We do give our members freedom to reply to such a thread but we ask them to use common sense and not bump old threads in which the information is outdated.

On the older (3.0 and older) vBulletin releases information was often limited to a single vB version. With the newer 3.5 and higher versions we had a long period where information would be valid spanning many vBulletin versions. Once vB4 comes out, most information posted on pre 4.0 will probably not apply anymore, so replying to a thread on 3.8 with a question intended for 4.0 will probably be frowned upon as that would only confuse people.

You also reported a post that was a reply to a bit older thread about making backups. Making backups is the same on almost all vBulletin versions, external tools also are mostly still the same, so the information in such a thread is still valid and accurate and we have no problems if someone replies to such a thread regarding his current situation.

PS I can not find a warning or infracation in your profile.


All times are GMT. The time now is 02:31 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02196 seconds
  • Memory Usage 1,718KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (4)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete