• Bu site çerezler kullanır. Bu siteyi kullanmaya devam ederek çerez kullanımımızı kabul etmiş olursunuz. Daha fazla bilgi edin.

Warning: Declaration of vBForum_Item_SocialGroupMessage

uydudoktoru

Tanınmış Üye
Yönetici
Yönetici
Offline
#1
Hello,

I solved the problem in the following way:

1. - GetLoadQuery function edit the files "socialgroupmessage.php" and "socialgroupdiscussion.php" found in "packages/vbforum/item/"
2. - The original function reads:

PHP:
protected function getLoadQuery($required_query, $force_rebuild = false)3. - Change the function to this:
PHP:
protected function getLoadQuery($required_query = self::QUERY_BASIC, $force_rebuild = false)
Warning: Declaration of vBForum_Item_SocialGroupMessage vb4.2.2 Sorununu düzelmek nasıl olur
 

Ekli dosyalar

uydudoktoru

Tanınmış Üye
Yönetici
Yönetici
Offline
#2

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 encounted 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 a couple of methods, depending on your circumstances and technical ability.


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

Goto :
Settings > Options > Plugin/Hook System and then set the "PHP Compatability" 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) this setting will pretty much disable all the new Strict & Deprecated messages anywhere.
If you have vBulletin Forum only, and have the Panjo enabled, this setting will also pretty much disable all the new Strict & Deprecated messages anywhere.

This is because all of those products use the "init_startup" hook, which is called at the start of every vbulletin page.
If you dont have any of those products running, you can create a dummy plugin yourself - again using the "init_startup" hook, and just put a comment in the php section.

PHP:
// Dummy Hook //
. This will cause the option to suppress errors after init_startup has been called.


2. For those who feel comfortable with editing files.

In class_core.php locate lines 5683-5685 (class_core.php is in the 'includes' folder)
PHP:
        case E_NOTICE:
            // Just ignore these completely //
        break;
Add lines for Deprecated and/or Strict errors as required ;

PHP:
        case E_NOTICE:
        case E_STRICT:
        case E_DEPRECATED:
            // Just ignore these completely //
        break;
This will bypass the additional error reporting.