My forum is ++++ed...

[MahdyE23]

I cannot quote someone or do anything. When I post a thread, this appears:

https://vborg.vbsupport.ru/external/2015/05/15.png

Can anyone help me?

[ForceHSS]

add the following line to the top of your /includes/config.php file under the <?php line:
Code:
define('SKIP_ALL_ERRORS', true);

[AusPhotography]

Likely cause, php was upgraded and you need to upgrade to vB4.2.3 RC 1

[MahdyE23]

Likely cause, php was upgraded and you need to upgrade to vB4.2.3 RC 1

My vBulletin is upgraded to the most recent version out.

[ForceHSS]

If you are running 4.2.3 RC 1 then you should not be getting this error

[MahdyE23]

If you are running 4.2.3 RC 1 then you should not be getting this error

I was never receiving this order, I've had my forums running smoothly for a month and a half with no problems. And then there were nameserver changes, DNS issues and host problems and then I started getting all these errors.

There's nothing in my members area that gives me the option to download 4.2.3, so adding the code is all I can do for now,

[Lynne]

What version of PHP is your server running?

You may get 4.2.3 by clicking the More Options button on the download page.

[MahdyE23]

What version of PHP is your server running?

You may get 4.2.3 by clicking the More Options button on the download page.

5.5.24. I looked all over for a download in the Mmber's Area, Patch area, couldn't find any version for 4.2.3

[ForceHSS]

See screenshot

[thetechgenius]

add the following line to the top of your /includes/config.php file under the <?php line:
Code:
define('SKIP_ALL_ERRORS', true);


Did you try what ForceHSS suggested? The very first time I installed vBulletin 4 I got all kinds of errors at the top of my forum, but my forum still worked fine with the errors there. So I added the same code as ForceHSS suggested, and the errors disappeared. There is also a config option in the PHP.ini I think, that does almost the same thing I believe. But I am not sure about the php.ini option, so I could be wrong about that. It has been a very long time.

[Disco_Stu]

add the following line to the top of your /includes/config.php file under the <?php line:
Code:
define('SKIP_ALL_ERRORS', true);

I've never subscribed to the notion of masking errors. It's a very bad and downright sloppy approach to software problems. Anyone on my payroll doing that would be fired immediately

[thetechgenius]

I've never subscribed to the notion of masking errors. It's a very bad and downright sloppy approach to software problems. Anyone on my payroll doing that would be fired immediately

Some errors have nothing to do with vBulletin, and some errors are just out of your control. I'm not saying that you should skip all errors with every website you create or build, but with vBulletin sometimes its a good idea in some cases.

I did it with my vBulletin, and it has been working perfectly fine for the past 2 years.

[ozzy47]

I've never subscribed to the notion of masking errors. It's a very bad and downright sloppy approach to software problems. Anyone on my payroll doing that would be fired immediately

Some errors have nothing to do with vBulletin, and some errors are just out of your control. I'm not saying that you should skip all errors with every website you create or build, but with vBulletin sometimes its a good idea in some cases.

I did it with my vBulletin, and it has been working perfectly fine for the past 2 years.

This is why you should use:
define('SKIP_DS_ERRORS', true);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.

[MahdyE23]

Did you try what ForceHSS suggested? .

This is what fixed it. It fixed all the errors I was having, I wasn't looking for a different way anyone because it was fixed.

[Disco_Stu]

This is what fixed it. It fixed all the errors I was having, I wasn't looking for a different way anyone because it was fixed.

That didn't fix any errors at all. All you did was hide the error messages. It's like piling snow on top of a garbage heap and saying "Hey, I just cleaned up the garbage!"

[cellarius]

To be fair, we're not talking errors here. We're talking deprecated warnings, translating to: It is perfectly okay to use this functionality as you do at present time, but be warned: things may change in one of the future versions of php.

[ForceHSS]

The line in the config is no longer needed in 4.2.3 so looks like vb has fixed it in this version

[cellarius]

The policy on warning suppression (which was changed for 4.2.2) has been reverted for 4.2.3. In effect, that line you had to add in 4.2.2 is now already included.

[DemOnstar]

If the warnings can't be fixed, hide them. It makes the board look better.

[Disco_Stu]

The policy on warning suppression (which was changed for 4.2.2) has been reverted for 4.2.3. In effect, that line you had to add in 4.2.2 is now already included.

When you don't have the skills or you're just too damn lazy then cover up the problems and don't address them. The customer will never know the difference!!! What a company!!

[Lynne]

5.5.24. I looked all over for a download in the Mmber's Area, Patch area, couldn't find any version for 4.2.3
If you are running PHP5.5, you need to use vB4.2.3. See post 9 for what to look for to download it.

[Digital Jedi]

When you don't have the skills or you're just too damn lazy then cover up the problems and don't address them. The customer will never know the difference!!! What a company!!
When error messages are for problems that can not only not be fixed, but are not actual problems, then, yes, you ignore them. You seem to fail to understand what the exact issue is.

[Zachery]

When you don't have the skills or you're just too damn lazy then cover up the problems and don't address them. The customer will never know the difference!!! What a company!!

The issues are actually CORRECTED in 4.2.3.