search issue

[CarpCharacin]

This warning shows up above the advanced search: Warning: Declaration of vBForum_Item_SocialGroupMessage::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupmessage.php on line 261

Warning: Declaration of vBForum_Item_SocialGroupDiscussion::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupdiscussion.php on line 337 the advanced search page is also kind of messed up.

[ozzy47]

Open your includes/config.php file and below <?php add the following.

define('SKIP_DS_ERRORS', true); So it looks like this:
<?php
define('SKIP_DS_ERRORS', true);
/*================================================= =====================*\
|| ################################################## ################## ||
|| # vBulletin 4.2.2

This turns off the extra error reporting in php 5.3 & 5.4 (for strict & deprecated warnings), but will allow other important errors to show.

Use a editor like notepad++ (http://notepad-plus-plus.org/download/v6.6.8.html) to edit any files, don't use Notepad or Wordpad.

[ForceHSS]

fixes in my sig or update to 4.2.3 will fix them for good

[CarpCharacin]

Is skipping errors really a good fix?

[ForceHSS]

they are not errors only warnings but the best thing you can do is add the fixes that are in my sig or update to 4.2.3 and that will also fix the warnings

[ozzy47]

You do not need to do the edits you are showing there. All you need to do is add the define('SKIP_DS_ERRORS', true); line to the includes/config.php file. This turns off the extra error reporting in php 5.3 & 5.4 (for strict & deprecated warnings), but will allow other important errors to show. That is for anything below 4.2.3

That will sort the issues you point out:
packages\vbforum\item
socialgroupmessage.php
socialgroupdiscussion.php

includes
class_core.php

Editing the class_core.php file doesn't cover up errors though. It changes the vBulletin Error Handler so it doesn't catch warnings, notices, or deprecated notices. These will still be properly logged in your php error log but if they are not displayed on the screen there is no adverse affect on the application because they are informational not errors.

As for this one:
clientscript\yui\uploader\assets
uploader

That is already add into v4.2.2 pl2 and beyond, so no need for that anymore.