Support Forum

This is quite an upset really as well as a bit of a puzzle. An upset because I have rarely seen anyone report such a perfect path to an upgrade which then failed and a puzzle because I know others have upgraded from 4.0.4 and – in fact – versions 2.x and 3 – without hitting this error message.

I am looking into it but one question… despite the error message – was the upgrade link still available or did it then actually fail to activate? I am thinking that it probably DID activate otherwise the error message is usually a 'fatal error' reported by WP.

Understood. My feeling is that it would have gone on to upgrade.
But – if you prefer – I can advise a simple code edit that would inhibit the error message but this would be to code within the 4.3.2 'new' files. Your call.

Problems upgrading (although not ths one) only usually come about because of a problem with other javascript loaded on the system. We see no end of people having probems because their theme loads up an old copy of jQuery for example – or loads it from Google. They don't use the WP API and everything else just gets whacked and trampled on. The other main problem are plugins that load their stuff on every page inlcuding admin panels when it is not used. We have had so many problems with things like gallery scripts being loaded in the admin panels! makes you want to weep!

So we canlt guarantee no problems because it depends so much on what you have or have not got loaded b ut hey – you took extra precautions so hopefully you should be OK. We have also had the opposite of course – people upgradng from version 2.0 with no problem.

Anyway the code edit is to the file sf-hooks.php…

Quite near the top you will find this code:

if($SFSTATUS != 'Install' && sf_get_option('sfblockadmin')) {
        add_action('init', 'sf_block_admin');
}

That first line needs to change to:

if($SFSTATUS == 'ok' && sf_get_option('sfblockadmin')) {
        add_action('init', 'sf_block_admin');
}

That should inhibit that error message.

Wow… you need to read this short wiki article and then deal with the list – the article tells you how. A list that big will be slowing down your forum display….

Good news on the upgrade though. That change is now in the core code although I will never quite understand why you and nobody else… but I have come to expect that with WP sites

use the 'About Simple:Press' option on the forum admin (above the forms) – or the information icon on the front end. It will tell you which skin and icon set it is trying to use.