There are likely only really 2 possibilities. The first is that something got corrupted during the download of the update resulting in actual, faulty files. This is highly unlikely as any such event would usually just stop everything dead. But there is always just that remote possibility.

The more likely and more common causes are simple script conflicts. And, of course, I can not look for those as you do not have SP running. You can, however, by simply using your web console. So you could activate the forum, run a few pages and try a few tasks and note what is reported in the console. This FAQ will guide you on how this works. It is very easy – https://simple-press.com/documentation/codex/faq/how-to/how-to-use-your-web-browser-console/

You clearly have tried the ‘remove all plugins and add then back one at a time’ process – which is always a good test. If you can do that again – but this time activating Simple:Press first – ir might also prove useful.

Also – has anything else changed? Most people usually say no to this but it more often than not proves to be that quite a few things have been added, updated etc., and any such change can have knock-on effects.

And finally… we have had issues with Avada before. The last seemed to be connected to them loading an unsupported JavaScript library that clashed with the standard, supported and supplied WordPress libraries but I would not expect that to clash with the admin side of things.

So – I do not mind taking a closer look at your site but would (a) need to have the forum active and (b) if you wanted me to look on the admin side of things, would need an admin account so that I could log in.

Hello

It’s not my intention to hijack this thread but I have the same issue as the lady above.

Running latest versions of all plugins and WP and Avada theme and I have the same bugs. As soon as I enable SP lots of issues.

For example when I open Avada theme options I get semi blank screen and get the following error

TypeError: $(…).wpColorPicker is not a function
http://www.zinga.eu/wp-content/themes/Avada/framework/admin/assets/js/smof.js?ver=4.4.1
Line 32

If you want me to open a new thread for this please let me know.

Found out that it has to do with me updating today to the latest version of the SP plugin ‘Tags’.

When I disable that one everything is A-OK again.

I’ll keep it disabled until a fix comes (if you can fix it no matter if it’s the theme’s author’s fault or not).

I can’t change theme or change forum plugin so I need to have a fix even if it means disabling parts of plugin or theme.

Angie: Are you using the Tags plugin as well? If so can you please deactivate it so we can see of that is the issue?

Chrostophe: Are you able and willing to make a small edit to a file in the Tags plugin so we scan ee if that is really the issue?

Yellow Swordfish said
Chrostophe: Are you able and willing to make a small edit to a file in the Tags plugin so we scan ee if that is really the issue?

Sure no problem

Thanks – try this:

The file in question is in the plugins folder so that would be by default:

/wp-content/sp-resources/forum-plugins/tags/sp-tags-upgrade.php

At line 40 of that file is the code block:

# db version upgrades
if ($db < 4) {
    # admin task glossary entries
    include_once('sp-admin-glossary.php');
}

That line – include_once – needs commenting out with the hash like the line above.

Let me know if that fixes things please…

Ok so the results are…

After I commented out that line and activated TAGS then I got the following error:

Fatal error: Call to undefined function sp_add_glossary_keyword() in /data/sites/web/zingabe/www/wp-content/sp-resources/forum-plugins/tags/sp-admin-glossary.php on line 15

But after refreshing the plugin page the plugin seems active and everything works in backend.

So yes it doesn’t break everything like before but just got this strange error when activating it.

If you need me for further things let me know

I have the same issue, my admin panel is not working anymore. I also did the plugin test, and I isolated it to the SP plugin. I have a huge forum with people posting every day as part of my business, so I cannot turn SP off. This just happened after the latest update. And I also noticed the same error message as Christophe above.

I tried deactivating the “Tags’ plugin, but it doesn’t let me. When I click on “deactivate”, I just get a blank screen. Then, when I go back to the plugins page, “Tags’ is still active.

Then I deactivated the “Subscriptions” plugin, just to see if all the plugins have this issue. But that one deactivated and then reactivated without any problems. So there is an issue with the “Tags” plugin.

Should I follow the same procedure which you gave Christophe or wait until you find the problem?

Shama said
I have the same issue, my admin panel is not working anymore. I also did the plugin test, and I isolated it to the SP plugin. I have a huge forum with people posting every day as part of my business, so I cannot turn SP off. This just happened after the latest update. And I also noticed the same error message as Christophe above.

I tried deactivating the “Tags’ plugin, but it doesn’t let me. When I click on “deactivate”, I just get a blank screen. Then, when I go back to the plugins page, “Tags’ is still active.

Then I deactivated the “Subscriptions” plugin, just to see if all the plugins have this issue. But that one deactivated and then reactivated without any problems. So there is an issue with the “Tags” plugin.

Should I follow the same procedure which you gave Christophe or wait until you find the problem?

I had same problem for deactivating.

What I did was first renaming “tags” directory to “tagsss”, then deactivated it without problems and then renaming it back to “tags”

My apologies. Absolutely my fault. The Tags plugin was due for release next week when it would have been safe to do so.

The error on de-activation would cause no damage to anything as it happens. Just a brief nuisance.

Yes Shama – please follow the same path as above if that it Ok with you. Let me know if anything else is amiss…

This has not been a good day!

Yellow Swordfish said
My apologies. Absolutely my fault. The Tags plugin was due for release next week when it would have been safe to do so.

The error on de-activation would cause no damage to anything as it happens. Just a brief nuisance.

Yes Shama – please follow the same path as above if that it Ok with you. Let me know if anything else is amiss…

This has not been a good day!

Lol me too I have done nothing but tracking and fixing plugin conflicts all day (not only this one which was the easiest one to identify).Tomorrow is a new day (with a new set of problems hehe)

My fingers are crossed!

Just to make sure that I am doing this right. I am in my Cpanel and I am looking at this block of text. Should I just delete this line only:

include_once(‘sp-admin-glossary.php’);

and leave everything else alone in this block of text?

I am not quite sure what you meant when you said “commenting out with the hash tag”.