PS – I’ve tried deactivating both WL Tags and WL Welcome, but that had no effect. I even uninstalled and reinstalled Tiny MCE Editor AFTER deactivating both WL plugins, but still no luck. 

it was working in 5.2.1?  all 5.2.2 did was fix two lines of code… or were you on an older version?

Any plugins that try to add things to tinymce?  seems that most make a bad assumption that wp tinymce only exists in the admin… and they blindly try to add their stuff to any wp tinymce instance…

probably be tomorrow at earliest before we can look into…  and next couple days are holidays… 

did you send the credentials to Yellow Swordfish, Mr Papa and BrandonC??

The conflict is with something called ‘php execution plugin’ which is attempting to add something to the tinymce editor and failing. My guess – and it is only a guess – is that this plugin expects the tinyMCE editor to be used in the admin side of things only and is, perhaps, not loading what it needs on the public-facing side of things but still trying to load itself into the editor. If this is the case then it is a false assumption as the WP tinyMCE editor has been exposed specifically so plugins can use it where they need to – which is what Simple:Press now does.

You might start out by seeing if there are any options to turn this other plugin off under certain circumstances perhaps.

Thanks, Mr Papa and Yellow Swordfish. I hadn’t subscribed to this topic, so only just saw your replies.

I think I installed the php execution plugin when I was using s2Member as my membership site plugin. I’ve since switched to WishList Member, so I think it was safe to deactivate and delete php execution plugin.

Unfortunately, this hasn’t solved the problem — I still have not tinyMCE editor bar. 

I’ll see if any other plugins might be affecting it…

Check with the theme as well – always worth trying the WP default theme to see if the theme is the root of the issue. Let us know what you find and we should be able to help or advise.

Okay, I tried deactivating all plugins except WishList Member, and that didn’t do anything.

Then I tried deactivating WishList Member (which can only be done for diagnosis, as that’s a “mission critical” plugin!) and my forum totally disappeared, so I couldn’t even test to see if tinyMCE editor was there or not!

Then I tried switching from Genesis theme to Twenty Twelve theme. Still no change.

I’m stumped!

PS – I’ve also tried deactivating all S:P plugins, then only activating tinyMCE editor plugin. Still no dice…

couple questions…

it appears you are using caching… have you told w3tc to ignore the forum page for ALL types of caching in use?  its not clear from the w3tc message in the footer if that has been done…

we know wishlist member works fine with simple press and tinymce because we use it here.   but we also know that wishlist tags, which I see you using, is known to be an issue… We even worked with the wishlist tags folks on the problem and a fix, but we have yet to see them release it (a bit disappointing)…

I am also seeing wishlist tags trying to interact with the tinymce instantiation…  I am guessing that this wishlist plugin has made a mistake in assuming that the wp tinymce editor would only be used in the wp admin for blog posts… but the wp devs made the editor a class such that it could be used anywhere including on the front end… it seems, but cannot be certain, that its failing on the wishlist tags stuff…  unfortunately too many wp plugins that deal with tinymce made the mistake of assuming blog posts only and assumed it was in the admin and that certain js or files may be loaded and have not been updated to stay current with wp…  they really should be checking if the tinymce they are trying to load to is the specific one they want to target…  or give you options or hooks to prevent this…

I also see another wishist plugin something about idcard interacting with tinymce… no clue if problem…

to top that off, the jetpack after the deadline module is trying to affect the tinymce editor too…

long winded, but can you try disabling those plugins and either confirm or rule them out?  start with wishlist tags and run a test.. then disable icard and run test… finally the after the deadline module and test…

Hi Mr Papa,

I disabled all plugins, and that made no difference to tinyMCE editor. However, I’m now going through and disabling the ones you asked about, one at a time.

WishList Tags: no change to tinyMCE editor, BUT, disabling this plugin actually made me unable to type in a new reply or topic!!! Very weird…

WishList ID Card: no change to tinyMCE editor

I can’t find the After the Deadline module. I’ve looked inside JetPack and see lots of modules, but do not see “after the deadline” anywhere. Am I looking in the wrong place?

???

PS – just noticed your question:

have you told w3tc to ignore the forum page for ALL types of caching in use? 

I looked inside W3Total Cache, and this is what is inside the field for “Never cache the following pages:”

wp-.*.php
index.php

So apparently W3TC is not being told to ignore the forum page, but I’m not sure what to type in that field to tell it to do so. Do you have any idea? It doesn’t look like putting the URL of the forum page will be correct… (And this plugin is notoriously opaque for non-techies like me to try and use correctly!!!)

I had to break one of my own strict rules to help answer this by activating JetPack. Afraid this plugin causes nothing but problems for many other plugins so I keep it inactive at all times!. The ‘After the Deadline’ component is part of the Spelling/Grammar section.

As to W3TC I have never used that either – I am afraid I’m totally unconvinced that the extra overhead is worth it – but as far as I am aware just putting the forum slug into each exclusion area is enough. So – assuming your forum page slug is the default then ‘/forum’ should do it (without the quotes of course). Maybe someone can conform that for me…

the issue with w3tc is the number of different caching options it has… each type of cache has its own tab or admin page…  you must put the exclusion on each page of caching type you are using… there is not a global exclusion…

I tried adding /forum to the “never cache the following pages” field in W3TC.

I tried deactivating the Spelling/Grammar section of Jet Pack. 

Neither made any difference.

I’ve also already tried deactivating W3TC and Jet Pack completely before, and just tried again, and nothing.

I am totally at a loss here.

Ok – let’s recap…

The changes to the wp-cache – adding the forum page as an exclusion has to stay there.

We believe there may be issues with that Jetpack component and with WishList Tags plugin. The problem is that it could be none, either or both so trying, for example, to switch wp-theme without deactivating these plugins might still produce the same result. It really needs to be all at once.

There is something else I would like you to try and that is turning off (for testing) the wp-wall thingy. I don’t know if you are aware but it is very, very resource hungry and is polling the server and grabbing quite a bit of data every 4-5 seconds. Now this should not really effect the editor loading but it is worth discounting it as a source of the issue.