View Single Post
  #3  
Old 09-24-2018, 05:31 PM
twistsol's Avatar
twistsol twistsol is offline
 
Join Date: Apr 2015
Location: Cottage Grove, MN
Posts: 52
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Not to be harsh, but if you're asking this question, you aren't ready to upgrade a production site. Upgrading vBulletin is not like installing a new version of Office. It requires planning, testing, and feedback from your community. I've been managing software projects for over 30 years and the best way to fail is to do this by the seat of your pants without a plan.

What is in the upgrade document gives the basic steps to upgrade, not a detailed step by step plan. There is an assumption that you have access to your web server, have at the very least basic skills moving files around on the server, and have access to your database. Assuming all that, note that upgrading from 3.8.11 to 5.4.4 you WILL LOSE all your styles, and any extenstions or customizations you have.

A detailed step by step guide would be difficult if not impossible to produce since there are so many differences from one server setup to another.

My best advice would be as follows:

Determine why you want to upgrade. If it is to be on the latest version, then stop and don't go any further. If you have other valid reasons then:
  1. Identify all your customizations and extenstions and find replacements for them if they are not already built into VB5.
  2. Know that there won't be replacments for all of them and you may need to live without some functionality you have today.
  3. Determine if you, and your users, can live without that functionality and decide if the upgrade still makes sense.

Once you've decided to proceed with the upgrade, create a backup of your database and site files and use those to build a test environment to practice your upgrade. The very first time I did this I went from 387 to 422 and practiced it over a dozen times until I could get it upgraded in about 4 hours. That upgrade plan had over 100 individual steps.

Document in excrutiating detail the steps necessary to upgrade and differences, if any, between the steps in your test and production environments.

Decide if you will build, buy, or use one of the built in styles for your site.

Once your test upgrade is done and the way YOU like it on your test site, open it up for a few select users of your site to look around and poke at it. There will be stuff you may have missed, things you like that they hate etc. Take their feedback seriously and adjust your test site as necessary.

Now you're almost ready to upgrade your live site.

Add to your upgrade plan the necessary steps to restore your site to pre upgrade condition if everything goes to hell.

Upgrade your production site and good luck to you. If you have specific questions and need help as you go along, ask here and you'll get plenty of help
Reply With Quote
7 благодарности(ей) от:
Brandon Sheley, delicjous, In Omnibus, Manoel J?nior, MarkFL, Max Taxable, noypiscripter
 
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01132 seconds
  • Memory Usage 1,779KB
  • Queries Executed 11 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD_SHOWPOST
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_box
  • (7)post_thanks_box_bit
  • (1)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (1)post_thanks_postbit
  • (1)post_thanks_postbit_info
  • (1)postbit
  • (1)postbit_onlinestatus
  • (1)postbit_wrapper
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • reputationlevel
  • showthread
Included Files:
  • ./showpost.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/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_post_thanks.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_postinfo_query
  • fetch_postinfo
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • showpost_start
  • bbcode_fetch_tags
  • bbcode_create
  • postbit_factory
  • showpost_post
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • fetch_musername
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • post_thanks_function_fetch_thanks_bit_start
  • post_thanks_function_show_thanks_date_start
  • post_thanks_function_show_thanks_date_end
  • post_thanks_function_fetch_thanks_bit_end
  • post_thanks_function_fetch_post_thanks_template_start
  • post_thanks_function_fetch_post_thanks_template_end
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • showpost_complete