Hey Sascha,

I should really start by saying that we have lots of users who use Simple:Press along side WooCommerce with no problem at all, and so far have not had any other reports of what sounds like a jquery conflict due to WooCommerce.

Just for peace of mind, ‘javascript:void(null)’ is not an error or a problem of any kind – see This Page for reference.

So as to the problem itself, is everything up to date i.e SP and SP plugins, WP and WP plugins, WooCommerce and any of it’s additions?

What has changed that you know of? You’ve said ‘working like in past’ so I’m assuming it worked fine meaning something must have changed. Have you added any WooCommerce extensions or third party plugins that run along with WooCommerce that could be to blame?

Make sure you are not caching the forum page too, as Simple:Press is dynamically loaded on one page it can’t be cached. Not sure if WooCommerce offer any kind of caching but it’s worth me mentioning.

And lastly, are you able to open the browsers console when viewing a page with the problem to see if any errors / conflicts are showing?

Can we start off by asking what has changed? I think you have had Simple:Press active for quite a while now so what changed to stop it working?

At the end of the day however, it sounds like a javascript conflict or error.

This FAQ explains the javascript:void: https://simple-press.com/documentation/codex/faq/troubleshooting/i-am-seeing-javascriptvoidnull-for-a-browser-link/

This one explains one of the most common causes of script conflicts: https://simple-press.com/documentation/codex/faq/troubleshooting/what-is-this-jquery-conflict/

You can look for such errors using the web browser console. If you do not know how to do this then this FAQ gives guidance: https://simple-press.com/documentation/codex/faq/how-to/how-to-use-your-web-browser-console/

But the first question is important as it might help pinpoint where to look.

Oh dear. Whoops! Looks like we both posted at the same time. But the message is the same.

Thanks for Information. What I have done to find out – I deactivate everything – just simple-press is active. Then it worked. I activated WooCommerce too. It didn’t work again.

But today I remembered that I have forgotten to deactivate all simple press plugins too. Done now. All is working fine. Activated all wordpress plugins inkl. WooCommerce. All is working fine. Activated “Editor TinyMCE Rich Text” in  3.2.3 Version – Buttons don’t work again. Made complete test again.

Deactivated everything now and just activate Simple Press Plugin “Editor TinyMCE Rich Text” in  3.2.3 Version. Buttons don’t work. Activating all Simple Press Plugin but not TinyMCE. Buttons are working. With active TinyMCE not again.

Question about TinyMCE:

Is it possible that there is a conflict between “https://de.wordpress.org/plugins/tinymce-advanced/” and “https://simple-press.com/downloads/tinymce-editor-plugin/”?

How can I find a possible conflict? Using firebug but just for css and html-cases until now.

Absolutely there may well be a conflict with the WP plugin advanced-tinymce. I thought we had people using that one so firstly do check that it is fully up to date.

The main problem with some tinyMCE ‘extension’ plugins is that they have not been created to ONLY load their extensions within the WP Admin (i.e., for blog post creation) so they try to load on the ‘front’ as well – but because the components are geared for the admin it can fail and cause all kinds of problems.

So this could be the case here, If it is then it is probably also an easy fix. Most plugins we have seen use the ‘init’ WordPress hook to load their stuff. To ensure it is only loaded on the admin side they should be using the ‘init_admin’ (or is that ‘admin_init??? – I will need to check!). I would contact the plugin authors to ask if this is the problem and request a fix if it is.

Just for extra information – not that long ago it was not possible for plugins to use the WP editor on the front end of your site but the WP team made that possible a couple of years back and some plugins have just not caught up with the implications of that.

Done – we will see – https://wordpress.org/support/topic/getting-javascript-issues-with-simple-press-forum-buttons-dont-work?replies=1#post-7891156

please do let us know the outcome…

No it’s not this issue. It so strange. Now I’m opening also a ticket on the theme-developer of “Avada”.

I’m lost any idea what I can do… I’m stuck.

Getting this in firebug:

Uncaught Error: `selector` option must be specified when initializing tooltip on the window.document object!

/wp-content/themes/Avada/assets/js/main.min.js?ver=1.0.0:1

Deprecated TinyMCE API call: .onNodeChange.add(..)/wp-includes/js/tinymce/plugins/compat3x/plugin.min.js?ver=4208-20151113

You do not need to worry about the ‘Deprecated TinyMCE API call’. One day the WP team will deal with that I am sure but it doesn’t cause anything to stop working.

The first error in the WP theme’s main.min.js is an issue however. That is probably what is stopping things from working. It needs dealign with or, at the very least, trapping.

Hopefully they can give you a fix. Actually – I am pretty sure we have encountered this once before so most interested in what they say.

Now – this is clearly something to do with tooltips. I very much doubt there is any connection but just in case try this…

In the templates folder of your Simple:Press theme is a file named spFunctions.php. At the very top there is an option to not use the jQuery.ui tooltips for Simple:Press. Try changing the true to false and see if that helps at all. You will probably need to clear your browser web cache before you test the change.

YEAH! It’s working again. Thanks a lot. Very nice!

Well that’s good news.. What was the fix – Tooltips?

I have to update this and done:

In the templates folder of your Simple:Press theme is a file named spFunctions.php. At the very top there is an option to not use the jQuery.ui tooltips for Simple:Press. Try changing the true to false and see if that helps at all. You will probably need to clear your browser web cache before you test the change.

Good to know, thanks!