CKeditor & WYSIWYG - UI for registered users does not appear despite having ALL needed permissions

I haven't had time to check this yet, but maybe it's related to #835682: %t (path_to_theme() ) returns modules/field (or whatever module is creating the wysiwyg) instead of the active theme., since that issue could cause it to try to fetch a list of stylesheets from the admin theme when not intended to?

I am having the same issue but I tried the above solution to view administration theme but that did nothing.

Edit: I am having this same issue on 2 different installs on 2 different servers.

Wysiwyg does not check any permissions at this point, if you've got access to a format, the assigned editor should show up.
I don't know where to begin speculating what could cause these issues since I can't reproduce them on my own.

If it's alright with any of you, I would like to request access to a site with this problem so I can debug the "attach an editor"-process. (A regular user with access to at least one format with an assigned editor should be enough to get started.)

Please use my contact form and mention this issue if you are able to give me access and I'll get back to you ASAP.

My site had a similar issue: rich text editing toolbar available only for administrator although it was available to an editor role before.

Apparently moving print $scripts out of the header section to just before the closing body-tag in html.tpl.php caused the problem.

<?php print $scripts; ?>

Moving print $scripts back into the header section solved it for my site.

Giving editors the 'View administration theme' permission also brought back the toolbar.

Other solutions did not work:

• uninstalling and re-installing CKEditor module
• use Wysiwyg module instead of CKEditor module
• downgrade CKEditor library to an older version
• tinkering with text formats
• give editor access to additional text formats (linked to Wysiwyg profile)

I figured it out and forgot to post up until now sorry for taking so long. I am up late tonight but i left my self a note to post my solution that i saved for it. it is a permissions issue with it not updating in sql you can update it manually or you can create a new "rank" and promote people to that.

farnswoth is right. You can solve this issue by creating a new role with the corresponding permissions for text formats.

On my system the problem was caused by an old version of firefox. To make sure that this is causing the problem try to access the affected form with chromium or another browser. If the ckeditor is showing up in another browser, try updating your firefox to the current stable release.

Here is another strange workaround: In .../admin/settings/filters assign all input formats to more than 1 role and the editor UI will also appear for authenticated users, not just admins (at least in OpenAtrium this worked for me).

svigneua posted on https://community.openatrium.com/issues/node/2561 "The Wysiwyg FCKeditor 2.6.6 is not visible when only one input format is authorized for a given user/role, but it is visible when two input formats are authorized. How can I have it visible with only the default input format authorized?"

@benhack, Looks like svigneua is/was using an old version of Wysiwyg (6.x-2.1), that problem should have been fixed in #950216: No editor for singular filter format, which is now part of the latest releases.
Which version are you using?

#4 Solved my issue as well.
Apparently moving print $scripts out of the header section to just before the closing body-tag in html.tpl.php caused the problem.

print $scripts;

Were there any JavaScript errors before you moved it back?
You always need to print &closure after &scripts, so the execution order is maintained.

I can confirm that I had a similar problem for all roles lower than user-1. Unless I enable the permission "VIEW THE ADMINISTRATION THEME" for that particular role the wysiwyg+ckeditor does not appear for that role.

Drupal 7.12
wysiwyg7.x-2.1+13-dev
CKEDITOR 3.6.2.7275
AdaptiveTheme 7.x-2.2+0-dev
Corolla 7.x-2.2+7-dev

Btw, you can use the settings in the "CSS" fieldset when configuring your editor profiles to specify which stylesheet(s) should get loaded into the editingarea. If the user doesn't have permissions to view the admin theme but the editor tries to load it anyway, it could get problematic.

Checking the View Administrative Theme permission fixed the issue for me. Thanks everyone for contributing!

I had this issue when upgrading from D6-D7. I believe it was a problem with the Better Formats module. I had to enable the permission for "Show format selection for nodes " before the editor would appear again.

@trickyricky26, that might be fixed by the patch in #934976: Provide method to hide input format fields without disabling WYSIWYG.

The admin theme permission should no longer be an issue once we've fixed an issue with how Wysiwyg picks the "active" theme. There are several theme related issues open and I don't remember in exactly which one this was discussed. Which theme actually gets picked depends on the value of a global variable from Core, which in D7 is either the front-end theme or the admin-theme. It wasn't used exactly the same way in D6 and this was overlooked when the port was made.

For now, if you have issues with the wrong theme being used inside the editor, try different combinations of the options available in the "CSS" section when configuring an editor profile. Usually, going with "Define CSS" and putting in a path to a stylesheet customized for your theme and the editor gives the best result, but it may take a little longer to get right.

I'm going to close this issue for now as the original poster found a way to fix the situation and we haven't heard back from others who said they had the same issue.

My problem sounded just like this! None of my authenticated users could see the body field for any content they had permission to edit. Admin could see everything. Wysiwyg (7.x-2.2+12-dev) and ckeditor (4.1.0.80c139aa) and AdaptiveTheme (Footheme). Checked everything listed above, tried changing the css from theme to editor default (in wysiwyg ckeditor profile). Then I thought again about all of those permissions in Organic Groups ....

There is one in OG Node (that would be things like ... Blog entry, right) Group Permissions: create, edit, delete for all of the content types enabled for OG (that's all of them at this point).

Maybe some day we can collect all of those permission settings from all of those modules and put them in one place ... maybe there is a module for THAT ....

I ran into this issue as well. To solve, I switched the formats order and moved "Plain text" to the top at admin/config/content/formats . I'm guessing it's a weight issue, but I didn't really look into it much as to the actual problem.

Got editor UI to appear. Just not sure this is intended behaviour, so leaving it open as a support request.

#17 fixed this in an Omega 4 subtheme. Thanks @ bwoods!

I got the same issue as mentioned above and I am running WYSIWG 7.x-2.2 with Ckeditor.

Currently I am bypassing the issue by giving users the permission to use the admin theme. But if you are still working on the issue I am more than willing to provide code/information. I also tried the solution in 17 but that did not work and I am not sure on if I properly tested the suggested CSS solution or if I messed up the paths as I am unfamiliar with tokens.

I fixed this issue changing permissions to files directory with chmod -R command.

Hope it help.

Hi,

In Drupal 7.38, I change the version of Jquery update to 1.8 and work it!

Hello,

#4 worked for me. All I had to do was enable authenticated users to be able to view the administration theme and the CKEditor toolbar appeared.

People > Permissions (tab)

View Administration Theme <- check this for authenticated user

Graham Leach

I have jquery update, for Alternate jQuery version for administrative pages, select 1.10 v. and this solved it for me.

Enable the permission "Access administration theme" worked. D7.53

same solution here on 7.67 core and latest wysiwyg module

Enable the permission "Access administration theme"

thanks everyone.

View the administration theme permission worked for me as well.