Editor does not save

i just installed and have same issue. created New Content page, entered text, uploaded image. when i view the text/image inside the editor, i see it just fine. it sames my tags, image, etc. yet when i preview or save, it seems to strip all my tags and the image. i am left with just plain text?!?!?

Exact same problem here- it just doesn't save.

Here's my actions:
1. Downloaded both YUI Rich Text Editor from here http://drupal.org/project/yui_editor and downloaded YUI module
2. Uncompressed and uploaded both into my Drupal modules folder
3. Went to my modules in the admin and activated both
4. Create or Edit a page, modify with the YUI interface, and Save.

NO CHANGES SAVED. Page stays the same.

I will look forward to hearing the result of this issue. Thanks!

Yes, make sure page "Input Format" is set to "Full HTML", you can set globally from Administrater > Input Formats then select FULL HTML.

this is what fixed my issue... hope it helps!
-o

I had previously tried Full HTML and it still doesn't save. I went ahead and tried it again and made the default full html- it still doesn't work.

Other ideas?

Reporting the same.

Same issue at my end.

Read that the issue may be because the coder or plain text is enabled, so disabled that. Then enabled full HTML, but still doesn't work. Does not save. Does not preview.

Using the online version of Yahoo! APIs.

Please help!

I'm completely stumped. I did not change a single thing, but it just started working again on its own...

There's no way it could be a browser cache problem, could it?

I'm having this problem with the YUI module (both stable and dev) but only in WebKit based browsers (i.e. Chrome and Safari). It works fine for me in IE, Firefox and Opera.

Thanks for pointing that out! I can confirm it doesn't work in Safari 4 beta but works on Camino…

For me, it didn't work in any browser. Not in IE 7, Firefox 3, or Chrome.

I installed today with hosted API files from Yahoo.
Coder plugin and image upload activated.
Works perfect!

I installed today with hosted API files from Yahoo.
Coder plugin and image upload activated.
Works perfect!

We have seen that when we edit in the Plain Text Editor the editor will not save properly unless we switch back to the Rich Text Editor first. This is with Full HTML enabled.

The first click on save seems to wipe changes in the editor unless you have switched back to Rich Text Editor.

It is able to save on a second save click while in Plain Text mode. E.g. edit, click save, edit again, click save and the save works.

Firefox 3 & IE 7

I am also having problems with saving content in the editor, here are my experiences... in the hope someone can see any clues on how to solve this issue..

I have several node types defined, with textarea's (cck fields, I don't like using body fields).

Not all node types are having this issue. I can save contents without any problems in nodetype-X, but nodetype-Y is behaving strangely.

In nodetype Y, when i create a node, i get the message ' field is required!' even if i did type some content in the field. On submission however, it seems like the content has been erased.

When changing the contents in that field in an existing node (using the rich text editor), the changes are not saved on submission.

However, if I hit the plaintext button once (or switch back to rich text afterwards), the content is submitted correctly.

I'm having same issue with Safari & Omni - Firefox & IE are ok.
Just want to keep track.

I am also finding not saved in Chrome. OK in IE7, Firefox.

Finding the same problem in Chrome. Firefox and IE7 OK.

Same here, can't use Safari. Firefox is ok.

It APPEARS that Chrome and Safari have some sort of problem with the YUI WYSIWYG editor for me, as well.

If I turn YUI WYSIWYG editor off I can create topics and save them with no problem.

I've pinned this down a little. It seems to relate to fields not validating properly... (also see post #15 above).

In Chrome/Safari (WebKit browsers), one is returned to various fields without an advisory -- but they have asterisks. In some cases, as with forum locations of posts, the multi-choice pulldown selector resets to the top/null option every time.

So, if the user wants to *trick* the editor into saving, he must reset the pulldown selector to the correct forum location and then postion the cursor in one of the other asterisked fields and hit the return key (in the case of a forum post, for instance).

At least that's what I've pinned down so far. (And not likely to go any farther now that I've broken down and set up FCKeditor, which I like much better.)

It's a bit of a drag because otherwise, the YUI editor works pretty nicely and was certainly easy to set up. But... if it doesn't work in Chrome and Safari, that's pretty much a deal killer, y'know?

ADDENDUM: It's not as slick setting up -- but FCKeditor works and, in some significant ways works considerably better, even beyond the apparent WebKit bug in YUI Ed described above. (I'm still a bit confused about how the FCKE install is supposed to go but I got it done; getting image uploading [I'm using IMCE] took a few hoop jumps -- watch the details.)

But now that it's set up -- it's really nice and really flexible. I can give user tiers their own level of complexity of functions/menus as well as differing access to site resources like images -- so content creating users can have access to images on the server but I can also let unathenticated visitors like potential clients upload sketches or other images for RFQs without having to create an account. Of course, you probably want them to authenticate so you don't waste your time on trolls, but, well, it's nice to have the option.