While the foundations of the codebase remain very fast, stable and secure even by today's standards, the evolution of the technologies on which it is based (especially PHP and MySQL) has reached a point where it is no longer viable to fix incompatibilities.

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ...................* Wrong boards order in your Board Index

You should note that PHP has already reached version 5.6+ and the current version of MySQL is 5.7+, so it is very likely that your host will upgrade to more recent versions shortly.If you still run SMF 1.1.x you should consider an upgrade to 2.0.x, with time to try to adapt things while everything still works, instead of trying to recover from an unusable forum if the current incompatibilities get worse with time. The chances are that further changes to PHP/MySQL will render 1.1.x unusable in a not so distant future.

Logged

Se forem conduzir, não bebam. Se forem beber... CHAMEM-ME!!!!

Quote

Over 90% of all computer problems can be traced back to the interface between the keyboard and the chair

and the reason you get the deprecated warning is because the function will soon be completely removed instead of just deprecated - so, hiding the warning will get you a short time of function - all the while you are digging yourself deeper into a hole when you will eventually HAVE to upgrade in a short time instead of a planned migration.

Logged

Please do not PM, IM or Email me with support questions. You will get better and faster responses in the support boards. Thank you.

I just registered to say thank you!I have an older forum that has been left running for a number of years with a small membership, so never really seen the need to upgrade as it just 'works'.

The recent PHP change by my host threw me in the deep end, but now it's back up and running for now.I now know I have no choice but to look at upgrading it, which is a shame as I like my forum's layout, mods, customization etc:

At least your fix has bought me some time to investigate just how to upgrade 1.1.21 to latest.I'm just disappointed that I need to upgrade, site's been up for close to 10 years and only now has it 'broken'.

Many thanks for you help.

Also to anyone needing to upgrade to 1.1.21 from an older version, if your admin control panel does not let you upgrade the normal way:

1) Click the normal upgrade link, when you get the errors look at the address bar and you'll see the URL for the .zip file for the 1.1.20/1.1.21 file.2) Browse to this manually and download the file.3) You can then manually go to package manager, upload the .zip and apply it without getting the error messages stopping you. Note you may need to rename the zip with something on the end if it says the file already exists. For example I renamed mine from 'smf_patch_1.1.21_2.0.10' to 'smf_patch_1.1.21_2.0.10-2' to then upload and apply it.

I just registered to say thank you!I have an older forum that has been left running for a number of years with a small membership, so never really seen the need to upgrade as it just 'works'.

The recent PHP change by my host threw me in the deep end, but now it's back up and running for now.I now know I have no choice but to look at upgrading it, which is a shame as I like my forum's layout, mods, customization etc:

At least your fix has bought me some time to investigate just how to upgrade 1.1.21 to latest.I'm just disappointed that I need to upgrade, site's been up for close to 10 years and only now has it 'broken'.

Many thanks for you help.

Also to anyone needing to upgrade to 1.1.21 from an older version, if your admin control panel does not let you upgrade the normal way:

1) Click the normal upgrade link, when you get the errors look at the address bar and you'll see the URL for the .zip file for the 1.1.20/1.1.21 file.2) Browse to this manually and download the file.3) You can then manually go to package manager, upload the .zip and apply it without getting the error messages stopping you. Note you may need to rename the zip with something on the end if it says the file already exists. For example I renamed mine from 'smf_patch_1.1.21_2.0.10' to 'smf_patch_1.1.21_2.0.10-2' to then upload and apply it.

Who is your hosting provider and what control panel are they providing you? Most providers in the shared market should offer you the ability of selecting your own PHP version (Including PHP 5.2, 5.3, 5.4 etc) . You should see something like a 'Select PHP Version' icon in your control panel if your web host offers it.

Whilst it is recommended you stay up to date, this might be an option worth considering.

Who is your hosting provider and what control panel are they providing you? Most providers in the shared market should offer you the ability of selecting your own PHP version (Including PHP 5.2, 5.3, 5.4 etc) . You should see something like a 'Select PHP Version' icon in your control panel if your web host offers it.

Whilst it is recommended you stay up to date, this might be an option worth considering.

Hey, thanks for posting this. My webhost gives me the cPanel interface, and sure enough there was that option in there. It looks like they recently upgraded to 5.6, but with that option in the control panel I was able to downgrade back to 5.4. Obviously I know I need to bite the bullet and start figuring out how to upgrade to SMF 2.x, but at least my forum is back to normal functionality for a while so I can upgrade at my convenience, rather than having to do it tonight.

I have extracted fixes for preg_replace(_callback) from SMF 2.0.15 into a XML mod file which I use together with my own mod for 1.1.21.If you have your own modifications, you can add this XML file and apply it or you can create new mod with that modifications.

Please note, I'm using Queryless URLs without Apache 1.0 mod in 1.1.21 and also some other custom modifications and I'm not sure if it affects the pregreplace.xml modifications or not.

No warranty! I can't confirm everything would work in all situations. I'm also not sure if the mod covers all places where preg_replace with 'e' modifier is used. I'm using this mod with PHP 5.6 for few weeks and we did not notice any problems so far but our users could not use all features.