Home » Site Building Guide » Working with user-generated content » Editor, Filter and WYSIWYG modules » Wysiwyg module

FAQ

· · · · ·
Last modified: September 10, 2009 - 19:20

Overview

Installation

Configuration

Third-party module integration

Installation

Q: I got it working for Garland, however, when I switch to my custom theme it says "Drupal is not defined" ?

A: Please ensure that $scripts is output before $closure in page.tpl.php of your theme. Also make sure your page.tpl.php in your theme contains print $closure somewhere at the bottom. Without this theme area the module will not work.

Q: I'm getting a Javascript error "u.indexOf is not a function" when viewing a page that should have TinyMCE on it.

A: Did you recently install the fbconnect module? Facebook Connect's Javascript is known to cause this error.

Q: Why do I get "Object doesn't support this property or method" in IE7, no matter what editor I use with Wysiwyg?

A: The Chatblock module is known to cause this problem. Try disabling it for add/edit pages in its block configuration. Lootz Item Filter also causes both of these issues (even when not being used for the Wysiwyg Input Format).

Q: Why does SVN prevent me from committing after installing FCKEditor 2.6.4 in wysiwyg/fckeditor?

A: The default permissions for the folders in the fckeditor folder may not allow SVN to create its necessary .svn folder. Set the correct permissions on the fckeditor folder and its subfolders BEFORE adding the folder via 'svn add'.

Q: Why is the editor properly displayed in FF and Chrome, but not in IE6/IE7/IE8?

The editor works properly in FF and Chrome, but in IE it is not styled at all. The box/frame appears, but it is not looking how it should.

A: Internet Explorer (IE6/IE7/IE8) has a hard limit to only load ~31 CSS files on a page. Enable CSS aggregration under Performance settings (admin/settings/performance) to see whether that helps.

Configuration

Q: How do I select a different installed editor? The box is disabled.

A: Click the Remove link to the right of the Edit button. This will remove the editor profile linked to that input format, but not the input format itself.
It is then possible to select any installed editor. This was needed since editors can't use the same profiles and it was not obvious the settings would be lost when selecting a different editor.

Q: Images are not displayed in output

A: Add <img> to the HTML filter (Administer -> Site Configuration -> Input Formats) to allow the tag.

Q: Where can I add a new Input Format?

A: This is located in Administer > Site Configuration > Input Formats. You can click the Add Input Format link at the top. Then when you go to Administer > Site Configuration > Wysiwyg, your new Input Format should be listed there.

Q: I selected a different language than English and buttons only display "advanced.something" as titles now?

A: You have to download the corresponding language package. Example for TinyMCE: http://tinymce.moxiecode.net/download_i18n.php

Q: Since i have updated to the latest development snapshot there is only a white textfield instead of the wysiwyg-inputbox, any ideas why?

A: Try to switch your language settings in your wysiwyg-profile settings.

Q: When looking at the source code of the final page, some HTML tags are missing?

A: Most likely, this is because you have the "HTML filter" enabled in your input format and it is configured to not allow the tags you mentioned. Please go to admin/settings/filters and check your input format configuration, especially whether HTML filter is enabled and how it is configured for the input format you associated with an editor.

Q: When looking at the source code of the final page, the expected HTML tags are present, but the formatting is missing?

A: Your theme may not implement styles/formatting for the HTML tags in question, or it overrides the default styles of the browser. Please test whether it works when switching to one of Drupal's stock themes like Garland. If it does, you need to fix your theme. You might just need to add

p {
  padding-bottom: 15px;
}
strong {
  font-weight: bold;
}

to your style.css.

