vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   News and Announcements (https://vborg.vbsupport.ru/forumdisplay.php?f=2)
-   -   Abandon vBulletin 2? (https://vborg.vbsupport.ru/showthread.php?t=107007)

Xenon 02-02-2006 09:22 PM

Abandon vBulletin 2?
 
Hey,

i went through some thread statistics tonight, and found out, that we didn't have a new release for vb2 since more than 6 months, so i think vbulletin 2 is definitelly out of date for most user on vbulletin.org.

That's why i want to start a poll, about moving it into the archive, so we would have a clearer forumhome again (this will restrict people from posting in the vb2 sections, downloading the hacks would of course still be possible by browsing the archive)

So what do you mean?

tehste 02-02-2006 09:33 PM

i think you should think about removing the 3.0 category too :)
3.5 has AJAX!

TruthElixirX 02-02-2006 09:36 PM

Are there still people being given support in the 2.0 section? ;)

I'd say we should archive it somehow...

Allan 02-02-2006 09:42 PM

Remove just 2.0 section ;)

Stangsta 02-02-2006 09:52 PM

Maybe collapse it into 1 forum and lock them so they cant be posted in. That way they are still accessable for reference.

DrewM 02-02-2006 09:58 PM

Quote:

Remove just 2.0 section
agree

yayvb 02-02-2006 10:00 PM

Agreed, I donno why anyone would really want to still use 3.0 now that 3.5.3 is available.

Oblivion Knight 02-02-2006 10:01 PM

I doubt many modifications in that forum are even getting any kind of support from their authors.. I certainly haven't been keeping track of my 3.0.x releases, never mind 2.x.x!

Although I think that the 3.0.x forums should be kept for the time being..

Zidane007nl 02-02-2006 10:01 PM

Yeah, just remove 2.0 section.
A lot of users still use 3.0.x.

Xenon 02-02-2006 10:14 PM

Quote:

Originally Posted by Stangsta
Maybe collapse it into 1 forum and lock them so they cant be posted in. That way they are still accessable for reference.

that's the sense of archiving them.

we still ahve the vb1 forums on vb.org just noone post in them anymore ;)

Princeton 02-02-2006 10:17 PM

yes, archive .... I would suggest going all the way and archive 3.0 -- soon we will have vbulletin 4.0 :D

Daniel 02-02-2006 10:39 PM

2 & 3 removed ;)

Gio~Logist 02-02-2006 10:42 PM

Quote:

Originally Posted by yayvb
Agreed, I donno why anyone would really want to still use 3.0 now that 3.5.3 is available.

Because no one has been able to convert ushop successfully?

Giovanni Martinez

Paul M 02-02-2006 10:47 PM

Quote:

Originally Posted by yayvb
Agreed, I donno why anyone would really want to still use 3.0 now that 3.5.3 is available.

That's an very selfish and narrow view. Lots of forums still run 3.0, not everyone wants to run the latest and greatest when they are happy with what they have. I agree with moving the vb2 forums to a single location. I think 3.0 should be left alone for at least another 12/18 months.

If vb.com still support vb2 & 3 then so should vb.org.

Princeton 02-02-2006 10:57 PM

Is it worth it? (keeping 3.0 forums) I don't know.
Check the activity and compare posting rate and support for those hacks. My guess is ... it's been declining ever since 3.5 was released.

BamaStangGuy 02-02-2006 10:58 PM

Remove 2.0 and 3.0

yayvb 02-02-2006 11:36 PM

Ok I do take back what I said... I don't use 3.0 but I know for a fact others do because I see topics posted regarding 3.0. I'm not trying to be selfish, I just feel like there are so many security upgrades that I personally want the newest, but I'm not everyone. :)

Tony G 02-03-2006 12:15 AM

No. 2.0 and 3.0 are still widely used - its just that most mods for these versions have been made and thought of.

derekivey 02-03-2006 12:24 AM

Archive 2.0, but leave 3.0.

SCRIPT3R 02-03-2006 01:38 AM

Remove 2.0 and 3.0

Andreas 02-03-2006 02:00 AM

Archive vB 2. IMHO, vB 3 should be supported at least until vB 4 is out.

Logikos 02-03-2006 02:01 AM

Either Or for me, I can deal with vB3.0 since its still used. 2.0? Out the door... :)

Hellcat 02-03-2006 02:07 AM

I'd say archive the 2.x sections, but keep one spot open for discussions and support about 2.x issues and hacks.

I know a (very large and public) forum that ran 2.x till a month ago, or so....

