Form buttons

[kellyd]

I am having a couple problems with a form. When I make a textual change to the page the CMS removes the value from a hidden form field tag and removes the value='submit' from the submit button tag. All the other form fields are left unchanged but they don't have values so it looks to me like any form tag with a value defined has the value removed. Any ideas on how to stop this?

[admin]

Can you send me a copy of your HTML page (before editing) and I'll try to reproduce the problem on my test machine?

Thanks!

henri @ www.snippetmaster.com

[kellyd]

Any word on this? I have a couple of sites now that are being effected and two are e-commerece.

[admin]

Not yet.  I'm hoping to get this into the next release in a few days.  If not, then very shortly after.

[kellyd]

Been almost two weeks, isn't anyone else having the same issue? Any ideas for an easy work around til a fix is done?

[kennyr]

Hi there, my client is also seeing this problem when he tried to set up a Paypal shopping basket on his site.
Any one seen a solution to this yet ??

Cheers,
K.

[Patty]

I'm having the same problem on a client's site. Everytime he edits a page with a form button, the submit text disappears. Check it out: http://www.abemec.com.br/cursos.php

You can still click on what's left of the buttons and it will take you to the right page. But what about the "submit" text? It looks like a bug. 
Is there a fix for this yet?

[Jenkinhill]

There is certainly a problem using the tinyMCE editor (which is the editor plugged in to SnippetMaster) to edit forms. I suspect this is because the editor uses a text field as the editor window, which must therefore be enclosed within form tags. You cannot nest forms, so any content being edited that contains form tags will have them removed on saving, when the editor tries to convert all the code to valid XHTML.

It may be possible to edit the valid_elements file in the tinyMCE plugin to prevent removal of form related tags & attributes, but I have not needed to look at this as I only use SnippetMaster to edit "normal content" within XHTML pages.

[Patty]

Tks for your reply, but it really doesn't present a solution. I hope Henry can take a closer look at this and find a fix, so our clients can continue to use Snippetmaster.

Any ideas, Henry?

[Patty]

Henry?? Is there any way to fix this bug?
It's really messing up my client's site whenever he needs to use Snippetmaster to edit the page.

Please say something about it.
Thank you in advance.

[Jenkinhill]

I have tested editing a form after editing the admin/config page to include extended valid elements and it worked just fine. I did it about 10 times with different edits each time just to be sure!

The  HTML Code Validation & Cleanup Rule Sets were set to "Use full XHTML rule set" and the sollowing was entetered into the "Extended Valid Elements" text box:

Code:

form[name|id|action|method|enctype|accept-charset|onsubmit|onreset|target],input[id|name|type|value|size|maxlength|checked|accept|s rc|width|height|disabled|readonly|tabindex|accessk ey|onfocus|onblur|onchange|onselect],textarea[id|name|rows|cols|disabled|readonly|tabindex|acces skey|onfocus|onblur|onchange|onselect],option[name|id|value],select[id|name|type|value|size|maxlength|checked|accept|s rc|width|height|disabled|readonly|tabindex|accessk ey|onfocus|onblur|onchange|onselect|length|options |selectedIndex]

I think that list is probably overkill, but it worked - at least for me, with a valid XHTML1.0 strict page. I also tested using the limited XHTML rule set switch, also with the extra code, and that worked OK, too.

The only remaining problem is that the editor will stall if there is a <textarea> within an editable snippet, but I have heard a suggestion that it may be possible to define a special tag for a textbox within a form using XML. I won't be exploring that route as I don't use the editor on forms, normally.

[Patty]

Henry, still waiting to hear from you on this. Problem is still happening.
Is there any way to overcome this?

Awaiting your reply. Thank you.

[Ralyn-UTR]

I also need help with this topic - My clients don't know how to code, that's why they hire me, but they need to be able to put PayPal buttons on their pages. This problem almost makes it almost unusable by clients that want to offer items for sale - and puts me back to having to code it all for them.

Ralyn Schraceo
Under The Rainbow, Online Craft Mall
http://www.undertherainbow.us

[ddaudelin]

Hi Guys,

I've been having this problem too! I have a customer with a shopping cart which is driven by forms. She wants to do some minor price changes without my help. That's a reasonable request. However, Snippetmaster's editor, TinyMCE was not working as configured with forms.

It's been a really long time without any answers so I spent some time on the TinyMCE site today and was able to figure it out (for me at least)!

Snippetmaster comes standard with a set of standard "valid elements". However this set does not include forms. (Henri, you might want to add them?)

If I had been smarter (more knowledgeable?), I would have known that Jenkinhill figured this out way earlier. Anyway, there is a way to add them in yourself to get the forms to work. Earlier in this thread, Jenkinhill gave a set of additional valid elements that worked in their situation. However, it didn't work in mine.

So, I changed the set of additional valid elements to match my needs by following this set of rules:

http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements


To do this work, go to your admin screen in Snippetmaster. Scroll down to: HTML Code Validation & Cleanup Rule Sets.

Then select the last option: Use a custom HTML rule set.

This will open a box called, "Custom HTML Rule Set". You will find all the current valid elements (from the standard set) here. You just need to add the form elements that you use to the end of this set to make it work.


I was able to find what appears to be a complete set of "valid elements" for forms. You can add these to the end of the current set to have the maximum list. I learned a couple of things in doing this though:

1) Using the entire list makes the startup slow
2) You need to make sure that there are no "new lines" or "carriage feeds". The text needs to be one long line.

Here is the maximum list:

form[name|id|action|method|enctype|accept-charset|onsubmit|onreset|target|style|class|summary],input[id|name|type|value|size|maxlength|checked|accept|src|width|height|disabled|readonly|tabindex|accesskey|onfocus|onblur|onchange|onselect|onclick|required|style|class|summary],textarea[id|name|rows|cols|disabled|readonly|tabindex|accesskey|onfocus|onblur|onchange|onselect|onclick|required|style|class|summary],option[name|id|value|selected|style|class|summary],select[id|name|type|value|size|maxlength|checked|accept|src|width|height|disabled|readonly|tabindex|accesskey|onfocus|onblur|onchange|onselect|onclick|length|options|selectedIndex|required|style|class|summary]

To reduce the time for startup. I went into each section; form[], input[], textarea[], option[], and select[] and removed any that were not in use in my application. It made it load much faster!

I've not yet tried it with PayPal forms but will be doing that shortly for a new customer. Once I try it, I will report back. Unless, one of  you can do that and let us know how it works!

Cheers,

Dennis

[RayC]

Bumping this up from 4 years ago!

I've just run into this. Client updates PayPal Button using HTML editing function, and key information is stripped out rendering the button useless.'

I'm not comfortable creating a custom set of rules (as posted above) for fear of having too much that bogs everything down, or missing something that breakes the page.

I did not see any other resolution on this, not could I find any other thread.

Is there any way around this? Any guidance on which rules need to be modified to get a PayPal "Buy Now" button code to work when inserted?

Thanks.
 8)Ray

[heffleyd]

Most likely, there is a problem brewing with the use of that mce editor for the forms.  If looked at plainly this would be looking to be caused by the mere fact that the editor window is a very simple implementation of a text field which proves to be a liability in terms of getting them to work without tags.  That poses to be a level of problem when trying to convert the code to xhtml.