Wysiwyg toolbar disappeared from nodes after Wysiwyg/CKEditor update

The _samples directory is not used or looked for at all by Wysiwyg, and should not be needed by the editor itself either.

You should be able to see which editor version you have installed on admin/settings/wysiwyg under the "Installation instructions" fieldset. The version number should also be visible after the editor name in the table showing which editor profiles have been assigned to which input formats, on the same page. If you do not see an editor name and version on an assigned profile, it indicates Wysiwyg is no longer able to detect the editor library which was once assigned to that format. You can still edit the existing profile(s) but you can't create new profiles with that editor until its installation is fixed.

I'm a bit confused about which editor is missing the toolbar, TinyMCE or CKEditor? You say you're only using TinyMCE profiles. If you are not using CKEditor you should simply be able to remove its folder, that won't affect TinyMCE at all. If the TinyMCE profiles are missing the toolbar and buttons have been enabled, it's a problem with the sites/all/libraries/tinymce folder which should show up as an "could not detect version"-error under "Installation instructions" - or simply "Not installed" if sites/all/libraries/tinymce wasn't found at all.

Note that 2.4 fixed detection of CKEditor versions 3.5.4 and 3.6, so you'll need that Wysiwyg version if you want to use those versions of CKEditor.

The FAQ might help you identify some common issues. Does that help?

I'm having a very similar problem. I have TinyMCE 3.4.2 installed with Wysiwig 6.x-2.4. We have users that we've defined as "Content Editors". They've just started reporting that when they try to edit a blog item, the TinyMCE editor doesn't appear. But the TinyMCE editor does appear when editing an event or a page item.

I wasn't seeing this as the Administrator and nothing I changed seemed to resolve the problem. So I deleted the WYSIWIG profile associated with Full HTML and recreated it. Then I tried to create new content items (blog, page, etc.). When viewing those items in edit mode, the TinyMCE editor didn't appear for me as Administrator. When I went into "Buttons and Plugins" under the newly recreated profile, none of them were checked. When I checked them, saved the changes and then went back to the content items, the TinyMCE editor and the appropriate buttons appeared. What's odd about this is that when I viewed the "Buttons and Plugins" settings before I deleted the profile, none of them had been checked but the buttons still appeared. It was only after I deleted and recreated the profile did it start checking to see what buttons were checked in that area.

Even after deleting and recreating the profile, I still can't get the TinyMCE editor to appear for our "Content Editors" when viewing blog items. They also don't see the "Disable Rich Text" link under the body input box even though that setting is checked in the WYSIWIG profile. TinyMCE does appear for them when they edit event and page items.

As Administrator, I see the TinyMCE editor when editing any content type (blog, event, page, etc.)

Based on the above, it appears there's some kind of configuration problem going on here. I would first start with permissions but as thoughtcat noted, there's no permissions to check.

I figured this out on my end and thought I would share in case it might be of help. I'm using the "Filter by Node Type" module and discovered that the Input Format applied to the blog posts didn't include the "Content Editors" role. It did include "Authenticated Users" but for some reason, it only worked once I added the "Content Editors" role to that Input Format. I don't know why that stopped working recently but that change fixed it for me.

Just one more follow-up - I jumped the gun a bit on the above post. Turns out, adding the "Content Editors" to that Input Format didn't fix the problem for that group. Instead, I had to change the Input Format to allow both Filtered HTML and Full HTML on the blog content to get the editor to show up for "Content Editors" users. I don't know why that is since it doesn't make sense to me that it only works for those users when both Input Formats are selected but not when one or the other is checked. But it's now displaying for those users.

@aimutch, @thoughtcat, we've had problems detecting when only one format is available to a user before, but I thought those issues were fixed in the latest release(s). Are you using a module which alters the node form, input format descriptions (under the textarea) or perhaps does theme overrides for these things? Do you see any JavaScript errors on the page?

@thoughtcat, do you use a custom theme? If so, does it print $page_bottom before the body tag closes in the page template?

I assume the problems were resolved. If not, please reopen the issue.