Closed (fixed)
Project:
Wysiwyg
Version:
6.x-2.x-dev
Component:
Editor - TinyMCE
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
27 Mar 2010 at 11:52 UTC
Updated:
10 Aug 2011 at 00:11 UTC
I was using tinymce editör with its own module. But when I have installed WYSIWYG API module and then tinymce the editör does not appear. There is no difference between browsers in all of them it does not appear. What should I do?
Versions are: WYSIWYG 6-x 2.x dev Tinymce 3_3_2
Comments
Comment #1
twodHave you looked through the FAQ?
Did you double-check that you followed the Installation instructions?
Is the editor listed as installed on admin/settings/wysiwyg?
Is the listed editor version number correct or does it say that the version could not be detected?
Are you seeing any errors when trying to use the editor?
Are you using a custom theme? It must print the $closure variable near the end of the page.
Have you tried with the Garland theme?
Comment #2
DrewMathers commentedI have an identical issue. I have checked all the items in #1. Interestingly I have two site, one where TinyMCE works perfectly, and one where it doesn't show up.
Both are:
Drupal 6.16
TinyMCE 3.2.5
Wysiwyg API 6.x-2.1
I have tested with identical sets of contrib modules enabled and used the Garland theme. All testing done with the Page content type.
Curiously, where the editor does not show, there is still a link to "Disable rich-text".
I am open to suggestions as to what else to compare between the working and non-working sites.
Comment #3
DrewMathers commentedAs an additional test, I copied the TinyMCE directory from the working site to the non-working site. Still no change.
Comment #4
twodCan you check (using Firebug for FF or a similar tool) that the script files are loaded properly?
There should be at least wysiwyg.js, wysiwyg-init.js, tinymce-3.js from Wysiwyg module, and then the TinyMCE files themselves.
The "Disable rich-text" link showing does indicate that Wysiwyg has tried to load an editor.
If there are no errors in the JavaScript console (FF: Ctrl+Shift+J), this may actually be a styling problem (editor loaded but invisible). If this only happened in IE, I'd suggest checking that you haven't hit its "max 31 stylesheets" limit by enabling "Optimize CSS" on the Performance page but this appears to happen in multiple browsers.
Could you also make sure all the CSS files are loaded as well? Any missing or otherwise un-loadable file should be listed with red text in Firebug's Net tab (clear cache first to see all files).
Comment #5
3cwebdev commentedExact same issues here. After spending hours troubleshooting I finally installed TinyMCE 3.3.1 and it is working. Must be an issue with 3.3.2?
Comment #6
mikebann commentedI had this issue as well and I think the latest version of tiny mc does not work with the wysiwig api. I jsut used an older version and Bob's your uncle.
Comment #7
twodI'm using 3.3.2 without any problems. 3.3.2 is just a bugfix version without any changes that should affect how Wysiwyg module's implementation is able to handle it.
From the official TinyMCE changelog.txt.
As I'm not able to reproduce this I'm unable to debug it. If any of you are willing to give me access to a site where this happens I'd be happy to look into it when I have time.
Use the contact form on my profile (and please mention this issue) if the site does not have public content creation access (just access to anywhere the editor is supposed to appear is enough).
Comment #8
DrewMathers commentedTwoD,
Checking the FireBug Net tab solved it. I had the WYSIWYG Spellcheck module enabled, but had not installed that plugin code to the designated location. When WYSIWYG Spellcheck couldn't find its executable, it prevented the editor from loading. This behaviour only affected FireFox, it always worked OK in IE.
As soon as I disabled WYSIWYG Spellcheck, TinyMCE started loading properly in FireFox. I also tested compatibility with TinyMCE 3.3.2. It seems to be OK.
Even though this is caused by WYSIWYG Spellcheck, I think this issue should remain in the WYSIWYG support queue because that is people will search for the problem symptoms. I have opened a feature request in WYSIWYG Spellcheck asking them to check for the presence of their plugin files. #755592: Test for presence of plugin before loading JS
Comment #9
twodThanks for the report Drew!
As we've not yet heard back from preper, I'll leave this issue open for a while longer.
Comment #10
preper commentedSorry for late.. I check every thing and all the things are normal.. In the settings page i can see tinymce 3_3_2 is installed. I have also tried 3_3_1 version but there is no change...
I am using newswire and page.tpl has closure tag. Moreover I tried garland theme there is no change again. Every time I cleared cache.. I have controlled with firebug script is not loading..
There is stiil problem. I can not see tinymce...
Comment #11
sun1) Which JavaScript files are specified/loaded in the HTML of the page? (don't forget to look into the footer)
2) Did you try to remove your profile for TinyMCE and re-add a new one?
Comment #12
preper commentedLoaded scripts are google analytics, user relationships popup and google adsense. I tried remove profile and add new one. This time i can see a different form, it is tinymce but buttons are not displaying. Only a white space instead of editor.
Comment #13
sunPlease post the actual scripts you find in your HTML output.
Comment #14
preper commented(removed by sun)
With these scripts on the page I can see the editor with firefox but can not with IE.
Comment #15
twodI think sun meant just the names (and locations) of the scripts. Either way, could you please wrap the above code in a <code></code> block to stop filters from interfering with it?
Comment #16
preper commentedWhy sun didn't take the codes into ''
block nothing is shown. But you know the contents of these scripts: Google adwords, analytics, user relationship popups and alexa pulu.. These are general for everyone.
Comment #17
twodIf you don't mind, I could take a look at your site and try debugging it. I'd just need an account with permissions to create nodes or comments with the relevant input format. You can use the contact form on my profile to send account info, please mention this issue.
Comment #18
preper commentedComment #19
DrewMathers commentedpreper,
It would help if we could see a screenshot of what you see under the Net tab in Firebug. Especially any lines that show up in red.
Comment #20
SecCon commentedWell I have the same.
I followed the FAQ and disable all editing options in Tiny but for BOLD and left it like that. Also using 3.3.2 version
I do get a database warning when trying to disablt Tiny in Wyswyg:
I am using drupal on a subsite, if relevant, I have not been able to make it load in Garland, let alone the theme I am supposed to use.
I used Firebug as recommended and get a http:500 error.
It fails loading a JQuery from
http://showbusiness.conram.com/sites/default/files/js/js_d541a260ddfb6f307f5267d720298fd9.jsHow can that be when I have TinyMCE installed at ../showbusiness/sites/all/libraries/tinymce/ ?
I also get
in FF Java Console.
I FOUND THE ISSUE!!
(I think)
I had Optimize Javascript Files in Drupal / Admin / Performance enabled.
After disabling it the lots works.
I just love helping my self by posting to a bug forum...;)
Hope this helps others!!
:D
PS And it works in the site theme as well, LiteJazz...
Comment #21
twod@Homdax, I think that may be a different issue. Wysiwyg should not be able to generate that HTTP 500 error, as it isn't really involved in the process of generating and serving the aggregated .js file, other than marking some of them for exclusion. The main TinyMCE library file is one of the files which we've decided not to include when scripts are aggregated, simply because there were one or more errors when doing so. (The latest version of TinyMCE may be possible to aggregate, as noted in code comments, but we're taking the safe route and excluding it for now.
@preper, a quick update: I did get your message and I will take a look at your site when I have time to do so. I'm sorry I've had to postpone this so long.
Comment #22
SecCon commentedOk. Understood. No big bug there then... ;)
Comment #23
Breakerandi commentedSame problem here. I just tried a fresh install of tinymce 3.3.2 with wysiwyg latest dev. Editor doesn't appear...
Comment #24
Breakerandi commentedI have now tried several versions of tinymce, really old versions, newest,.. always the same problem:
WYSYWIG Api says it is installed proberbly, but on node edit page nothing appears, just a normal text area.
I have tried different settings in admin/filters and also in the wysiwyg filter settings...
Does anybody now another wysiwyg editor a table button and rows and cols add buttons ?
Comment #25
Breakerandi commentedI got the same problem with openWYSIWYG 1.4.7...
It's a fresh drupal installation with garland theme... really strange...
Comment #26
twodRe #24, I think at least CKEditor and FCKeditor have good table controls, haven't used them in a while though so I don't remember which one is best. Their official demo sites should give a good idea.
Re #25 OpenWysiwyg not working is a known [unrelated] problem, see #713942: OpenWYSIWYG broken, jWysiwyg needs jQuery 1.3+.
Everyone still having issues with the editor[s] not appearing,
let's start over and please try to answer these questions. We need to find out what you have in common and I can only do that with very detailed replies (or rather, simple answers to very specific questions).
Thanks for your patience.
Comment #27
garbo commented@TwoD
1. yes, faq checked. Solution nt found
2. installation followed thoroughly tried with WYSIWYG 2.1 & 2.0 and TinyMCE 3.3.3 & 3.2.7
3. the editor is listed properly with all tested versions
4. correct
5. no errors
6. n errors
7. nothing strange
8. using a sub thee based on ZEN
9. it works in Garland when I use WYSIWYG 2.0 and tinyMCE 3.2.7. It doesn't work in Zen though.
10. tried to optimize css and js, together and apart. It doesn't help
11. no
12. no scripts added manually
For the record: I'm using drupal 6.16. I think it has to do with the drupal version because this configuration worked fine in drupal 6.15
Hope this info helps
Comment #28
garbo commentedHere are some of the warnings in firefox:
Comment #29
twodThose warnings should not be a problem and the changes between Drupal 6.15 and 6.16 didn't affect anything Wysiwyg relies on. It is interesting though that it works with Garland but not a Zen subtheme. It suggests either that some scripts are not loaded (btw, $closure must be printed inside the <body> tag, I've seen some themes putting it after the body), or maybe that some styling interferes and makes the editor invisible (it's actually loaded and should be possible to find using Firebug's HTML tab).
Comment #30
garbo commented$closure is inside the body tag at the bottom of the page.
And TinyMCE didn't work in the original ZEN theme neither, so it's not just my custom sub theme.
The strange thing though is that on another install TinyMCE works fine. Also on Drup 6.16
Comment #31
nflowers1228 commentedNot sure if this helps, but I can't get TINYMC or CKEditor WYSIWYG editor to work on one of my sites since the 6.1.6 upgrade of Drupal on my one site that is a subtheme from the Zen starter kit. It does work on another site that used the BlueBreeze 6.x-1.x-dev theme. I don't know if that provides any clues. I'd be happy to give access to one of the sites if that helps, but please contact me directly.
Comment #32
twod@nflowers1228, please look at the questions in #26. If it works with one theme, but not with the other, it's guaranteed to be a problem with the first theme. Specifically check that $closure is printed in the body and the number of stylesheets don't go above 31 (if problem only appears in IE).
Comment #33
nflowers1228 commentedThanks, I did some uninstalling and reinstalling and it's working now.
Comment #34
pokadan commentedWe have a similar issue.
This happens when assigning TinyMCE 3.3 editor to Full HTML input format.
When assigning a similar profile to a different input format the editor works correctly and buttons pop up.
We've tried to recreate(delete, create againg) the wysiwyg profile but that did'n help.
Changing version from TinyMCE 3.3.3 to TinyMCE 3.3.6 didn't help.
Disabling JS aggregation does help but that is not what we want to do.
Comment #35
goosemagoo commentedI had same/similar problem and a lot of searching indicated Imagepicker was the problem. Either disable the whole module or uncheck (in the image picker options) the content types where the problem occurs. Dunno why but works for me.
Comment #36
ssafiullah_h commentedWYSIWYG problem fixed for me........
let me tell what making the WYSIWYG to disappear for me...
in mymodule_form_alter().........
i removed the line
if(my custom node type)
unset($form['body_field']['format']);
but now I have to find some other way to hide/disable 'Input Format' on Create Content pages( for my few custom node types )......
Comment #37
twodBetter Formats module will help you with that, simply remove the permission to use the format tips for the roles which should not see them.
Comment #38
hnln commentedFYI, I had this issue when I changed the language in the dropdown of the wysiwyg profile page.
Comment #39
twodYes, changing the language may disrupt TinyMCE if not all of its plugins also have the corresponding language packs.
Comment #40
mot commentedI have a similar (but not the same) problem. But it might be somehow related:
#832784: Tinymce disappeared with WYSIWYG
Please note that I had WYSIWYG appearing, but after some actions, it disappeared. Those actions are related to two nearby modules (IMCE, IMCE Wysiwyg bridge) which might be connected to this tickets reports here as well.
Comment #41
sunSeveral different issues got resolved in here. It's impossible to tell which problems are still unresolved and which are resolved.
Thus marking as fixed. If you still have an issue, then please search the queue for already existing support requests before creating a new one.
Comment #42
DrewMathers commentedIn many of the cases above, it appears that one or another cause prevented the browser from loading some script file before the editor script was loaded. It is possible that browsers may stop loading subsequent scripts if a previous one fails to load.
Comment #43
RichieB commentedI just tried to get TinyMCE 3.3.9.1 working with WYSIWYG 6.x-2.1. The first hurdle was that I had to increase the fgets() parameter in tinymce.inc since the version string is now at 115 chars:
$line = fgets($script, 200);The problem I am having now is that TinyMCE works just fine in IE8, but is not shown in Firefox 3.6.10. All javascript files are loaded: wysiwyg.js, wysiwyg-init.js, tinymce-3.js, tinymce.js, etc. There are no javascript errors or warnings but TinyMCE simply does not show.
The same thing happens with TinyMCE 3.3.2 and 3.3.8 (I just tried a few). The opposite happens with 3.2.4.1: it works with Firefox, but does not work with IE8 (javascript errors). Sigh.
Comment #44
twod@RichieB, the version string problem will soon be fixed in -dev snapshots, see #695398-36: Support for TinyMCE 3.3. That alone made TinyMCE show up in FF 3.6.10 for me.
Not sure about the other non-loading issues you're having. Mind creating a new issue about this?
Comment #45
RichieB commented@TwoD: never mind, I fixed it. Gallery 2 Image Chooser 3.0.3 was using tinyMCE.addToLang() (TinyMCE 2.x style) instead of tinyMCE.addI18n(). Support for tinyMCE.addToLang() was dropped in TinyMCE 3.3. I changed tiny_mce/plugins/g2image/langs/nl.js from
to
and now TinyMCE 3.3.9.1 is working in IE8 and Firefox 3.6.10.
Comment #46
melon commentedI was happy to see that 3.3.x is supported now and it seemed to work fine.
However I found that this (TinyMCE 3.3.9.1, running with wysiwyg-6.x-2.x-dev) completely breaks CCK filefield behavior when Vertical tabs is installed. The problem is that when you upload a file to a CCK filefield/imagefield, it never finishes upload, it only shows the throbber forever.
With either Vertical Tabs disabled or switching back to any TinyMCE version before 3.3.9.1 (even 3.3.9 will do fine) the problem goes away.
Firebug console says on tinymce.js:
j is undefined- this happens as soon as I hit Upload in the filefield widget.What do you think, is this a Vertical tabs, a Wysiwyg or a TinyMCE issue?
Thanks.
Comment #47
twodIn either case, please file a new issue about it. We can't solve all TinyMCE related problems in a single support request or bug report, it just makes things too confusing.
Comment #49
yan commentedFYI: In my case I moved the $scripts to the bottom of the page (which I think is recommended), but after $closure, which led to TinyMCE not showing and Firebug telling me "jQuery is not defined". I put it before $closure then, and everything works fine again.
Comment #50
ksmith911 commentedI had to turn overlay module off to get any text editors to work!
Comment #51
twod@ksmith, see #1170940: Editor not showing up with overlay. Please follow up there and answer the questions from #1.