I searched the bugs and didn't see my exact problem. I have installed wysiwyg 7.x-2.x-dev as well as ckeditor_3.6 and nicedit .9. I installed wysiwyg through drupal's "install new module", enabled the module, and followed the editor installation by downloading, extracting, ftp'ing editors into /sites/all/libraries/xxx.

I then edited the wysiwyg profiles and enabled ckeditor for content type "easy format" and nicedit for content type "filtered html". I then enabled a few buttons & plugins on each to try them out. I left the other settings as default. The editors work without the overlay, but won't show up with the overlay.

i.e. Both editors work if I go to edit a page via: /node/19/edit?destination=admin/content
however, they do not even appear when I try to edit the same page via: /city_departments/commissioner#overlay=node/19/edit

Any help would be appreciated.

Andrew

Comments

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Title: Editor not showing up » Editor not showing up with overlay
Status: Active » Postponed (maintainer needs more info)

Do you see any errors in the browser's JavaScript console (with overlay)?
Which browser(s) have you tested with, does the same thing happen in all of them?
If you're using CSS/JavaScript aggregation/optimization/minification, have you tried disabling them?
Do you see the "Disable rich-text" link when using the overlay?
Do you see the original textarea, or nothing at all, where the field should be when the overlay is active?
Have you tried using Firebug for Firefox or a similar tool to investigate the HTML structure where the field/editor should be to see if any markup related to the editor is there?

andyl29’s picture

andyl29 commented

Same result in both firefox 4 and chrome. I have the following enabled (checked): verify html, convert tags to styles, remove linebreaks, and force cleanup on standard paste. Rich text toggle link is disabled. I see the originial text area.

Because of this error I have simply disabled the overlay part of drupal core in the modules section.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

Ok, but can you please answer the other questions as well or I'll never be able to find out what causes this issue?

andyl29’s picture

andyl29 commented

Yes, sorry. I do not know what these questions mean:
"Do you see any errors in the browser's JavaScript console (with overlay)?
If you're using CSS/JavaScript aggregation/optimization/minification, have you tried disabling them?"

And I have tried using firebug but I'm not sure what to be looking for.

Sorry for the lack of knowledge, let me know what I need to do to clarify the problem

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

No problem.

Firebug has a "Console tab". Click the "clear" button in it, then reload the page when Overlay is enabled and watch for any errors being listed and copy them here. If no red lines show up, there are no errors. If JavaScript optimization is enabled (see below) the listed filename and line the error shows up on won't be helpful since all scripts are in merged into one huge file.

In Drupal's Performance page you can toggle whether JavaScripts and stylesheets should be combined into a single file on the server before being sent to the browser. This can sometimes cause errors if scripts are missing semi-colons or can't be read. Disable these options and try looking for errors again. If errrors happen now, they'll have the real filename and line number listed.

Firebug also has a "Net" tab listing all file request your browser makes when loading a page. Clear or disable the browser's cache and reload the page to see if any file is listed in read with a HTTP Status code other than "200 OK". That indicates missing or unreadable files on the server.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Sorry, without further information this issue can only be closed as not reproducible.

Feel free to re-open this issue if you want to provide further information. Thanks.

arcaneadam’s picture

arcaneadam commented
Status: Closed (cannot reproduce) » Active

Just as an FYI to anyone else who ends up here.

I pulled a Drupal Gardens sites and then ran updates on some of the code but not wysiwyg, leaving it at version 7.x-2.0. I then ran into this same problem on at least chrome and FF. Upgrading to 7.x-2.1 version of WYSIWYG fixed the problems.

So this may have been a bug in older version but seems to be fixed in newer version.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

michaelfavia’s picture

michaelfavia commented

Subscribing as affected party. Need to research cause and solution.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

If this problem is still present in the latest release (and/or -devs), could those affected by it please answer the questions from #1 and change this back to 'active'.

michaelfavia’s picture

michaelfavia commented

This issue is a symptom of another bug with the DHTML menu for me and i imagine for others as well. That module is throwing a JS error and stopping the execution of WYSIWYG JS in its tracks. A number of other modules are affected and the issue with a functional patch is here #1130250: JS error with admin overlay screens. Leaving closed and tracking upstream.

roadran422’s picture

roadran422 commented
Status: Closed (fixed) » Active

The same thing is happening to me, I wonder if it's wysiwyg's problem or my theme. This happens when I try to edit or post a comment also happens when I need to add a new page to my wiki module. This is what happens.

http://imgur.com/rBGMzC2

Do you see any errors in the browser's JavaScript console (with overlay)?
Yes,
Failed to load resource: the server responded with a status of 400 (Bad Request) https://fonts.googleapis.com/css?family=bodega+Serif:400,400italic,700it...
Failed to load resource: the server responded with a status of 400 (Bad Request) https://fonts.googleapis.com/css?family=bodega+Serif:400,400italic,700it...
Failed to load resource: the server responded with a status of 400 (Bad Request) https://fonts.googleapis.com/css?family=bodega+Serif:400,400italic,700it...

Which browser(s) have you tested with, does the same thing happen in all of them?
Chrome

If you're using CSS/JavaScript aggregation/optimization/minification, have you tried disabling them?
I don't understand.

Do you see the "Disable rich-text" link when using the overlay?
Yes, see picture.

Do you see the original textarea, or nothing at all, where the field should be when the overlay is active?
I don't understand.

Have you tried using Firebug for Firefox or a similar tool to investigate the HTML structure where the field/editor should be to see if any markup related to the editor is there?
I don't understand.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Closed (fixed)

@roadran422, the problem you're seeing is very different. The editor does work in your case, as apparent in your screenshot. Your problems has nothing to do with the Overlay being active or not. That explains why you don't understand the other questions.

The "Failed to load resource" errors are not caused by Wysiwyg module or the editor. It looks like you may be using a module which requests fonts - or images of text using a font - but Google's server does not like those requests.

The problem with a chopped off toolbar happens because Wysiwyg currently puts all buttons in a single toolbar group. We're working on fixing that and you can test the code by checking out the sort_buttons branch from the git repository. (Click the Version control link at the top of the project page and follow the instructions.) Or you can try to apply the latest patch from #277954: Allow to sort editor buttons to the 7.x-2.x-dev snapshot and then re-arrange the buttons when configuring your editor profiles.