Closed (fixed)
Project:
YUI Rich Text Editor
Version:
5.x-2.6-96
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 May 2008 at 14:14 UTC
Updated:
12 Aug 2008 at 21:58 UTC
I originally posted here: http://drupal.org/node/253809
I am trying to add some code to my page and the YUI module is interferring with the formating of the code:
This is the code I paste into my page:
<swflist player="wijering_imagerotator"
files="image1.jpg&&image2.jpg&&image3.jpg&&image4.jpg"
width="400" height="400" transition="random">
And this is what YUI turns it into:
<strong>
<DIV class=codeblock><CODE><swflist player="wijering_imagerotator"<br /> files="image1.jpg&&image2.jpg&&image3.jpg&&image4.jpg"<br /> width="400" height="400" transition="random"></CODE></DIV></strong>
Any help would be greatly appreciated!
Comments
Comment #1
jeffcd commentedWhat are your yui_editor settings? What version of yui are you using?
Comment #2
jcbrew commentedHi - thanks for the reply:
YUI 6.x-1.1-1 YUI Module
YUI editor 6.x-1.2-91
No Path
No IDs
No Title
height: 250px
width: 100%
markup: xhtml
button profile: default
Checked:
Show titlebar
plaintest button
Show DOM
button type: simple
Comment #3
jeffcd commentedI have been trying to replicate the error with no success.
Two more questions:
- Which version of the YUI library are you using? I tried it with 2.5.0 and 2.5.1.
- What drupal input filter are you using on the body field?
Comment #4
jcbrew commentedYUI Library - 2.5.0
Do you mean the Input Formats? If so, I've tried it with all three Filter HTML, Full HTML, and PHP code...
I've tried pasting PHP code and HTML code in separate occasions and still get the formatted text instead of code...
Comment #5
vm commentedyou input format is exposed when you use the collapsed menu under the text area before submitting the node, or by setting a format as default in administer -> input formats
Comment #6
jcbrew commentedThank you for clarifying - I edited my reply above... I finally figured out what he meant - took me awhile...
Comment #7
jcbrew commentedI even tried typing
<b>Dog</b>figuring it was a problem with pasting the code...
and I get
Comment #8
jcbrew commentedI'm not sure if I should be downloading the library and storing it locally or if this location is good:
http://yui.yahooapis.com/2.5.0 or http://yui.yahooapis.com/2.5.1
Comment #9
jeffcd commentedTry posting the source html from the offending page so we can take a look at it.
Are you posting the html directly into the editor without going into plain text mode? If so, then it is doing what is expected.
Comment #10
jcbrew commentedSteps involved in creating my page:
Click "create Content"
Click on ""page"
Type title : Dog
Switch to Plain Editor >
Select Input format > Full HTML
Type:
<b>DOG</b>Hit Save
Then the body text field goes blank...
Here is the code to the page:
Comment #11
jeffcd commentedTry upgrading to 6.x-1.2-94 and the body field shouldn't go blank.
Comment #12
jeffcd commentedMy yahoo ID is jcd_7. i'll give you live help if I am online and have the time.
Comment #13
jcbrew commentedyui_editor 6.x-1.2-93 is the latest available I can download... I'll give it a try.
Thanks
Comment #14
jeffcd commentedNo posts have been made on this in a week so I am going to assume it is resolved. Re-open the issue with more details if necessary. Thanks.
Comment #15
WallyJtD commentedI'm having a similar problem with this editor; by going into plain text and setting input format to PHP, I can write code into the textarea, then save - and it displays. However, if I try to edit it, the edit function opens with the YUI editor in rich text mode, and if I switch to plain text, it's gone - nothing is displayed.
I have the php opener and closer correctly set; the php works because when the page was created and saved, it did what it was supposed to.
a) is there a way to force YUI editor to open in plain text mode if input format is PHP?
b) is there a way for YUI editor not to make any kind of parsing attempt on anything within the php tags?
c) has anyone else found this to be an issue?
TIA
Comment #16
jeffcd commentedI am going to move #15 to a separate feature request because I think it brings up some good points and it also is different from the original bug.