I have tried to read through the existing issues - but my case is a bit different - The editor does not show up at all!
I have installed it in two different sites, one a fresh install of Drupal 7 with WYSIWYG being the only additional module, and one in an upgraded version of Drupal 7 (with a few additional, existing modules - though WYSIWYG is new to this site). I have used this module on several Drupal 6 sites before and I am familiar with the install/configuration routine. On both sites I have installed CKeditor and TINYMCE - both show up as being installed correctly, I have configured the modules, created profiles for Full HTML, Filtered HTML and Plain text, added buttons, etc. I am using added themes but have also checked the problem using Garland. I have even checked to see if it appears in comments (as mentioned in a few posts above). While everything indicates that the module is working properly - it simply does not appear. I have confirmed this to be the case in Opera, IE9 and Firefox - I'm stumped.
On the advise of TwoD:
"Wysiwyg recently disabled a debug/fallback mode where editors would show their default toolbar instead of the buttons enabled under "Buttons and plugins" when no buttons had been checked. That could make it appear as if the editors aren't loaded at all.
So, if you create a new issue please enable just a few basic buttons first and look for errors in the script console. Also check if the "Disable rich-text" link is visible."
The editors had most buttons enabled, but I re-did the selection to only a few key buttons - same result. I have made this mistake in the past (Drupal 6) and a blank editor bar with no buttons would appear, in my case I'm not even getting that. The disable rich text button is also NOT appearing.
I tried installing the CKEditor module and have had the same results. NOt sure what/where the script console is but I did notice the following log entries corresponding to my attempts to re-do the button selection:
page not found - /misc/jquery.cookie.js?v=10
| Comment | File | Size | Author |
|---|---|---|---|
| #35 | language-disables-editor.gif | 81.12 KB | thomaslausz |
| #23 | greenshot_2011-03-31_13-34-20.png | 24 KB | MCautreels |
| #14 | tinymce.jpg | 146.24 KB | SMartin |
| #10 | drupal.settings.wysiwyg.jpg | 94.23 KB | wcsinn |
| #10 | confige-triggers.jpg | 124.77 KB | wcsinn |
Comments
Comment #1
wcsinn commentedComment #2
sunThis most likely means that you uploaded your files via FTP and some files were not properly created on the server, or the file permissions are incorrect, so the files cannot be accessed through the browser.
Comment #3
wcsinn commentedActually no, I uploaded the tar files the first time by ftp but unpacked them in place on the server. I have subsequently uninstalled and removed the files and replaced them through the new drupal 7 add module feature. I have checked server permissions and they look ok, most files being 755.
What are the chances I have a bad tar files? Thinking of redownloading the module uninstalling and trying again.
BTW - now that I think about it - the module was unpacked on the server but the actual editor files were uploaded via ftp. Going to get new downloads of the module and editor and try again.
Comment #4
wcsinn commentedOK, removed the old WYSIWYG module and ckeditor files. Downloaded new tar files of the module and ckeditor. Installed the module through drupal and unpacked the new ckeditor tarball on the server. Checked the profiles (buttons turned on), checked permissions (drupal - I do have permission to edit, add, delete pages etc). I rechecked server permissions - both directories (and most subdirectories) are set at 755 but most .js files are at 644.
Comment #5
sunwell, your problem starts way earlier:
This is a file in Drupal core, not Wysiwyg or CKEditor.
Comment #6
wcsinn commentedOh great - so you're saying its a bad drupal install? Damn, but thanks so much for the quick response.
Any way to fix this without a complete reinstall of Drupal? The actual file is there and appears to be correct.
Comment #7
twodJust making sure the file is possible to download via the browser should be enough, basically the same file/folder permission check you did for Wysiwyg and the editor should take care of that. If the file is damaged/unparsable, simply re-uploading just that file is enough as long as you make sure it's from the same Drupal core version.
Comment #8
wcsinn commentedTwoD - thanks, but no joy! Permissions on that file were (are) the same as all other javascript files - 644. I no longer seem to be getting that error msg (guess that's a good thing) when I alter WYSIWYG profile settings, but I still have no editor.
I tried disabling and re-abling WYSIWYG, ran update again (can't hurt) and even changed a couple of profile settings - nada!
I am not even getting a blank or empty bar at the top of the body window - while everything in the admin section shows it installed, enabled and apparently working, (shows CKEditor as the chosen editor, profiles exist, plenty of buttons selected, etc.) going to any add content or edit page simply looks like a bare install. I have checked on - Full HTML, Filtered and text settings - all appear the same - no difference and no editor.
Any other ideas guys - I'm getting desperate here. Thanks for all the help so far.
BTW - I went ahead and overwrote the entire install (with the exception of the entire sites directory) after untarring a new download of Drupal 7.0 - no difference.
Comment #9
twodIf you use Firebug for Firefox, Firebug Lite or a similar tool to inspect the DOM (easist to do without the Overlay), is there anything in Drupal.settings.wysiwygs? The settings generated for each editor profile should be in the configs objects and there should be "trigger" objects for each format selector/field id.
If not, Wysiwyg's clientside scripts are never triggered.
All of Wysiwyg's scripts are currently loaded from the start, check if wysiwyg.js, wysiwyg.init.js and the relevant editor scripts from wysiwyg/editors/js are loaded, and of course the corresponding editor scripts from sites/all/libraries/editor are there. Not all of the editor's scripts are loaded before it's activated.
You might want to set breakpoints in wysiwyg.js to see what happens during initialization. The attach() method in the editor-specific Wysiwyg scripts need tp be called for an editor to ever activate. If script execution never reaches that point, something's wrong with the trigger data Wysiwyg created when inspecting the form. If files are not loaded at all, Wysiwyg might never have found the format-enabled fields in the form, or thought they were disabled.
Comment #10
wcsinn commentedTwoD
I want to thank you for all the help - but I am afraid we have gone a little over my head with the last suggestion. I do have Firebug, but I'm not sure why since its beyond my skill set. Yes - there is data in drupal.settings.wysiwyg - see attached.
I believe I captured the right data for editor profiles and triggers - see attached. I am assuming that the client side scripts have been triggered?
I am afraid I don't know where to look to see if wysiwyg.js, wysiwyg.init.js and the relevant editor scripts from wysiwyg/editors/js are loaded - sorry.
What can I do to get you the correct info?
Comment #11
kacifant commentedComment #12
wcsinn commentedDon't know how this got tagged fixed - it is not, so thanks - but this is Drupal 7.0 issue not 6x.20.
Comment #13
SMartin commentedHi,
I'm having exactly the same issue. (I'm using D7. It seems to say V6 here...)
Neither TinyMCE or CKEditor seem to load. I have tried both stable and dev versions of the editors and Wysiwyg with the same result. I'm not even getting the "enable/disable rich text" link.
I'm not getting any error messages at all. The editors both show in the wysiwyg profiles page and I have activated a few buttons for both full and filtered html and assigned then to show as default.
Would love some advice :-)
(Edit) I'm not familiar with Firebug but looking at the DOM tab there, TinyMCE is listed twice.
I'm on OSX 10.6 using Mozilla & Firefox btw...
Thanks
S
Comment #14
SMartin commentedI'm just exploring Firebug...
See the attached image. I'm seeing 'activeEditor' as 'Null'.
Is that correct?
S
Comment #15
SMartin commentedI have miraculously managed to solve this issue in my installation...
More or less by a complete fluke, I found that the contents of the 'misc' directory at the root of my Drupal install had only partially uploaded to the server.
I re-uploaded the folder and things changed quite dramatically all over the place :-)
I now see the rich-text editor.
Hope that helps someone :-)
S
Comment #16
twod@SMartin hehe, that explains a things. Missing scripts, even those not used by the editor directly, can cause errors to be thrown which stops script executcompletely or cause a cascade of other problems. The empty activeEditor in TinyMCE is just because no editor has been given focus.
@wcinn. The settings look correct. The Net tab in Firebug would show missing files as red and with a 404 status code, or perhaps another code if it could not be read. Clear the cache, enable the Net tab and reload the page to make sure all files are included (those loaded from cache may be skipped).
If you're still having problems, I could perhaps help you debug it directly on the site, just drop me a line using my contact form if you want me to have a look and I'll get back to you ASAP:
Comment #17
jaymckinsey commentedI had the same problem and solved it by clearing the cache in the performance section.
Comment #18
mcaudy commentedI had the same problem, but followed jaymckinsey's advice and "flushed all caches" from the admin_menu. That worked, and "wysiwg" now shows up on the /admin/config/content
page.
It's amazing how many problems are solved by clearing your caches.
@jaymckinsey: thanks very much for sharing your method for solving this problem!
Comment #19
triple5 commentedJust now I have been trying to make tinyMCE show up, for me it was the language setting which messed things up, I had selected German as interface language in the Editor Configuration menu and this didn't work...
The language file has to be uploaded separately.
Comment #20
mcaudy commentedI also added the CKEditor. After following the instructions in the README for the Drupal module, everything worked.
Comment #21
saepl commentedI was having problems with it not showing up so I disabled the module, ran cron, cleared cache, enabled the module, ran cron and cleared cache and now it shows up.
Comment #22
twodFor the record, I'm still waiting for wcinn's response to #16. If you sent me a mail I probably missed it, please send another one.
Linking in #1046062: Drupal 7, wysiwyg 7.x-2.0 and TinyMCE 3.3.9.3 not working for reference here (solved by clearing caches and checking file permissions, but that was already checked in #4).
Multiple editors have been mentioned here, so moving it out of the TinyMCE component.
Comment #23
MCautreels commentedI have a similar problem.
Everything shows up perfectly only the buttons to control the layout don't show.
There's only some kind of separator visible if I use CKEditor.
So all editors work except for their control buttons.
I've attached an image of my Drupal.settings.wysiwyg object in Webkit Dev Tools.
Thanks in advance.
Comment #24
saepl commentedI also noticed that the WYSIWYG editor only shows up if you are editing the page with the overlay. This means that if you go to www.example.com/admin and then create or edit your content you don't get the WYSIWYG editor, but if you create or edit the page when you have the editing overlay (the lightbox type thing) then you will get the WYSIWYG editor - or this just may be how it works on my install. It was driving me CRAZY that the editor was sometimes there and sometimes not. Now at least I know when it's happening
Comment #25
Anonymous (not verified) commentedComment #26
oranges13Came to say the exact problem - fixed by clearing caches and running cron. DOH!
Comment #27
MCautreels commentedEven after clearing cache and running chron my buttons are still not showing.
So the text got his layout but there are no buttons to for example: make the selected text bold.
So the scripts work but none of them shows their buttons!
Anyone any idea?
Comment #28
twod@MCautreels, I'm assuming you enabled a couple of buttons under "Buttons and plugins".
I recently saw an issue where the toolbar images had become corrupt due to a wrong transfer mode setting in the person's FTP client. Can you try re-uploading sites/all/libraries/ckeditor with a different transfer mode if you're using FTP?
Comment #29
brightbold@wcsinn: I don't know if you're still reading this thread, but the misc/jquery.cookie.js "page not found" error does not actually indicate a corrupt installation. More likely, it's a problem with mod_security on your server. See #522646: jquery.cookie.js incompatible with Apache mod_security by default, #306889: Fails to load jquery.cookie.js (hosting problem), http://drupal.org/node/1017612, and http://drupal.org/node/1052372 for more information.
Comment #30
harmlessdrudge commentedWriting as a new user of drupal (7):
I was surprised to find that, despite installing the WYSIWYG module correctly (AFAIK) and installing an editor, I had no buttons on the tool bar. Reading here (having searched with Google for why this might be the case) furnished the clue that somewhere the buttons needed to be added, and I duly found the place to do this.
But, really, what a counterintuitive default: to have click on dozens of buttons, and then to have to do this repeatedly to try out the look and feel of different editors.
Surely it would be useful to be able to select and unselected all buttons, and for all buttons to be selected by default initially?
I appreciate that to some extent that this may be in the domain of the editor but even so, unless I have contributed unwittingly to this bizarre default, it would be good to see a better default imposed.
Popularity indications for the editors would be nice too, if possible. For what it's worth, I found ckeditor buggy (remove some buttons and the toolbars don't display properly) and I settled for now on TinyMCE which works and looks good.
Comment #31
twod@harmlessdrudge, what you're asking for already have their own feature requests: #698348: Check / UnCheck All Option (won't be needed once we get #277954: Allow to sort editor buttons), there's also #1006072: Provide some kind of default toolbar that is similar to each editor's default and related issues.
Popularity indications would be interesting, but we currently have no way to measure that. Tracking similar to what the core update module would perhaps be possible, but it would only be valid for Drupal sites with Wysiwyg module.
The CKEditor toolbar was probably buggy due to button sorting being missing, see #829266: Fixing toolbar for the CKeditor / Using the settings hook for a workaround that won't require hacks to Wysiwyg itself.
Comment #32
unegro commentedSimple,
I had a headache to solve this problem, but it's too easy:
Flush Cache,
Run Cron,
Uninstall Module
FLUSH CACHE
Run cron
Install Module again, and...
PIMBA, it works.
I used the administration menu, more complete than the original administrative menu in drupal 7
Comment #33
unegro commentedI Presume it's fixed...
2 weeks no reply...
Thanks
Comment #34
mesr01 commentedI was having the same issue and, like triple5, changing the profile's language back to English brought back TinyMCE.
Comment #35
thomaslausz commentedsame here
When I change the Interface Language in
/?q=admin/config/content/wysiwyg/profile/full_html/edit
/?q=admin/config/content/wysiwyg/profile/filtered_html/edit
from Englisch to Deutsch (german)
the editor will not show in my own content type/field
If I change it back to englisch, all back to normal. ;-)
Gif Animation attached
Comment #36
baskin commentedI have the opposite problem. My editor (TinyMCE) is disappearing when i enable "Aggregate JavaScript files". As soon as i disable it the editor is coming back but i need this feature to solve other issues with my theme (and for performance).
I have tried any possible solution in this thread (and others) with no result.
Comment #37
baskin commentedI have also tried with different editors, without success. Also i'm testing with the default theme. As soon as i enable "Aggragate JavaScript files" my editor disappears.
Comment #38
twod@baskin, do you see any errors in the browser's JavaScript console when aggregation is enabled?
Aggregation requires all aggregated scripts to be very well formed and have all semi-colons in place. Since aggregation basically turns all scrips into a single huge script a syntax error in any of them will prevent the browser from executing them at all.
The line/column an error is reported on when aggregation is enabled is often unhelpful for most debugging purposes since it may be different in each installation and won't correspond to the correct lines in the unaggregated files. But if there is a syntax error, examining the area near the reported location of a syntax error should reveal at least in which script there may be a problem. Function names are often good orientation markers since they don't change during aggregation/minimization so if you see one near the reported location, please post it here.
Comment #39
baskin commentedThank you for your answer.
My debugging knowledge is limited so i will try, but i will need some guidance for this.
On Firefox's "Error Console" i'm getting some "illegal character" errors like the following:
and only one:
When i click on the jQuery error it gives me the following line:
Hope this is helpful. If it is not, please guide me how to provide more information.
Thanks in advance.
Comment #40
brineblank commentedI have checked, unchecked, cleared, uncleared...used overlay, not used overlay...done all the steps listed above that is work for others...but still no editor...
I am using the book visual quickstart guide...I downloaded the newest version with the security feature today...7.7...the book (page 93) listed to make a library file inside of /sites/all/module and I could not do that because module file was not an option and I never got the wisywyg function to work...I installed the library in sites/all and got the appropriate 'options'...I have no error messages at all. The editor just will not pop up like it should...
I am on a new macbook pro...
Any help would be appreciated
Comment #41
twod@brineblank, I'm sorry but much of your second paragraph make little sense to me.
Wysiwyg has no version 7.7 and I have no idea what book you're talking about. Which module file and library file and wysiwyg function are you talking about?
No files other than Wysiwyg module's complete folder should be extracted into sites/all/modules, without modifications. The editor library package should be extracted into sites/all/libraries without modifications.
If you don't mind, can you please send me a link to your site and a username/pass via my contact form and I'll take as soon as I can. I would normally not ask for this info so quickly, but when there are no error messages I often end up having to dig into the problem myself simply because it's a lot quicker than walking someone through the debugging process via the queue (that'll most likely take days or even weeks).
@baskin, the first error is indeed a syntax error. The second one most likely happens because the jQuery object was in the process of being defined when the first error happened, so it was never completed.
I tried to access the javascript file you linked to in the first error, but it's no longer around so I assume the hash in the filename has changed. Would you mind reproducing the error, save that aggregated script file and upload it here? It should not contain any sensitive information since it's just a composition of public files used by the various modules.
Then I can probably see exactly why the error happens and perhaps which file should be fixed.
Comment #42
spainisdifferent commented#19 That solved my problem, thanks!!
Comment #43
zwoelfgrad commentedPerhaps it helps. In my case the ckeditor didn't appear because the "window.CKEDITOR_BASEPATH" variable was set incorrect in the head. Completly remove the variable solved the problem.
A quick and dirt workaround in the html.tpl.php:
Comment #44
twod@zwoelfgrad, what was it set to?
Wysiwyg does not currently set it, maybe you need the patch from #356480-91: Lazy-load editors, which does set CKEDITOR_BASEPATH?
Comment #45
zwoelfgrad commented@TwoD
it is a strange behaviour. On a blank drupal install all works as expected. after enabling some modules the script appears in the head and breaks the editor. I couldn't figure out which module causes this error, but I think it is the "Drupal for Facebook" module (actually in a *.dev). On another site I have enabled the same Modules, expect fb, and all works as expected. But disabling the module has no effect, the uninstall returns an error.
The problem with this small script is, that it obviously don't consider the base path.
In my case:
<script>window.CKEDITOR_BASEPATH = '/sites/all/libraries/ckeditor/'</script>and perhaps it should be:
<script>window.CKEDITOR_BASEPATH = '/DRUPAL_ROOT/sites/all/libraries/ckeditor/'</script>But as I said, the code isn't neccesary at all, removing it and the ckeditor works.
Comment #46
qpro#17 Works for me, thanks!
Comment #47
twodBaskin from #39 and brineblank from #40 have not returned with more information so I assume those issues was resolved.
I do not know where zwoelfgrad's problem comes from, as Wysiwyg does not add
<script>window.CKEDITOR_BASEPATH = '/sites/all/libraries/ckeditor/'</script>to the page. The only module I know which does something like that is ckeditor.module, which shouldn't be used together with Wysiwyg module as they are incompatible in general.Hence, reverting this back to fixed.
Comment #49
dirckdigler commentedI has the same issue, the editor wysiwyg does not show up in the browser firefox, and I have used this module on several Drupal 7 sites before and I am familiar with the install/configuration routine. After to follow all the instructions of this foro, I realized it was disabled javascript in firefox, so in this link explain how to activate javascript in the browser: http://www.enable-javascript.com/es/