Warning: Declaration of vBForum_Item_SocialGroupMessage

[chubba]

I am getting the same trying to upgrade a forum from 3.7.1 to 4.2.2. Member list white-screens and advanced search gives:

Warning: Declaration of vBForum_Item_SocialGroupMessage::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupmessage.php on line 262

Warning: Declaration of vBForum_Item_SocialGroupDiscussion::getLoadQuery() should be compatible with that of vB_Model::getLoadQuery() in ..../packages/vbforum/item/socialgroupdiscussion.php on line 338 

Only a test copy of the site so will try a previous version and see if that works. The fix did now work for me but made the advanced search white-screen rather than show the errors. So maybe if my search was working properly then the fix would have worked...

[lyndonbarrie]

I added a new plugin on:

init_startup

to:

define('SKIP_ALL_ERRORS','SKIP_ALL_ERRORS');

to execute the first piece of code. That worked for me without changing the files.

5677 function vb_error_handler($errno, $errstr, $errfile, $errline)
5678 {
5679 global $vbulletin;
5680
5681 if (defined('SKIP_ALL_ERRORS'))
5682 {
5683 return;
5684 }
5685


hope this helps someone.

[Zachery]

Each person should start their own topic, or support ticket if they're having issues.

[GamBun]

I have HERE: http://tracker.vbulletin.com/browse/...#action_189994 and HERE: http://tracker.vbulletin.com/browse/...#action_191141

but I still cannot do anything on my site since October 13th. It's a bit frustrating waiting so long to be honest. I thought I might get help there as this is what vBulletin tells us to do for help. Any suggestions? I have put in my own post here: http://www.vbulletin.com/forum/forum...82#post4013048

[rootsxrocks]

I have a novel idea!
how about fixing the errors¿

[Zachery]

I have a novel idea!
how about fixing the errors¿

For the most part, they're not errors, these are warnings and depreciated notices that have been disabled as long as vBulletin has been around. We enabled them to test for compatibility, some did not surface during testing. But if you report them in jira, and then apply the work around, we'll see to them the next time we're able to push an update out.

[gsk8]

Just a note that it has not been updated since latest 4.2.2 patch....

[Zachery]

The patch addressed a security issue, nothing to do with the warnings and notices.

[Phat Phreddy]

Did this really never get fixed ?? 4.2.2.

[Mark.B]

Did this really never get fixed ?? 4.2.2.

There's nothing to fix.

As of vBulletin 4.2.2 we’ve stopped suppressing notices and warnings. This is a change from all previous versions of the software.
In some environments more notices/warnings show than in others. In order to address the issue you just need to add the following line to your config.php file
define('SKIP_ALL_ERRORS', true);
You can see additional information about this change here: http://www.vbulletin.com/forum/forum...-been-released

[majickal]

There's nothing to fix.

As of vBulletin 4.2.2 we’ve stopped suppressing notices and warnings. This is a change from all previous versions of the software.
In some environments more notices/warnings show than in others. In order to address the issue you just need to add the following line to your config.php file
define('SKIP_ALL_ERRORS', true);
You can see additional information about this change here: http://www.vbulletin.com/forum/forum...-been-released

Mark,

If there is nothing to fix, why is this warning occurring then? Also, why would we need to change anything in the class_core.php file if there is nothing wrong with the release?

If as you say 'In some environments more notices/warnings show than in others', are we to understand that this is an issue with the QA process and there are not enough resources allocated to sufficiently test release candidates prior to upgrade notices being posted in our administration areas?

Skipping errors/warnings/notices is very poor programming practice, why not simply fix them? If the error is being generated by PHP, rather than vBulletin, surely this indicates that there is an issue with the code/software.

There has been a solution to the issue posted, why not just endorse that fix rather than tell members to make code changes which cause the warning to be ignored? It simply makes no sense to me.

I understand that the 4.2.2 stopped suppressing notices and warnings, as you stated, so why pretend that this is OK. If this warning is hidden, by changing the core class of vBulletin, what if there are other flaws this will cause us to miss warnings for? which could be far more serious?

If there is a good reason not to use the method noted here: http://www.vbulletin.com/forum/forum...93#post4000793 I would be really keen to hear it.

[Mark.B]

vBulletin has always suppressed php warnings by default, right up until 4.2.2. Most other software works exactly the same way. Php warnings should not really be displayed on a production server at all, so you may want to ask your host about that.. You need to understand what a php warning is. It simply means that that piece of code is, or will soon be, deprecated in php and may not work at all in a future version of php. It does NOT mean it won't work now. However, displaying the warnings themselves can break functionality in a php application such as vBulletin.

[fayax]

Barcraft's post number 26 fixed the same issue on mine.

[Paul M]

Its not going to be fixed in 4.2.2 at all, its fixed as part of 4.2.3.

[kourou]

This is not a software we should be paying for.

Upgraded to the latest "stable" release so that I have to google for a problem, the solution to which was to "hide the error/warning messages". It's a known bug for more than a year and still not fixed.

Your next goal should be to release something really stable, worth our money, because, from what I can see, for the last 3 or 4 years any new version is much more buggy than the previous.

[donald1234]

This is not a software we should be paying for.

Upgraded to the latest "stable" release so that I have to google for a problem, the solution to which was to "hide the error/warning messages". It's a known bug for more than a year and still not fixed.

Your next goal should be to release something really stable, worth our money, because, from what I can see, for the last 3 or 4 years any new version is much more buggy than the previous.

Vbulletin 4 is not being developed anymore. You will need to upgrade to vbulletin 5 for latest release. Also the issue you mentioned I believe has been fixed in 4.2.3, and although is beta that is only because it is not being developed and no point in having 4.2.4 etc so easier to add anything that crops up as the next beta.

[Mark.B]

This is not a software we should be paying for.

Upgraded to the latest "stable" release so that I have to google for a problem, the solution to which was to "hide the error/warning messages". It's a known bug for more than a year and still not fixed.

Your next goal should be to release something really stable, worth our money, because, from what I can see, for the last 3 or 4 years any new version is much more buggy than the previous.

There is nothing to fix.

They are not error messages, they are php warning and notice messages. Every version of vBulletin prior to 4.2.2 used to hide them by default. They should not display on a production server anyway.

In 4.2.2 we changed the behaviour of this, which has the result that on in correctly configured servers, the warnings and notices will show.

[GrnEyedDvl]

I don't generally get involved in these conversations but its getting a bit ridiculous around here.

There is nothing to fix.

There is definitely something to fix, even if it is only the perception of your customers.

Most of your customers have no idea how their servers are configured as they are on hosting provided by a third party, and they are not technical people to begin with. The fact that this is just a deprecation warning doesn't really mean anything to them, what DOES mean something to them is that they either do not know how to fix it or do not have the access to change how their webserver is setup and that on some installs it really does break the forum software. All they want is their forum to run smoothly.

So yes, it needs to be "fixed" and it needs to be fixed now.

But what really needs to be fixed around here is the attitude of some vBulletin employees. First off who are you to say what an "incorrectly configured" server is. The reason that is even an option in php is so that people can test things. So lets say that someone running a shared hosting server has a problem reported by one of his customers and he enables this to help troubleshoot. It doesn't "break" other software packages, but suddenly now anyone hosting vBulletin on this server has a broken site because the server owner tried to help another customer. This is unacceptable.

But even worse is the way vBulletin employees respond to their customers. You deliberately changed it to display in 4.2.2 even though you know full well it breaks some installs of vBulletin, and then 3-4 of you respond spend more time responding in this thread than it would take to change it back. And then you tell your customer to go tell whoever operates his server that its their problem when they truly do not understand what is going on in the first place. All they know is that vBulletin does weird stuff.

I have been in business for a very long time now, and I swear if someone working for me did that he would be fired. Either you do not know how this impacts the reputation of vBulletin or you do not care. Either is unacceptable. At some point every forum operator out there has one of his forum members ask him his opinion of whatever software package they are using, and you just gave them one hell of a good reason to give you a negative review. Shame on you.

As one of the bigger vBulletin forums out there, along with several other smaller installs, I do as a general rule like the package. But you guys are notorious for not responding well to problems. I can point out numerous examples of this. Its probably not worth my time to do so but I had to comment this time because I am getting tired of seeing these kinds of replies on a premium platform.