vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin Pre-Sales Questions (https://vborg.vbsupport.ru/forumdisplay.php?f=26)
-   -   TOTAL Confusion 3, 4 or 5 (https://vborg.vbsupport.ru/showthread.php?t=303713)

TheLastSuperman 11-01-2013 09:12 PM

Quote:

Originally Posted by skol (Post 2457558)
It's php specific,not just 5.3 or 5.4..What runs on 5.3.27 won't run on 5.3.17 and vice versa..So upgrading to 5.4 won't solve all the problems.

Yes I know as in old mods etc that use deprecated values etc and yes someone was upgraded to 4.2.2 and to php5.4 then had to move them back to 5.3.27 I believe and it worked fine (yeah 4.2.2 on 5.3.27 but then on another 4.2.2 site it would not function properly on 5.3.27 but it was new the owner said forget it Mike just install me 4.2.1 so he could get going with the site as it was brand new but not everyone can simply do that i.e. if their forum has been long standing and has thousands of threads and posts etc) long story short every site there's been an issue on was custom regarding modifications/plugins so in essence unless you do a test server/site (most host will accommodate that request for free if you call and explain what is going on to them, if not perhaps a nominal fee and you will more than likely need to edit your hosts file to view the new site on the different server IP) then you just don't know and that compatibility tab in the admincp does not work all the time, it's a band-aid per say you should do as the hint suggest and sort the issues properly.

I'm not recommending 4.2.2 at all now, same as vB5.x I suggest 4.2.1 but that's because of the mod issues as some owners simply don't want to deal with all that, had them tell me that on the phone despite me telling them 4.2.2 and 5.4 will ensure their site runs smoother for longer (if no issues).

skol 11-01-2013 11:25 PM

Thats good advice,but it's not only down to mods/plugins.Vb is also different on specific php versions,but we cant go constantly testing php versions with the vb version or the mod/plugin.So we really need to see some more system requirements being more specific as to the version of 5.3 or 5.4.

nhawk 11-01-2013 11:49 PM

LOL, just to add to the confusion...

4.2.2 is running fine on PHP 5.3.10 for me. :D

oldengine 10-15-2014 04:14 PM

Now on vBulletin 3.8.9 Beta 2, but still looking.

Threads: 127,761, Posts: 1,041,312, Members: 74,459

Max Taxable 10-15-2014 04:31 PM

Quote:

Originally Posted by oldengine (Post 2518925)
Now on vBulletin 3.8.9 Beta 2, but still looking.

Threads: 127,761, Posts: 1,041,312, Members: 74,459

If it ain't broke, don't fix it.

Yoshiburger 10-15-2014 05:46 PM

vB5.1 is broken, do NOT use it under any circumstances on a site you care about.

oldengine 10-21-2014 02:08 PM

I suppose it could be considered broke in that I'm finding mods for version 4 that I cannot run on version 3.

If I update to 4, what exact version should I be targeting toward for starters?

Looks like Paul says: 4.2.1 or 4.2.2

Brandon Sheley 10-21-2014 02:54 PM

My suggestion is to stay far far away from vbulletin 5. It's nowhere near ready for prime time.
vBulletin 5 is broke in the fact that most of the site does not work and your members will hate you for "upgrading" to it.

Paul M 10-21-2014 04:05 PM

Quote:

Originally Posted by oldengine (Post 2519625)
I suppose it could be considered broke in that I'm finding mods for version 4 that I cannot run on version 3.

If I update to 4, what exact version should I be targeting toward for starters?

Looks like Paul says: 4.2.1 or 4.2.2

4.2.3 (wait for Beta 3 now, its due out soon).

For vB3, 3.8.9 (again, Beta 3 due in a week or two).

Max Taxable 10-21-2014 04:29 PM

Quote:

Originally Posted by oldengine (Post 2519625)
I suppose it could be considered broke in that I'm finding mods for version 4 that I cannot run on version 3.

You should list them. BoP5 has a huge list of v3 mods that work in v4, and otherwise. The two platforms are not so dissimilar that v4 mods cannot be also coded/ported to v3.

That's not a definition of "broken" by the way. You'll see "broken" and alot of misery and heartbreak - and loss of a ton of regular users - on a botched or glitchy "upgrade."

I've seen this happen even with a smooth "upgrade."

What's the compelling reason to "upgrade?"


All times are GMT. The time now is 04:27 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.00955 seconds
  • Memory Usage 1,740KB
  • 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
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)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