Re: SMF 1.1.x incompatibility with recent PHP versions (PHP5.5+)

[Bazino]

1.1.x will work fine on  php 5.5
Here is a quick change to fix all notices.

open index.php change

Code Select Expand


error_reporting(E_ALL);

To

Code Select Expand


error_reporting(E_ALL & ~E_DEPRECATED & ~E_NOTICE);


open ssi.php
Change

Code Select Expand


$ssi_error_reporting = error_reporting(E_ALL);

To

Code Select Expand


$ssi_error_reporting = error_reporting(E_ALL & ~E_DEPRECATED & ~E_NOTICE);


Hey!

First of all, thank you very much for trying to help people who don't want to upgrade to 2.+ due to heavy customization.

Today unfortunately and against my demands (at first, then later begging), my stupid provider has upgraded my webspace to 5.5 and I can't go back, they simply deleted everything below 5.5.

I was soooo much hoping, that I would skid by with the help you provided here, but now I have a problem:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 82767645 bytes) in /www/htdocs/xxxxxxx/smf/Sources/Subs.php on line 1843

This is all I get instead of my forums :-(

Any ideas?

[Kindred]

Split the topic since this is unrelated to the php switch.

You need to check with your host....  however, if they have updated php, then you will need to upgrade to SMF 2.0.13 anyway...

[Bazino]

Split the topic since this is unrelated to the php switch.

You need to check with your host....  however, if they have updated php, then you will need to upgrade to SMF 2.0.13 anyway...

I don't understand.
The topic was about people having forums on php versions below 5.5 and with the change to 5.5 on their webspace should have been able to still run the forum with the quoted changes?
Are you telling me that's not the case, even tho ppl have posted that their forums still work after such a change?

[Kindred]

What vbgamer suggested does not STOP the errors, it just HIDES the error messages.

Also, your issue is completely unrelated to those error messages.

Running out of memory is a host-side issue and they should be able to tell you what is causing it.


That being said, SMF 1.1.x is not getting any further updates and only minimal support at this point. It is at the end of its life. You (and everyone) should upgrade to 2.0.x

[vbgamer45]

Attach your Sources/Subs.php file i can see what it is getting stuck on that line.

[Bazino]

Attach your Sources/Subs.php file i can see what it is getting stuck on that line.

Here you go.

[vbgamer45]

It looks like autolinks setting using up memory
I disabled it try this file for now

[Bazino]

It looks like autolinks setting using up memory
I disabled it try this file for now

Well it did help for sure... just not enough it seems... damn.

Now I run out of time...

Fatal error: Maximum execution time of 30 seconds exceeded in /www/htdocs/v104793/smf/Sources/Subs.php on line 2507

EDIT: Is there a way to kill the whole error-logging? I'd guess that would free up a lot of time?

[vbgamer45]

script time can be done on a hosting level in php.ini try this subs.php file disables parse bbc code might give you time to fix stuff

[Bazino]

script time can be done on a hosting level in php.ini try this subs.php file disables parse bbc code might give you time to fix stuff

YES!!!!!!!!!!!!

Man, you are my hero now!

Thank you SOOOO much!!!

First I'm gonna try to get rid of a few mods to save space, then maybe I can keep running this old piece until September and then I'm gonna close it anyways.