Closed (fixed)
Project:
Flash Node
Version:
6.x-2.2
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2008 at 09:43 UTC
Updated:
20 Oct 2008 at 00:03 UTC
I am using Flash Node and SwfTools. Everything works fine, except when I specify any flashvars that need to be passed to the movie
using FckEditor, the created content behaves unpredictable because of fckEditor rendering the input (adding some htm
's etc) iI suggest changing the input to a normal input field instead of a editor.
Comments
Comment #1
Stuart Greenfield commentedA different issue with FCKeditor and flash node was raised here. The solution described at #1 on that thead explains how to prevent FCKeditor from attaching to the flash vars field, and that should fix things.
Not sure what you mean by changing the input to a normal input field instead of a editor. The area is set as a multiline field on purpose to make editing easier, and by adding the FCKeditor exclusion described above you turn it in to a plain text field.
Let me know if this works.
Comment #2
IT100 commentedThanks Stuart, 'excluding' makes sure flashvars can be entered as plain text. That works! What I meant was that when I use fckeditor as flashvar editor the flashvars show up wrong in the swfobject.embedSWF( argument string) and the flashnode content doesn't behave correct thereafter (check javascript errors using firebug)
Comment #3
Stuart Greenfield commentedThe flashvars string will get "corrupted" if the editor tries to format it with line breaks or similar. I think I need to update the documentation to say exclude the flashvars field from FCKeditor in all cases (or maybe it can be automated).
It sounds like the exclusion sorted the problem, so as far as your error is concerned things are fixed?
Comment #4
IT100 commentedYes, it did!
Good idea to update the documentation.
Maybe you could also add an example of how to construct the parameters items (just being helpful ;-)
Thanks for the support!
Chris.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.