Error above header

[Chimpie]

On our site, www.emtlife.com we're receiving numerous lines of errors, mostly..

Warning: trim() expects parameter 1 to be string, array given in [path]/includes/class_activecache_methods.php on line 423

Warning: trim() expects parameter 1 to be string, array given in [path]/includes/class_activecache.php on line 123

We cannot log into the AdminCP. Any attempts to do so result in:

Unable to add cookies, header already sent.
File: /home/emtlife/public_html/includes/class_core.php
Line: 3283

Thoughts?

[Hawk2]

have you tried to replace them files in the ftp?

[Chimpie]

The funny thing is that I don't see a class_activecache.php file in the /includes directory.

[Hawk2]

disable all plugins see if that fixes it, replace the core.php file, edit the config and put the disable line into it, make a support ticket

[Chimpie]

Will the tools.php give us access to the AdminCP? We're unable to log into through the forum.

[Hawk2]

would not hurt to try if it does not start a support ticket

[Steve Machol]

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, vB CMS and Skimlinks if you have them.)

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?