Also keep the 3.0.x sections as they are for the moment since the 3.0.x is not outdated yet IMHO....

rjordan 02-03-2006 02:41 AM

Quote:

Originally Posted by Paul M
If vb.com still support vb2 & 3 then so should vb.org.

100% agree. If Jelsoft is still willing to sell (and update with critical fixes) any version, it should not be tossed.

Cal813 02-03-2006 03:47 AM

vb 2 was my dream back then I say keep it I also agree above if jelsoft is making vb2 still and updating it we should keep it up here too :)

Quillz 02-03-2006 04:28 AM

I say archive vBulletin 2 but keep 3.0.x and above.

Marco van Herwaarden 02-03-2006 07:36 AM

I still see questions in vB2 hack threads maybe once every 2 weeks (not counting the people who not looked in what version they where posting or are askign for a vB2 hack to be ported to vB4 ;)). So maybe archive and lock for new threads, but don't lock for replies.

GamerzWorld 02-03-2006 12:17 PM

Quote:

Originally Posted by derekivey
Archive 2.0, but leave 3.0.

/signed

Cle 02-03-2006 12:42 PM

No, as long vB2 is still available for download and fully supported by vB.com, I think it should stay there.

Zachariah 02-03-2006 12:46 PM

Keep online:
- I go in and out of all ver of forums all the time filling requests now and then.
- There are many sites with all ver. of the forums.
- There are tons of ideas and old hacks that update with time.

EX:
Winamp.com
Powered by: vBulletin Version 2.3.9

deathemperor 02-03-2006 02:39 PM

archive 2.0, it's still not time to do that on 3.0, there are still zilliant boards use 3.0

MrZeropage 02-03-2006 03:32 PM

**voted**

Chris M 02-03-2006 04:56 PM

Until Jelsoft stops actively updating the 2.x series (which does include bug and security updates :p), it shouldn't be "thrown out the door"...

Condensing all the threads into one forum, and disabling new threads in that forum would be a good idea - Allow replies to be made to the threads, but other than that I can't see why we would want to totally archive vB2.... Yet...

Chris

nitro 02-03-2006 07:50 PM

Quote:

Originally Posted by Chris M
Until Jelsoft stops actively updating the 2.x series (which does include bug and security updates :p), it shouldn't be "thrown out the door"...

Condensing all the threads into one forum, and disabling new threads in that forum would be a good idea - Allow replies to be made to the threads, but other than that I can't see why we would want to totally archive vB2.... Yet...

Chris

I think most forums that are on v2.x today are unlikley to be pro active vb hack users.

I also think you will get a good idea altho not entirely accurate as not evryone sees polls how many here still use v2.

I think Chris M has the best option which is the beginning of a phase out. Persoanlly I really like 3.5 but killing 3 aswell would be quite ludicrous as theres still hordes using it even here, is still 3.07 I believe unless I missed here getting upgraded. :)

Marco van Herwaarden 02-03-2006 08:08 PM

Quote:

Originally Posted by nitro
I think most forums that are on v2.x today are unlikley to be pro active vb hack users.

doubt that is correct. I think most vB2 boards are still at vB2 because they use so many hacks.

AN-net 02-03-2006 09:24 PM

i would say leave 2.0 and 3.0.x as they are still supported by jelsoft and that there are forums still out there operating on such softwares. would jelsoft bother releasing patched 2.x software if no one was using it?

Tony G 02-04-2006 12:04 AM

Exactly what my point was before. Just because the hack forums aren't busy with posts doesn't mean people aren't using the hacks or the software version. :)

Andreas 02-04-2006 12:13 AM

Quote:

Originally Posted by Chris M
Until Jelsoft stops actively updating the 2.x series (which does include bug and security updates :p), it shouldn't be "thrown out the door"...

Condensing all the threads into one forum, and disabling new threads in that forum would be a good idea - Allow replies to be made to the threads, but other than that I can't see why we would want to totally archive vB2.... Yet...

Chris

That sounds like a good solution.
*thumbs up*

GamerJunk.net 02-04-2006 03:42 AM

I think they should be compiled into one forum and basically have the category description be "If you still use the 2.0 version of Vbulletin, post anything related to that software version here"

Kinneas 02-04-2006 06:11 AM

Archiving 2.0 at this point would make sense I think, but support for 3.0 should be kept, for sure. I know of quite a few companies that still use 3.0.


All times are GMT. The time now is 05:20 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.06063 seconds
  • Memory Usage 1,808KB
  • 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
  • (9)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (2)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (40)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
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete