I'm not sure if this is a bug, or that I have something somewhere set wrong. In any case, I have a few nodes that contain JavaScript code within them that worked fine with the Input Filter of Full HTML. After installing WYSIWYG 2.0 module to add support for the FCKEditor (2.6.4.1), these no longer work. Any help on this would be appreciated!

Comments

twod’s picture

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

If the script is still there if you use the link to disable the rich text editor it's not a problem with Wysiwyg module. If it's not, there might be a problem with the editor itself. Wysiwyg module does not filter anything out on its own, but maybe it should pass different settings to the editor or change the way it interacts with the editor.

Which browsers does this happen in?
Does it also happen with Wysiwyg 2.x-dev?
Do you have any 'Drupal plugins' plugins enabled like Teaser Break or Image Assist?
Do you have any native plugins enabled which might cause this?

IreneKraus’s picture

IreneKraus commented

Script is still present when the Rich Text editor is disabled. So, perhaps it isn't an issue with WYSIWYG.

> Which browsers does this happen in?
Present in all browsers I've checked (Firefox 3.53, IE 8.0.7100)

> Does it also happen with Wysiwyg 2.x-dev?
Haven't tested this, as this is a live site. Is it stable enough for testing there?

> Do you have any 'Drupal plugins' plugins enabled like Teaser Break or Image Assist?
Teaser Break is enabled, as is the IMCE Bridge

> Do you have any native plugins enabled which might cause this?
No

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

2.x should be stable enough for that yes, but if you have any doubts, it's always better to set up a separate test site. I don't think you should need that tho as the script is still present after disabling the editor, so it's probably an input format/filter setting or something else filtering it out.

Is the script still there if you save the node and edit it again? Can you see it in the source code of the viewed node?

vm’s picture

vm commented

FULL HTML doesn't support javascript as far as I can tell in my testing over the past few months with or without wysiwyg.module

I have found that to use javscript in the body of a node I need to use the php input format, provided by the core phpfilter.module.

I think the idea here may be that javascript isn't HTML whether FULL or FILTERED. Javascript isn't PHP either, but the risk would be equal where it concerns both of these languages.

If this isn't the case, then my installations are broken in some way.

off to install a fresh D6.14 to check the default behavior

IreneKraus’s picture

IreneKraus commented

> Is the script still there if you save the node and edit it again? Can you see it in the source code of the viewed node?

Yes, and yes. Odd thing is, the Javascript for a mess of other things, the Digg module amongst others, works just fine. Driving me nuts as to why the script worked before but isn't now. Same code I've been using for years to generate a pop-up window. No warnings - BTW - about a blocked pop-up window either, so I've narrowed my search down to that aspect of the code...

IreneKraus’s picture

IreneKraus commented

RE: Idea of using the PHP filter

Didn't think of this, but enabled that and tried it. No joy still. <*sigh*> Going to do some tests with the JavaScript code in a traditional web page to see if it still works on its own...

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

If inline STYLE or SCRIPT tags are vanishing, then this means that you still have HTML filter or some other security filter enabled. Not caused by Wysiwyg, sorry.

IreneKraus’s picture

IreneKraus commented
Status: Closed (won't fix) » Closed (fixed)

Sorry for not getting back on this sooner as I'm still undergoing cancer treatments and have been dealing with some very bad adverse reactions... At any rate, did resolve the issue within the editor after a more careful examination of the code involved.