Q: When looking at the source code of the final page, I see tags like [img]...[/img] or [color=#123456]...[/color] instead of the expected HTML

A: Disable the BBCode plugin in your Wysiwyg profiles. It makes TinyMCE - or other editors which supports similar plugins - output BBCode markup instead of regular HTML. Without installing and enabling a BBCode input filter for the corresponding input format Drupal won't know it should turn those tags into regular HTML so they're rendered as plain text.

Q: I want to create my custom styles such as "My Heading Style" available in "Styles" or "Font Styles" dropdown list. How?

A: Define CSS styles at Administer >> Site Configuration >> Wysiwyg >> [choose Wysiwyg profile] and EDIT >> CSS >> CSS classes.

Q: Why are font changes like color or size in TinyMCE not applied to the final output in the "Filtered HTML" input format with "HTML filter" enabled, even when HTML filter is configured to allow FONT and SPAN tags?

A: In your wysiwyg profile for "Filtered HTML" TinyMCE profile, you will see a setting that reads:

Convert <font> tags to styles
If enabled, HTML tags declaring the font size, font family, font color and font background color will be replaced by inline CSS styles.

Make sure you disable this setting. By doing so TinyMCE will use font tags when creating the HTML (as opposed to style tags which are blocked by HTML filter). Note: You will have to go back to any posts you made while you had this option checked, clear the formatting and re-do your fonts,size and color under the new font tag setting. Do not let general users have access to "Full HTML" as a quick fix. This makes your site vulnerable and lowers the safety of your users data.
Source: #400216: TinyMCE & Filter HTML not allowing font changes.

Q: Why isn't the TinyMCE Editor showing up?

A: In your wysiwyg profile for the input format you are using, try disabling all but a few basic buttons. Test to see if the editor is visible now. If so, there is simply a problem with one of the buttons you had enabled (most likely a more advanced one). You can re-enable the buttons now one-by-one to find out which work and which don't.
Source: #418990: Can't Toggle Between Input Formats (TinyMCE)

Third-party module integration

Q: Page displays code (ex: [img_assist|nid=6|title=Testing|desc=|link=none|align=left|width=640|height=640]) instead of image

A: Under Administer -> Site Configuration -> Input Formats edit the filter(s) that applies and make sure the "Inline Images" box is checked.

Q: Images are uploaded and counted as available in the "Add Image" popup, but no thumbnails are shown

A: The issue I found was that I had already created a content type called Image before installing the image/image assist modules which caused problems with field names and types (obviously). This caused the thumbnails to not show AND caused the images to not show on the post itself (see above issue)

Q: How do I configure Lightbox2 to work with images posted with wysiwyg/image assist

A: Go to Administer -> Site Configuration -> Lightbox2 -> Automatic Image Handling -> Image Node settings. Automatic handler is lightbox, display size is the size you want shown 'in' lightbox. The part that confused me a little due to the wording is the "Image trigger size". This basically sets which size image will trigger lightbox, selecting only thumbnail will only trigger lightbox on thumbnails, not preview or custom sizes.

Q: Why does the Image Assist pop-up (when clicking the camera icon) display my site's front page / homepage?

A: You have set up a redirect from index.php to using the Path Redirect module. You may have set this up to prevent index.php showing on your homepage. This kind of redirect is generally not a good idea, and you should delete this redirect.

Q: When trying to insert an image using the "Add image" link/button below the textarea/editor, I'm getting a JavaScript exception

uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLTextAreaElement.selectionStart]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: img_assist/img_assist_textarea.js?z :: insertToEditor :: line 90" data: no]

A: The Image Assist link or button below the editor should be disabled (via Image Assist's settings page) when using Wysiwyg API. Instead, you should enable the "Image assist" plugin in your wysiwyg profile(s). Afterwards, you will see a "camera" icon in the editor toolbar.
Source: #388146: Won't attach with TinyMCE enabled.

Q: Excerpt Module: I can't get a WYSIWYG editor to attach to the Teaser field generated by the Excerpt module

A: The Excerpt module does not use a unique Input Format for the teaser field it generates. Instead it shares the Input Format of the Body field. WYSIWYG requires a unique Input Format in order to work for each field. It is suggested to use either the Teaser Break plugin instead, or create a unique CCK field if you need completely customizable teasers.

» Login or register to post comments
 
 

Drupal is a registered trademark of Dries Buytaert.