Support Forum
its probably because that plugin is adding stuff to the wp tinymce editor incorrectly... too many plugins and themes make the false assumption that the wp tinymce editor is only loaded in the wp admin... a very bad assumption given that the wp editor can be used anywhere...
so you can see where they hook in for adding their stuff, they incorrectly tend to use 'init' and change it to 'admin_init' so they only do load it in the admin where they can make that assumption...
Visit Cruise Talk Central and Mr Papa's World
sintmacro said
sintmacro said
Hi, I've the same issue as Jan G. I use the plugin TinyMCE Advanced version 3.5.8. If I deactivate this plugin it works how it should work. But then I don't have editor for my standard posts.I replaced the plugin by Ultimate TinyMCE and this one is working fine. Seems TinyMCE is conflicting with the forum.
Hmm, unfortunatelly this isn't work eather. My editor stacks when using this plugin. What kind of editor are you using for this site?
stacks? what does that mean? what kind of editor here? our sp tinymce plugin...
Visit Cruise Talk Central and Mr Papa's World
Mr Papa said
stacks? what does that mean? what kind of editor here? our sp tinymce plugin...
It jams I mean. So no editing was possible anymore.
Oh oke, I use that to of course for the forum but to edit my WP Posts I use also a TinyMCE plugin. If I have activated that one it conflicted with the TinyMCE of the forum whereby the TinyMCE toolbar setting doesn't work anymore. The setting of the TinyMCE plugin overrules the setting of the TinyMCE forum plugin.
This is likely because authors who write extensions for the WP tinymce editor assume it is ONLY going to be used on the admin side of things. But this is erronious as WP have made it possible to use on the front end as well - like we do with SP.
The chances are that the plugin uses what is called the 'init' hook to activate it's stuff on each page load when it should, in fact, use the 'admin_init' hook. If you can find this and change it then it will probably correct the issue.
YELLOW
SWORDFISH
|
correct.. I said replace init with admin_init... but just to be sure, its often the issue, but not always...
see where they enqueuing their stuff (js, buttons, etc) to load...
Visit Cruise Talk Central and Mr Papa's World
I've checked it and the TinyMCE have below in his code. So I think it's correct as you said. In this case I don't need to change it but issue still there unfortunately.
add_action( 'admin_init', 'tadv_version' );
add_action( 'admin_init', 'tadv_load_defaults' );
if ( ! function_exists('tadv_mce_options') ) {
function tadv_mce_options($init) {
global $tadv_hidden_row;
$tadv_options = get_option('tadv_options', array());
if ( $tadv_hidden_row > 0 )
$init['wordpress_adv_toolbar'] = 'toolbar' . $tadv_hidden_row;
else
$init['wordpress_adv_hidden'] = false;
if ( isset($tadv_options['no_autop']) && $tadv_options['no_autop'] == 1 )
$init['apply_source_formatting'] = true;
if ( isset($tadv_options['hideclasses']) && $tadv_options['hideclasses'] == 1 )
$init['class_filter'] = '[function(){return false;}]';
return $init;
}
add_filter( 'tiny_mce_before_init', 'tadv_mce_options' );
}
well, as we said, would be looking for anything loading on init not admin_init... and not sure the ones you reference are the right functions anyways...
and as we said, its often, but not always, the init hook used...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)