after upgrading to 4.1.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MR K
    Senior Member
    • Dec 2006
    • 301
    • 4.0.0

    [Forum] after upgrading to 4.1.2

    i got this error onto my forumhome ...

    PHP Code:
    Warningtrim() expects parameter 1 to be string, array given in [path]/forum.php(653) : eval()'d code on line 28 
  • Steve Machol
    Former Customer Support Manager
    • Jul 2000
    • 154488

    #2
    Eval() errors are due to modifications.

    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?
    Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
    Change CKEditor Colors to Match Style (for 4.1.4 and above)

    Steve Machol Photography


    Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


    Comment

    • MR K
      Senior Member
      • Dec 2006
      • 301
      • 4.0.0

      #3
      find it, there was a trouble with a plug-in ..

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...