Advanced HTML Editor 3 Support Product Page

Form validation doesn't work with extension

Asked 20 Mar 2013 09:42:10
2
have this question
20 Mar 2013 09:42:10 Tim Pollard posted:
Hi

As well as the problem with the br method not working, I also find that form validation doesn't work with any field to which AHTMLEd is applied. For years I have been using Yaromat's extension for form field validation with no problem. However, when applied to an enhanced field it gives a 'can't find required form field' error, even though the name and id are correct.

So I went back to the standard DW behaviour and that does the same.

So it insists on using <p> formating, which I don't want, and it will let my users upload empty stories. Apart from that it's great!

Replies

Replied 21 Mar 2013 07:52:10
21 Mar 2013 07:52:10 Vulcho Vulev replied:
Hello Tim.

Note that the advanced html editor is html editor, any serverside code which is loaded within the editor text area will not work. The universal form validator itself use serverside validation (asp or php)and javascript validation.

You can achieve your goal for form validation if you create separate form outside the editor area which will submit as well with the content entered in the Advanced HTML Editor.

Can you describe your problems with the <p> formating a little bit more detailed?

Regards:Vulcho.



Replied 21 Mar 2013 08:36:41
21 Mar 2013 08:36:41 Tim Pollard replied:
Hi Vulcho

Thanks for the answer. I am not really sure what it is you are suggesting I do on the form validation? All I am trying to do is to ensure that there is some content (and not just the empty <p></p> tags the editor insists on putting in even if you don't type in any content. I therefore prefer Yaro's extension because I can specify at least 8 chars so that the empty tags don't work.

From what you're saying I can't set a dummy field to contain content onChange and validate the dummy field, so how can I do it?

On the <p> vs <br> problem, sometimes it seems to put in one and sometimes the other, even though it is set to <br>. There must be a pattern, but I haven't figured it out yet. I have to say, it is a real nuisance that the editor insists on putting in opening and closing <p> tags. I know I can remove them before entry by switching to code view, but I can't expect ordinary users to do that. It seems to me that this ought to be something the editor should let me customise to suit the rest of the site's formatting. All I really want to do is to allow non-technical users to use bold, italic and make links without hand-coding.
Replied 21 Mar 2013 13:12:23
21 Mar 2013 13:12:23 Vulcho Vulev replied:
Hello Tim.

Can you try the different enter handlings for formating in the user interface of the product?
Unfortunately there is no way to implement the universal form validator on the Advanced HTML Editor textfield.


Regards:Vulcho

Reply to this topic