If I remove the body text area from a content type, I get a dialog with this error.

The TEXTAREA with id or name set to "" was not found if content type has no body

every time I try to create a new node of this content.
A workaround might be to use better formats to set the default input format for the content type without a body to a format with which no wyiswyg editor is associated.

Comments

alberto56’s picture

alberto56 commented

The workaround works as expected; however I suspect Wysiwyg is attempting to assign an editor to a non-existant text area when the body of a content is not present.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Postponed (maintainer needs more info)

How was the body removed? I suspect the format selector may have been left intact. (or set to #access = false) I can't test that right now though.

alberto56’s picture

alberto56 commented
Status: Postponed (maintainer needs more info) » Active

Hi, the body was removed by

Let me know if you need any more info,
Albert

sun’s picture

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

Duplicate of #466054: FCKeditor: Breaks on CCK textfield (not textarea) ?

sun’s picture

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

Sorry, I'm not able to reproduce this bug with the latest development snapshot.

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

arski’s picture

arski commented
Version: 6.x-2.1 » 6.x-2.x-dev
Status: Closed (cannot reproduce) » Active

Still have this same issue.. created a simple content type with just the title field, no added fields.. for input format "basic input", fckeditor 2.6.5. is enabled and under "basic setup" - enabled by default is set.. if I remove that, the error goes away.

I'll try to provide more info as I go along

arski’s picture

arski commented

well, having the editor enabled for basic input was the real problem in the first place. I disabled that on my client's site because it's useless anyway, but you might want to remove the error and/or the option anyway.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Issue summary: View changes
Status: Active » Closed (cannot reproduce)

I'm unable to reproduce this with the latest 6.x-2.x-dev and the steps mentioned earlier.
If there is no format selector on the page - and there won't be for the title field since it only handles plain text - Wysiwyg does not even add its scripts to the page.

If you're still having problems, feel free to reopen the issue.