There have been a few people with this problem and I guess there have been three strands of the cause.

The first would be partial updates of WP, SP and plugins. Once WP is moved up to 4.1 then it really is imperative that SP and all other SP plugins are also updated.

The second strand has been simply caused by other components of the site not updated to use latest versions of key WordPress libraries. This is the hardest to fathom.

However, some people seem to had issues with our ‘checkbox’ script library. I think on the whole this too has been a conflict with other libraries but we have been unable to determine where. So if all else fails, open the spFunctions.php file in the Sp theme you are using (you can use the theme editor in the forum admin for this) and near the top you will see a note about checkboxes and it tells you how to turn it off. Try that.

We are about to release 5.4.4 and in the this new update we have switched to using a different method for the checkboxes to counter this issue. But let;s hope the above checks get you back on the road. if they don’t then we will probably need a link to your forum page so we can see what is happening when the buttons are clicked,.

Thanks Andy for the response. I updated all plugins as you mentioned in the first solution but didn’t help. I’m not very familiar with wordpress libraries so not sure what to do about the second solution. Regarding third solution, I didn’t see anything mentioned about checkbox in spfunctions.php. Have attached the screenshot. 

Here’s the link to the forum – link

No screenshot?

Actually I think the checkboxes are the problem looking at your site.

As far as I can tell you are using our ‘default’ theme but which looks to have been slightly customised so probably pre-dates the option to turn checkboxes off. Can you open the spFunctions.php file in your theme /templates folder and add the following line of code AFTER the opening php tags and BEFORE the closing php tag. At the bottom before the closing tag will be fine.

define('SP_USE_PRETTY_CBOX', false);

Try that and see if that resolves it please.

Boom. It worked! Finally after a week, I’m able to post on the forums. 

Thanks Andy. Now you, for sure, know that this checkbox problem is one of the primary reasons for the buttons to not work. 

Thanks again

with the latest wp release, the pretty checkboxes have caused issues for a handful of folks.. dont really know why…   but in our themes and core, we are replacing the pretty checkboxes with css only equivalents… still good looking, just no js required…

WOW! it worked for me too. Thanks for the help!

Glad you are all working!

We upgraded a client site yesterday to WP 4.1 and updated plugins (including SP Version 5.5.4 – Build 12424) and are having the same issues with “add topic” and “add reply” buttons. I’ve disabled the pretty checkboxes as described above, turned off combined caching in the global settings, and basically tried everything I could.

I have a staging server set up where every other plugin is disabled except for Advanced Custom Fields and UberMenu (which are both required in the theme templates I guess in order to even see a page at all). I’ve tried deleting every superfluous script from the source using Chrome Dev Tools, and the only way I’ve been able to view the response form at all is to simply remove the “display: none” attribute.

Here’s a link to the staging server. Any help would be tremendously appreciated.

Well you do have two JavaScript errors which do appear to be stopping all subsequent scripts from running,

The first is to do with something maybe called ‘search-menu’? IS that the search button up on the top heading menu? I tried clicking on that and it doesn’t do anything as far as I can see.

The other error is in something called ’embed player’ but that, I don’t think, is a show-stopper.

The first one might be the cause of the problem but really does not removing from the equation first.

I’m embarrassed to admit that I was dismissing that error as trivial and unrelated. I guess I need to raise my debugging game, because I was unable to discern that it was stopping other scripts from running.

It was a script belonging to the parent theme, calling a css property on an undefined object. I don’t know whether the object-not-being-defined is a new phenomenon with the upgrades, or what, but it doesn’t really matter now. I wrapped the code in an if statement checking whether the object exists, and now the problem is solved.

Thanks so much for the catch!

You’re welcome.

It has gone now from the source of course but I do seem to remember seeing the jQuery library referenced with the $. For WP it should really be jQuery. But there may have been more to it than that…

Anyway – glad you have things back to normal.