a bug ?

CommentFileSizeAuthor
#8 Capture2.PNG26 KBadrianmak
#8 Capture.PNG29.84 KBadrianmak
#3 Capture.PNG15.82 KBadrianmak
Capture.PNG33.9 KBadrianmak
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pobster’s picture

I can only imagine that you've gone into the table content type and put a body label in?

Pobster

pobster’s picture

Status: Active » Closed (won't fix)
adrianmak’s picture

FileSize
15.82 KB

I have remove the body field from the table content type.

But neither existing table or new created table has a textarea shown in table entry form.

pobster’s picture

Sorry I think maybe your English is a little rusty? ;o) So... You say "But" and you also say that neither have the textarea, so does that mean it was the answer? If not, then maybe you've got a CCK field? I suppose the best way to see where it's coming from is to view the source of the page and check what the field is labeled? You can post it here if you're not sure what I mean.

Pobster

adrianmak’s picture

Sorry for my bad Egnlish.

I found that if WYSIWYG module enabled. The WYSIWYG textarea will show up.

pobster’s picture

Heh, no need to apologise - I just wanted to make sure the problem is still there!

I'll enable the WYSIWYG module later tonight and see if I can recreate the issue.

Thanks,

Pobster

adrianmak’s picture

Any findings ?

adrianmak’s picture

FileSize
29.84 KB
26 KB

I did a fresh drupal installation and enabled table manager module only.

An input format fieldset is attached on each table as shown on capture2.png

And it may be cause of the problem when enable and configure wysiwyg module, a textarea will show up. catpure.png

pobster’s picture

Apologies have been in weekend mode ;o) Thanks for the prod!

Yeah I got the same as you... I was going to look into how WYSIWYG does its replace on textareas (my guess is that it doesn't, it likely relies on the filters being present hence this issue) but again, weekend mode... I'm tempted to simply bounce this as it's an issue with WYSIWYG not Tablemanager... But then... I know this module doesn't really use the filters as they're supposed to be used, so I guess incompatibility is going to come from that. Still, I'll look tonight on how the replace is actioned and see if I can work out why the WYSIWYG module is misbehaving as this is a bit of a silly issue (in that it should never happen!)

Thanks,

Pobster