Hi, I have installed chronocomment on site and love this component! I’m trying to use it with mootols 1.2 and it isn’t working. I heard that version of joomla 1.6 will come mootols 1.2. So I was wandering if there is any hack to use chronocomments with mootools 1.2?
Personally I'd be inclined to switch validators if you use Mootools I.2. ChronoForms uses a MooTools port of the Dexagogo 'Really Easy Validation' library. There's a much better port for MooTools 1.2 at Clientcide.
There is a 1.2 compatibility pack that you can add - it's not perfect but might do the trick. (There are some unofficial but more extensive compatibility packs somewhere - maybe at clientcide?).
Try getting the clientcide forms validator from here - downloads without MooTools. Rename it to mooValidation.js and drop it in place of the current mooValidation.js file in com_chronocontact/js
This is supposed to be a MooTools 1.2 port of the valdation code that ChronoForms use - so, if we are lucky it will be a drop in replacement. If we aren't lucky then it shoudl just need a few tweaks in the core code . . . fingers crossed.
Please let us know how it goes.
Bob
PS Max: this looks like a much better port than the one we are using at present and has some added functionality like an option to validate un-displayed fields which coudl be useful with tabbed forms.
This looks fantastic yes, thank you very much! beside the validation I really like all the built in fancy functions too!! I will take a look at it once I'm done from updating the wizard...
however, mlajo's question is about ChronoComments, because mootools 1.1 is used in all the AJAX code used by ChronoComments, so the only way to fix this is to wait for the new version!
I have installed chronocomment on site and love this component! I’m trying to use it with mootols 1.2 and it isn’t working. I heard that version of joomla 1.6 will come mootols 1.2. So I was wandering if there is any hack to use chronocomments with mootools 1.2?
Not as far as I know - what doesn't work??
Personally I'd be inclined to switch validators if you use Mootools I.2. ChronoForms uses a MooTools port of the Dexagogo 'Really Easy Validation' library. There's a much better port for MooTools 1.2 at Clientcide.
Bob
when you click at submit button nothing heppen..
There is a 1.2 compatibility pack that you can add - it's not perfect but might do the trick. (There are some unofficial but more extensive compatibility packs somewhere - maybe at clientcide?).
Bob
No idea here too, when .6 is out I will have to convert the code to be 1.2 compatible!
Regards,
Max
ChronoForms7 Video Tutorials
Try getting the clientcide forms validator from here - downloads without MooTools. Rename it to mooValidation.js and drop it in place of the current mooValidation.js file in com_chronocontact/js
The docs are here.
This is supposed to be a MooTools 1.2 port of the valdation code that ChronoForms use - so, if we are lucky it will be a drop in replacement. If we aren't lucky then it shoudl just need a few tweaks in the core code . . . fingers crossed.
Please let us know how it goes.
Bob
PS Max: this looks like a much better port than the one we are using at present and has some added functionality like an option to validate un-displayed fields which coudl be useful with tabbed forms.
This looks fantastic yes, thank you very much!
however, mlajo's question is about ChronoComments, because mootools 1.1 is used in all the AJAX code used by ChronoComments, so the only way to fix this is to wait for the new version!
Warm regards,
Max
ChronoForms7 Video Tutorials
Thanks Max, sorry Mlajo
Note to myself: you ***must*** look to see which forum you are in!!!
Bob
No problems!
Best regards,
Max
ChronoForms7 Video Tutorials