TinyMCE removing submit button text

[donia]

Sorry if this has been answered before.  I have done a number of searches and haven't been able to find the answer.

Why is TinyMCE removing the value="Submit" part of my submit button code?  And more importantly, what can I do about it (besides make the button an image, which I think is overkill and shouldn't be necessary)?  If I type in this code: and then hit update, it removes the value.  The submit button default reads "Submit Query" and I only want it to say "Submit".  It's really annoying.

Thanks!

[Pierre M.]

Hello,

I'm not a Tiny expert. There is something I don't understand : Tiny is for wysiwyg and you are talking about writing code. What am I missing ? You should either write code (in templates) by end or write content with the wysiwyg. You can disable Tiny according to your profile (designer/editor in chief/conten writer...)

Pierre M.

[donia]

I alternate between using some of the wysiwyg features and writing code.  Therefore, I don't want to turn TinyMCE off.  It is my understanding that TinyMCE changes the code to meet standards, but why does it remove the value attribute?  It seems like it shouldn't be so hard to just label a button.

Thanks for any help.

[Pierre M.]

What are you trying to do ? Why do you need to put HTML FORM code in a wysiwyg place ? Could you put your FORM alternatively in a UDT ? Or would FormBuilder be too big for your use case ?
Pierre M.

[donia]

I don't need to put form code in a wysiwyg place.  That just happens to be how I use CMS Made Simple.  Putting it in a UDT is a solution, but it adds a level of complexity that just isn't necessary.  I've already got 15 UDTs.  It would be nice to just have the code on the page it is needed on.  For whatever reason, it deletes the value attribute, so I'll have to go with plan B, which would be the UDT.

[lwheelr]

You can put a form in a page, if you do it with the WYSIWYG turned off. Then you Save it. Problem is, if you edit that page again with the WYSIWYG on, you'll have problems because the WYSIWYG will strip out the active code then.

Here is how we handle it:

1. Go into your personal settings, and turn OFF the setting for WYSIWYG editor in Global Content Blocks.
2. Create a Global Content Block for your form, or your other dynamic code.
3. You can put the Global Content Block tag into your content page, with the WYSIWYG turned on, and it will show up nicely on the page (you'll just see the tag in the backend, but when you load the page in the frontend, your form will show). The Global Content Block tags will show up the same in the middle of a content area as they will in the template, so you can use them for an item that is in content just like you would in the template.

This allows you to edit your other page content independently of your form code, and to still manage your form code fairly easily in a Global Content Block.

It is the simplest way we've found for handling the issue of the WYSIWYG stripping dynamic code.

Laura
Firelight Web Studio