Validation causes script error in IE

Hi all,

I know form validation has been discussed many times in this forum, but I have not found anything specific to my case. I've enabled form validation and either using mootools or prototype validation, I always get the following error in IE:

Error: Object doesn't support this property or method

http://www.agentswelcome.ca/contact

This form works in Firefox, but not in IE.

Any ideas appreciated.

Thx!

Trev

Hi trevb,

Hard to tell I get the error showing as line 124 which appears to be the search module. Have you tried turning that off to see if there's a conflict?

Bob

Hi Bob,

Thanks for the reply. I've tried turning off all modules, and get the same results.

Interestingly enough, on the following form I get an error on line 29..

http://www.agentswelcome.ca/agent-resources/agent_registration.html

(this form is currently being worked on).

For whatever reason, validation doesn't seem to work. Perhaps everyone should use FireFox :blink: . While that would be idea, it isn't practical and I like the integrated validation provided in the engine.

Any other ideas would be greatly appreciated.

Cheers!

Trev B

Me again.

I loaded the default rhuk_solarflare_ii template and to my suprise the validation worked.

So, I'm assuming this could be the result of some kind of javascript conflict? Any insight on what I should be looking for?

Thx!

Trev B

Hi Trev,

Have you tried bot the mootools and Prototype validations libraries ?

Cheers,

Max

Hi Max,

Thanks for the reply. I have tried both, with the same results. Unfortunately the validation never takes place.

I've used javascript validation on another form that came as part as a component I purchased. It just seems limited to the built-in validation as part of the chrono forms.

Any other ideas greatly appreciated. I'd be happy to hack away at any advice you can provide.

Cheers!

Trev B

Hi Trev,

There's a file you can put on your site to give you at least the FireBug console in IE see here. It might help you diagnose this.

Bob

Thanks Bob. I've narrowed it down to the combination of template and and the built-in form validation. The error goes away if a disable form validation in the form options.

I'm sure others have run into this in the past. Any other solution short of using a different template?

Many thanks!

Trev B

Hi Trev,

Please open chronocontact.html.php and remove this line :

<script src="components/com_chronocontact/js/mootools-release-1.11.js" type="text/javascript"></script>

now, set the validation library to mootools and retest, any updates ?

Hi there,

Thanks for the reply. Unfortunately this made no difference. I still get the script error. I even get the same error if I chose the prototype library.

Any other thoughts?

Cheers!

Trev B

Hi all,

ANy other ideas? Or failing this, can I pay someone to poke around to try to isolate the problem? Or failing this, can I use regular Javascript to validate my forms (with the preference leading to the built-in validation).

Thanks!

Trev Burchett

Hi Trev,

I looked at your template source code, your joomlashack template is using prototype library, at the same time your ezrealty component using mootools, this is a conflict before going to ChronoForms, can you adjust your site modules so only 1 library is used and then use the same one with chronoforms then see if the error is gone ?

Let me know

Cheers

Max

Hi Max,

I very much appreciate your help on this.

You are correct. I've modified the templates index.php file and ran some tests. Essentially, I can use both validation types in IE now (mootools and prototype) if I remove the following from the EZ Realty includes header file:

script type="text/javascript" src="<?php echo $mosConfig_live_site; ?>/components/com_ezrealty/library/slimbox/js/mootools.js"></script>

This is ok, because I can live without the slimbox features. That being said however, having removed the reference to the mootools script used by EZ Realty, I'm puzzled as to why both validation types now work. I would expect mootools validation to fail with the call to this script, but why is prototype failing? I would expect that putting this back in that I'd still be able to use the prototype validation.

Any ideas?

Thanks again for taking the time to help Max. Love your component, and the support so far has been excellent!

Cheers!

Trev B

Hi Trev,

I cant understand, you mean that right now both validation works ? mootools and proto ? if so then whats the problem!!🙂

Cheers

Max

Hi Max,

Don't get me wrong, I'm quite happy to have either working. However having removed the reference to mootools in the EZ Realty header file, both validation types now work. So the question is when I leave this reference to mootools in the template index file, I would expect mootools to fail, but prototype to work.

Is this correct?

Many thanks!

Trev B

Hi Max,

Don't get me wrong, I'm quite happy to have either working. However having removed the reference to mootools in the EZ Realty header file, both validation types now work. So the question is when I leave this reference to mootools in the template index file, I would expect mootools to fail, but prototype to work.

Is this correct?

Many thanks!

Trev B

Hi Trev,

My guess is that there may be more than one version of mootools being loaded - I don't know if that would cause the problem though.

Bob

Hi Trev,

No worries, when you have different JS libraries used then some may work and others no, so, try this, make the reference to mootools at the template the same as the one called by ChronoForms, see if this will get both EZ and Chronoforms to work with mootools!

Cheers

Max

I will give that a shot and let you know the results.

Many thanks!

Trev B

I have the same problem. I'm using Joomla 1.5.1 and the latest Chronoforms.

The problem occurs only when I'm logged in the front end. For normal users (guests) the validation works fine with prototype or mootools using IE because it doesn't load the three admin-related scripts described below (i've modified my template not to load those scripts for guests because they are quite useless for them).

There's a conflict with mootools -script that Joomla uses. These scripts are loaded in front end admin:

<script type="text/javascript" src="/includes/js/joomla.javascript.js"></script>
  <script type="text/javascript" src="/media/system/js/mootools.js"></script>
  <script type="text/javascript" src="/media/system/js/caption.js"></script>

+ the form loads these:

<script src="/components/com_chronocontact/js/prototype.js" type="text/javascript"></script>
<script src="/components/com_chronocontact/js/effects.js" type="text/javascript"></script>
<script src="/components/com_chronocontact/js/validation.js" type="text/javascript"></script>

And the error I get (in Firebug):

el.$tmp has no properties
onShow(html)mootools.js (line 92)
(no name)(html)prototype.js (line 450)
_each(function())prototype.js (line 675)
each(function())prototype.js (line 449)
onShow([span.hasTip], Object maxTitleChars=50 fixed=false)mootools.js (line 92)
htmlElement()mootools.js (line 8)
(no name)()cv-pankki-lomake (line 19)
returns()mootools.js (line 21)
create(undefined)mootools.js (line 21)
fireEvent(function())mootools.js (line 50)
(no name)(function())prototype.js (line 450)
_each(function())prototype.js (line 675)
each(function())prototype.js (line 449)
fireEvent("domready", undefined, undefined)mootools.js (line 50)
domReady()mootools.js (line 59)
returns()mootools.js (line 21)
create(DOMContentLoaded )

IE gives the same error given earlier in this thread.

Edit: Ooops! a double post🙂

Post edited by: OCS, at: 2008/03/28 09:06<br><br>Post edited by: OCS, at: 2008/03/28 09:10

Hi OCS,

And why not use mootools of Chronoforms then ?

Hi OCS,

That's exactly why CF offers the choice of the MooTools or Prototype libraries - there's a drop-down on the Validation tab.

Bob