[Forum] Upgraded from 3.8.6 to 4.0.7 and getting errors

[ColoradoAP]

We upgraded from 3.8.0 to 3.8.6 this morning, and it worked fine. We then ran the upgrade to 4.0.7. It didn't show any errors during the upgrade, but we're getting these errors when we go to the site. The admin panel doesn't work and we've already tried to disable hooks in the config file. That didn't help.

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: gobutton in [path]/includes/functions.php on line 4007

Parse error: syntax error, unexpected T_STRING in /home/color62/public_html/forum/global.php(605) : eval()'d code on line 1

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: spacer_open in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: spacer_close in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: ad_header_logo in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: ad_header_end in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: ad_navbar_below in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: ad_footer_start in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: ad_footer_end in [path]/includes/functions.php on line 4007

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: navbar_noticebit in [path]/includes/functions.php on line 4007

Parse error: syntax error, unexpected T_STRING in /home/color62/public_html/forum/global.php(658) : eval()'d code on line 1

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: headinclude in [path]/includes/functions.php on line 4007

Parse error: syntax error, unexpected T_STRING in /home/color62/public_html/forum/global.php(834) : eval()'d code on line 1

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: header in [path]/includes/functions.php on line 4007

Parse error: syntax error, unexpected T_STRING in /home/color62/public_html/forum/global.php(835) : eval()'d code on line 1

Warning: fetch_template() calls should be replaced by the vB_Template class. Template name: footer in [path]/includes/functions.php on line 4007

Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /home/color62/public_html/forum/global.php(836) : eval()'d code on line 1

and when we try to log in it gives this error

vBulletin Message

Unable to add cookies, header already sent.
File: /home/color62/public_html/forum/includes/class_core.php
Line: 4551

The website is http://www.coloradoap.com/forum

Thanks in advance!

[Steve Machol]

There is no fetch_template()function in vB4. Those errors are all either from add-ons or old files.

To troubleshoot this, first reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server. Also be sure to upload the admincp files to whichever directory you have set in your config.php file. Then run 'Suspect File Versions' in Diagnostics to make sure you have all the original files for your version and that none show 'File does not contain expected contents':

Admin CP -> Maintenance -> Diagnostics -> Suspect File Versions

[Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]

Next, disable all products (except vB Blog and vB CMS if you are running the Suite.)

Admin CP -> Plugins & Products -> Manage Products -> Disable

Then manually uncheck all plugins that are not for 'vBulletin Blog' and vBulletin CMS' here:

Admin CP -> Plugins & Products -> Plugin Manager

You must do BOTH of those steps in order to disable all non vBulletin Modifications.

Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it.

Do you have the same problem?