Mr Papa said
one, deactivate and uninstall the sp tinymce plugin…  then reactivate it… since it was running with very old SP version its possible there was  problem with its initialization…  see if that helps…

Ok I tried this, but… no effect!

Mr Papa said

In an earlier screenshot you posted, it looked correct, but double check forum – options – global settings and make sure tinymce is the default editor…  then as an extra check, go to your profile in the forum, the posting options and make sure tinymce is your editor…

Checked and OK !

Yellow Swordfish said
Do you have any plugins active (WordPress plugins that is) that add components to TinyMCE – ie., new toolbox buttons, TinyMCE plugon or other functionality?

I have Ultimate TinyMCE, but it is not activated !

I have sent to both of you the login/password for my forum !

OK – couple of things. One is that Ultimate TinyMCE – if active – almost certainly WILL mess with the forum editor because it is intended to be used on WP Posts and NOT in live site situations but is coded in such a way that it will always be loaded. We can almost certainly help you fix this.

Now – in post 14 above Steve asked you to ‘deactivate and uninstall the sp tinymce plugin…  then reactivate it…’. This is actually incorrect. What he should have asked you to do is uninstall it and then reactivate it.

can you please do that. And then – if it still does not show – can you make an image of the admin > components > editor panel so we can see what the TM settings are…

Wow Uninstallation and reactivation made the plugin to work ! Thank you !

Next stage for me is to test with my original theme now ! 

So, TinyMCE work with the basic theme, but not with my “Options” theme !

If nothing else that theme IS adding items to the tinyMCE editor. I will try and explain…

Your theme and some plugins make the assumption that the tinyMCE editor supplied by WordPress is ONLY going to be used to create/edit WP posts and pages. But this is not correct. WordPress makes the editor available for any plugin to make use of both in the back (admin) and front end (public side) of your web site.

The problems happen when a theme – such as yours, adds components to the editor but does NOT make the actual program code available on the front end of the site to support those added components. This then results in an error – the code is not found – and tinyMCE failing to load.

What the author of your WP theme needs to do is make sure that the theme components are ONLY added to the editor in the administrative back end of your site. Same goes for plugins like the Ultimate TinyMCE plugin. This is actually very easy for them to achieve

Hello Yellow swordfish!

Thanks for that explaination ! I dropped a mail to the theme author, I don’t know if he would help..

If not, I’m afraid I would be stuck ! 

I’ll let you know !

Anyway, I thanks your for the help and the time you already gave me with that issue !

Didero

let us know what they say…  quite often its the theme hooking into the ‘init’  hook for adding stuff instead of the ‘admin_init’ hook…

Hello Mr Papa,

Sorry to be such a pain… But could you post an example of code with “admin_init” and “init” hook, then I could check in my theme if I can find something similar and perhaps I could be able to make a modification myself (I’m not very optimistic but I need to try something !)

Once again, thanks in advance ! 

Well here is an example from oue blog libnkling plugin:

add_action(‘admin_init’, ‘sp_linking_blog_link_form’);

You will be looking for something similar but obviously with a different second parameter. And if you find it change ‘admin_init’ to ‘init’ if it looks like the second parameter is a function that loads up the tinyMCE extensions.

actually, I would look for the opposite…  look for it using ‘init’ hook and change it to ‘admin_init’…

since they are assuming (incorrectly) that the wp editor is only in the admin, only have them do their thing in the admin…

Hum.. anyway, I don’t find any add_action(‘admin_init, *tiny_something*) nor add_action(‘init, *tiny_something*), in my theme folder…

dont look for the tiny stuff… just look for the add action with init…  the second part is a function name and could be just about anything…

OK, I replaced some add_action(‘init’ I have found by add_action(‘admin_init’ 

until I get the editor to work and finally after 3 files changes it works !!!!

Now I’m going to test If can reverse some of the change I’ve made just to be sure I didn’t change anything unnecessary, but now I think I can handle the next steps by myself and I think this topic can be tagged as “resolved”.

I really want to thank you once again, you helped me to resolve my problem, even though, the problem wasn’t really related to your plugin, but to my theme. Most of the support team wouldn’t have spent much time for a problem that is not really related to what they are supposed to support. You guys went beyond my expectations and beyond your “duty”, that’s pretty rare, and I wanted to highlight this !

Plus, I’ve learnt many things because you don’t hesitate to share and teach your knowledge !  

Thank you very much ! 

Didero !

outstanding work!  glad we could assist!  it really helps when themes/plugins read and follow the wp api…  its possible, its just an outdated theme from before wp added the wp editor api to support using it anywhere, so dont want to be too harsh…