vBSEO 3.6.1 and vBulletin 4.2.2 - Likes warning message

vBulletin 4.2.2
vBSEO 3.6.1

When trying to view Likes on the Member Profile page, I get the following:

Any suggestions on the best way to correct this?

I haven't yet upgraded to PHP 5.4 - was waiting for 4.2.2 compatibility.

 

uninstall vbseo? (lol)

 

Eventually, I am going to dump both but at the moment this isn't helpful.

 

See
http://www.vbulletin.com/forum/foru...tion-of-vbforum_item_socialgroupmessage/page2

Workaround:

In class_core.php locate lines 5683-5685

Code:

case E_NOTICE:
// Just ignore these completely //
break;

Change to this

Code:

case E_NOTICE:
case E_STRICT;
case E_DEPRECATED;
// Just ignore these completely //
break;

 

Also:

http://www.vbulletin.com/forum/foru...000121-vbulletin-4-2-2-full-has-been-released

Some further information on error displays in 4.2.2 ;

As part of the php compliance changes, error reporting in 4.2.2 was fixed to take account of the new strict & deprecated errors added in php 5.x
A side effect of this is that old (existing) errors that were not showing up may also now get displayed.

All of the errors we encounter during testing were corrected, but there may be more.
If you encounter such an error, then please log it in the vB4 Jira project, so we are aware of it.


If you need to disable error displays, there are several methods, depending on your circumstances and technical ability.

1. Add this line to your php.ini file (production sites should run like this anyway)

Code:

display_errors = Off


2. If you cannot access your php.ini file, add this line near the top of your config.php

Code:

ini_set('display_errors', 'Off');


3. Use the option added in 4.2.2 to suppress messages if you have products or hooks in use that still generate errors.

Goto : Settings > Options > Plugin/Hook System and then set the "PHP Compatibility" setting to 'Yes'.

This will change the error reporting options within vBulletin on the first hook that is run.
If you have vBulletin Suite (i.e. Blogs / CMS) or you have the Panjo Product enabled, this setting will pretty much disable the Strict & Deprecated messages anywhere.
This is because all three of those products use the "init_startup" hook.

If you don’t actually have any of those running, you can create a dummy plugin yourself - use the "init_startup" hook, and just put a comment in the php section.

Code:

// Dummy Hook //

. This will cause the option to suppress errors after init_startup has been called (which is at the start of almost all pages)


4. This is for those who feel comfortable with editing files.

In class_core.php locate lines 5683-5685

Code:

case E_NOTICE:

// Just ignore these completely //

break;

Add lines for Deprecated and/or Strict errors as required ;

Code:

case E_NOTICE:

case E_STRICT:

case E_DEPRECATED:

// Just ignore these completely //

break;

This will bypass the additional error reporting.

 

Thanks for the info @djbaxter

 

You can also replace the 4.2.2 class_core.php file with the one attached to this Jira.

http://tracker.vbulletin.com/browse/VBIV-15862

This then allows you to add one of two new constant definitions to your config.php file, to either suppress the display of the new php5 errors, or just suppress all error display.

 

Excellent! Thank you, Paul.

 

This didn't make it into the new release this week, had to do the manual fix in post 5 again.

 

I just started getting these after applying the recent PL4 security update to 4.2.2

I have first done option 4, editing class_core.php.. no help..

Then 3 turning off the hook system.. also nothing..

And lastly 2 with config.php..

None of these seems to have stopped the error reporting.