Forums

I'm guessing lots of people are having this problem, so I thought I'd put it up here. I recently upgraded to Joomla 1.5.19 and Chronoforms (3.1 RC 5.5) isn't really working at all.

I sent in an email and Max wrote back:

"Unfortunately yes, the latest Joomla version has Mootools 1.2 and the form wizard is using the Mootools 1.11 (the official Joomla 1.5 mootools version), I think there is a switch some where to use the mootools 1.11 somewhere ? I didn't try the latest version yet."

I've looked around in joomla's global configuration for a mootools setting and am not seeing anything. Anybody have a way to get this working?

Thanks in advance!

Hi ironlion37,
I have'nt played around alot with the 1.5.19 update yet, but from what I can read (and experienced myself sofar), the site would not use MooTools 1.2 unless you explicitly enable the "System - Mootools Upgrade" plugin. Could you doublecheck that you havn't enabled this plugin by accident?

/Fredrik

Hi ironlion37,

If I understand correctly the upgrade to Mootools 1.2 is an optional plugin. The simple answer is to leave it disabled, then the old MooTools library should continue to work OK. See the Jooms Docs here and a helpful RocketTheme article here.

I did get most* of ChrononForms front-end working successfully under MooTools 1.2 a few months ago for this site which has re-sizing background driven by MooTools 1.2. When I have a moment I'll check out the changes I made.

The back-end Wizard is much more complex and that is unlikely to be upgraded soon.

Bob

* It was a site with just a single form so I only fixed the files I needed.

PS There has since been a 1.5.20 release but this seems to be only a fix with the installer package in 1.5.19.

Hi ironlion37,

I've installed 1.5.20 and looked at the MTUpgrade plugin. It is indeed optional and comes disabled.

I've found a small hack that will let you run MooTools 1.1 in the back-end and 1.2.4 in the Front end if you need to.

Open plugins/system/mtupgrade.php and find the onAfterInitialise function at the end (line 46). Then change the function to this:

	function onAfterInitialise()
	{
		global $mainframe;
		if ( $mainframe->isSite() ) {
			JHTML::addIncludePath(JPATH_PLUGINS.DS.'system'.DS.'mtupgrade');
		}
	}

This will let the ChronoForms Wizard run OK in the back-end under MooTools 1.1. while enabling MooTools 1.2 in the front-end.

Bob

PS You need more fixes for ChronoForms validation to run under MooTools 1.2 in the front-end.

Hi Bob,

could you please post which changes you made for the Validation to Work under Mootools 1.2 ?
I am using some Javascript in my Site which requires 1.2 , and the Server Side Validation works,
but I'ld prefer the Javascript Option.

thanks,
Mario

Gosh darn, I wish I had seen this earlier. Updated from Joomla 1.5.15 to 1.5.20 today; Chrono forms is dead in the water. I'd prefer not to modify the code as who knows what other effects this could have now or down the road.

Any idea when a ChronoForms update might be available to remedy this?

Hi pseconds,

ChonoForms has no problems under 1.5.20 *unless* the optional MooTools Upgrade Plug-in is enabled. If you choose to do this then ChronoForms (and some other extensions that use the MooTools library) will not run correctly.

Go to the Joomla! Extenstions | Plug-in Manager find the "System - Mootools Upgrade" plug-in and disable it and ChronoForms will run again.

Bob

Thanks Bob! I'm good now. I missed the piece about disabling the mootools upgrade. I did that and it works fine. I appreciate the speedy help!

Hi pseconds and all MooTools 1.2 users,

No problem, I'm starting to wonder if the upgrade plugin isn't being enabled on upgrade (it isn't if you install a new site).

I have now dug out my code and there are actually only a few changes needed to get the front-end of ChronoForms running under MooTools 1.2.4.

[list]

You **must** first apply the hack to the upgrade plug-in I posted earlier in this thread.

Then replace components\com_chronocontact\js\jsvalidation2.js and components\com_chronocontact\js\customclasses.js with the attached versions (unzip it to access the files).

[/list]
There are only a few changes in the file, in each case they either remove .$tmp or this code (or something very similar)

$ES('input', $(chronoformname)).each(function(field){

is replaced with this

$(chronoformname).getElements('input').each(function(field) {

I've checked the validation, date-pickers and tooltips and they all appear to work OK.

If you find any bugs please post them here and I'll try to fix them.

Bob

PS You **must** apply the hack. This file only upgrades the front-end. The back-end (the admin area) of ChronoForms still requires MooTools 1.1.2.

PPS I also took a quick look at the Wizard in the back-end but that's a more complex task. Part of it works but the drag-and-drop doesn't drop :-(

I've applied the hack and the new files as advised above, but the validation still doesn't work.

Using Firebug, I get the following error;

$("ChronoContact_contact").getInputByName2 is not a function

I had this previously, and I disabled the mootools upgrade plugin, and the validation then worked.

Is there more that needs changed for Chronoforms frontend to work with Mootools 1.2?

Here's the form;

Contact Form

Hi messyhead,

hmm . . . I see the error but don't get it on my form. The function definition looks as though it is in the header script OK too.

Please take a Form Backup using the icon in the Forms Manager and post it here (as a zipped file) or PM or email it to me and I'll take a closer look.

Bob

Thanks for your help with this.

Here you go.

I also just tried using the mootools with the 1.1 classes, but it still showed the same error.

I was reading up about String.implement which, I think, replaced Element.extend in Mootools 1.2. But I'm not really sure, and only know very basic JS so don't really know where to start with trying to debug it.

I was looking here - migration-guide

Hi messyhead,

I hadn't tested enough. The function problem shows up when you use the Validation tab (but not if you set the validation in the Wizard). I've rewritten jsvalidation.php so that now works OK but I atill have to do JSvalidation2.php :-(

Bob

Hi messyhead,

Please will you test the attached code. The two files need to go into the components/com_chronoconteact/libraries/includes folder.

You also need to fix some bugs in the Validation tab of your form.[list]

You've used 'email2' in a couple of places where it should be 'vemail' (use input names here not ids)

The syntax for validate_confirmation is name1=name2 (not name1,name2).

[/list]

The rewritten code will no longer fail on these errors but it won't add the validations either.

Bob

Had a test of it this morning and it looks to be working ok. Thanks very much for doing this, having looked at the changes it looks like a complete re-write, so much appreciated.

As for the validation tab settings I had, I originally had the field names, but when I was getting errors I thought it was looking for the Id's. Changed them back now and it's working fine.

Now just to style the messages to how I want 😲

Hi Messyhead,

Yes I decided that it was simpler to re-write than to try to fix the problems with Max's original code. It ended up quite a lot tighter and (I hope) more robust.

I have a doc with some info on styling the validation messages here.

Bob

Hi Bob!

Thanks for "ChronoForms and MooTools 1.2.zip".

Validation works with Mootools 1.2.4 now, but not completely. Radio Validation doesn't work.

The simple form:

<div class="form_item">
  <div class="form_element cf_radiobutton">
    <label class="cf_label" style="width: 150px;">Проверка</label>
    <div class="float_left">
      <input value="Да" title="" class="radio validate-one-required" id="radio00" name="radio0" type="radio" />
      <label for="radio00" class="radio_label">Да</label>
      <br />
      
<input value="Нет" title="" class="radio validate-one-required" id="radio01" name="radio0" type="radio" />
      <label for="radio01" class="radio_label">Нет</label>
      <br />
      
<input value="Не знаю" title="" class="radio validate-one-required" id="radio02" name="radio0" type="radio" />
      <label for="radio02" class="radio_label">Не знаю</label>
      <br />
      

    </div>
    
  </div>
  <div class="cfclear"> </div>
</div>

<div class="form_item">
  <div class="form_element cf_textbox">
    <label class="cf_label" style="width: 150px;">Имя</label>
    <input class="cf_inputbox required validate-alpha" maxlength="150" size="30" title="Ошибка" id="text_1" name="name" type="text" />
  
  </div>
  <div class="cfclear"> </div>
</div>

<div class="form_item">
  <div class="form_element cf_button">
    <input value="Отправить" name="button_2" type="submit" />
  </div>
  <div class="cfclear"> </div>
</div>

Firebug shows me the error:

Error: this.retrieve is not a function
Source: http://test_site/plugins/system/mtupgrade/mootools.js
Line: 1

When I include

<?php JHTML::_('behavior.mootools'); ?>

code to "Form HTML" or "Form JavaScript" there isn't this error, but Radio Validation doesn't work anyway.😟

When I switch off Mtupgrade plugin, Radio Validation works.

The link to the form.

Login is the same, if it's needed.

Hi T34,

Please test the updated jsvalidation2.js file from the attached zip file (the customclasses.js file is unchanged).

Bob

Later: please see the updated version later in the thread.

Please test the updated jsvalidation2.js file from the attached zip file.

Hi Bob!

I have update jsvalidation2.js file, and it shows me "Please select one of the options", even if I select one of the radio buttons.

Hi T34,

:-( Thanks - back to the drawing board . . .

Bob

Hi T43,

Updated - there was one 'return' I left out.

Bob

PS Note that for a check-box array each input needs to have the validate-one-required class for this to work correctly.

Hi Bob!

Thanks!!! It validates correctly now! 😀

But when I use "Transform Form" option selecting "theme1" view, I see that the message about error (Please select one of the options) repeats 3 times - 1 time for each button, directed horizontally:

So it's impossible to use it as module in the right or left position of the "vertical" templates.

Hi T34,

OK - Added to the To-Do list for the weekend.

I have just created a version that will use a Joomla! language file for the error messages too.

Bob

Thanks Bob!

I'd like to use Chronoengine as a very important part of my site, so I'm waiting Monday! 😀

The language support shall be very useful, I think. It's very good idea.

Hi T34,

Please will you test the attached files. The problem with the multiple messages was that the message was attached to the parent of the input - and in the Transformed version that is the label. This version is modified to look for the 'next' parent if it finds a label.

These files should also use the error messages defined in the com_chronocontact.ini file.

Bob

\language\en-GB\en-GB.com_chronocontact.ini
These are the validation error messages, you should add a translated version in ru-RU

\components\com_chronocontact\libraries\includes\JSvalidation.php
This version is modified to use JTEXT to add the error messages from the language file

\components\com_chronocontact\libraries\includes\JSvalidation2.php
This file now does nothing but is a dummy to replace the previous ChronoForms file

\components\com_chronocontact\js\jsvalidation2.js
This is the updated script file to work with MooTools 1.2 and use the translated error messages

\components\com_chronocontact\js\customclasses.js
This script file is also updated to work with MooTools 1.2

Hi Bob!

Thanks a lot! 🙂

I have begin to translate, but I'm nub🙂 and don't understand the difference between VALIDATE_NUMBERS and VALIDATE_DIGITS. Would you can explain me this difference?

Hi T34,

Looking at the code there is no difference :-( Both use the LiveValidation "Numericality" test.

Originally the difference was that 'digits' allowed only [0-9]; and number allowed any valid number (the test was the Javascript !isNaN)

Bob

Hi Bob!

I have work a little this Saturday and should like to show you the modified path, included the manual in English and in Russian ("!README.TXT" file in archive).

There are the some additional features now.

"!README.TXT":

====================================================================
FOR USERS WHO DON'T USE THE RUSSIAN LANGUAGE
====================================================================


-------
Read the manual in "ChronoForms and MooTools 1.2.pdf" file, then copy the contents of "files" folder to the root folder of your site (/public_html usually), included files of "administrator" folder (there are not the instructions of this file in PDF manual, but you need to do that for using the additional features).
-------

Additional features: 


I. Alpha and AlphaNum validate not only Latin symbols, but Cyrillic symbols too, included the letters "ё" and "Ё".

II. Usage the Digit Validation as the REALLY digit validation: real "digits only" — instead "numbers only", as the original version of Chronocontact component offers.


III. Usage the Digit Validation for the validation of international mobile phone numbers:

	1. Open the file "/components/com_chronocontact/js/jsvalidation2.js";
	
	2. Run to the line 96 under lhe line "//Digit Validation:" (95);
	
	3. Comment the line "pattern:..." (line 96);
	
	4. Uncomment the line 94 under the line "//Mobile Phone Numbers Validation:" (93);
	
	5. Save the modified file "/components/com_chronocontact/js/jsvalidation2.js" using the original encoding. 
	
	6. Modify the validation message of your form using Backend of Joomla.


IV. Changing the function "validation currency" to the carrency that you need to validate in your form (if there is the carrency field in this form).

The carrency validation feature is set to "universal" by default — i.e. you don't need to include the currency symbols to the input field. For changing carrency validation to Dollar ($), Euro (€) or Rubles (" руб."):

	1. Open the file "/components/com_chronocontact/js/jsvalidation2.js";
	
	2. Run to the line "//Carrency validation" (line 167);
	
	3. Comment the line "pattern:..." (line 184) under the line "//Universal pattern without currency indication" (line 183);
	
	4. Uncomment the line that you need (172, 175 or 181) under the "//Carrency validation" (line 167);
	
	5. Save the modified file "/components/com_chronocontact/js/jsvalidation2.js" using the original encoding.

-------
Patch author: Bob Janes aka GreyHead (www.GrayHead.net)
Additional features author: Kirill Svetitskiy aka T34 (swetit@gmail.com, www.Svetitskiy.com)


====================================================================
РУССКОЯЗЫЧНЫЙ МАНУАЛ
====================================================================

Данный патч позволяет использовать компонент Chronoforms для CMS Joomla! совместно с плагином "System - Mootools Upgrade".

Установка патча делает возможным одновременное использование Mootools 1.0 для Backend (что требует Chronoforms 3.1 RC5.5) и Mootools 1.2 для Frontend, что могут требовать некоторые шаблоны и иные расширения Joomla.

-------
Для установки патча:

1. В текстовом редакторе, позволяющем редактировать исходный код, откройте файл plugins/system/mtupgrade.php и перейдите к функции onAfterInitialise() в самом конце кода (строка 46). Замените эту функцию на следующую:

function onAfterInitialise()
  {
     global $mainframe;
     if ( $mainframe->isSite() ) {
        JHTML::addIncludePath(JPATH_PLUGINS.DS.'system'.DS.'mtupgrade');
     }
  }

2. Скопируйте содержимое папки "files" в корень вашего сайта.
-------

Патч расширен и адаптирован для России:


I. Валидация Alpha и AlphaNum теперь допускает ввод не только латиницы, но и кириллицы, включая буквы "ё" и "Ё".


II. Валидация Digit теперь действительно разрешает только цифры — и ничего, кроме них.


III. Возможно использование валидации Digit для проверки номеров мобильных телефонов как в международном, так и в российском форматах, например 8 (916) 123 45 76 или +39-098-334-7654.

Чтобы включить это расширение:

	1. Откройте в текстовом редакторе, позволяющем редактировать исходный код, файл "/components/com_chronocontact/js/jsvalidation2.js";

	2. Закомментируйте строку 96, расположенную под строкой "//Digit Validation:" (95);

	3. Раскомментируйте строку 94, расположенную под строкой "//Mobile Phone Numbers Validation:" (93);

	4. Сохраните изменённый файл "/components/com_chronocontact/js/jsvalidation2.js" в той же кодировке.
	
	5. Измените текст об ошибке валидации, используя панель управления вашей формой в административной панели сайта.


IV. Возможна валидация ввода валюты не только в долларах США (символ "$" перед числом), но также в любой иной валюте (без её указания) или с указанием Евро (как символа "€" перед числом) и Рубля (" руб." после числа).

По умолчанию установлена валидация без указания типа валюты. Чтобы иметь возможность валидации нужного Вам типа валюты:

	1. Откройте в текстовом редакторе, позволяющем редактировать исходный код, файл "/components/com_chronocontact/js/jsvalidation2.js";

	2. Перейдите к строке 156 и действуйте согласно расположенной там инструкции.
	
	3. Сохраните изменённый файл "/components/com_chronocontact/js/jsvalidation2.js" в той же кодировке.
	
-------
Автор патча: Bob Janes aka GreyHead (www.GreyHead.net)
Автор расширений: Кирилл Светицкий aka T34 (swetit@gmail.com, www.Svetitskiy.com)
====================================================================

May be it helps users of Chronoforms to be happy. 😀

The modified patch is: CF_MooTools_1.2_v.2.zip

Thanks a lot for your real help!

Hi Bob!

I bring a bad news — your patch works perfectly only with the forms created using the original files of CF. 😟 I have try to create a new form and I've see that mootools doesn't work when I open the new form in browser.

The palliative is to rewrite the new files by original one, create new form and rewrite old files by new. But it's too inconveniently, I thing.

Would you can check the creation function of your patch and correct it, if it's possible?

Hi T34,

This is the radio button group 'select one required' validation? What is the HTML that isn't working?

There has to be a parent tag that wraps the buttons for the validator to work. Like

<div>
<input type='radio' . . . />
<input type='radio' . . . />
<input type='radio' . . . />
</div>

or

<div>
<label. . .><input type='radio' . . . /></label>
<label. . .><input type='radio' . . . /></label>
<label. . .><input type='radio' . . . /></label>
</div>

The wrapper can be a <div> or a <td> or a <span> or a <p>.

Bob

Hi Bob!

Sorry, I've forget to write the important information: I have a wrong form created by "Form wizard".

Then I've try to include

<?php JHTML::_('behavior.mootools'); ?>

code to HTML, but there isn't effect.

There is a very simple test form here.

Also you may see this form HTML etc. in admin panel using the login that I've send you previously.

Hi T34,

Sorry, I missed a line in libraries/includes/JSvalidation.php

Bob

$script .= "
var sel = null;
var sel_0 = null;
var message_required = '".JTEXT::_(VALIDATE_REQUIRED)."';
var message_validate_number = '".JTEXT::_(VALIDATE_NUMBER)."';
var message_validate_digits = '".JTEXT::_(VALIDATE_DIGITS)."';
var message_validate_alpha = '".JTEXT::_(VALIDATE_ALPHA)."'; // <-- add this line
var message_validate_alphanum = '".JTEXT::_(VALIDATE_ALPHANUM)."';
var message_validate_date = '".JTEXT::_(VALIDATE_DATE)."';
var message_validate_email = '".JTEXT::_(VALIDATE_EMAIL)."';
var message_validate_url = '".JTEXT::_(VALIDATE_URL)."';
var message_validate_date_au = '".JTEXT::_(VALIDATE_DATE_AU)."';
var message_validate_currency_dollar = '".JTEXT::_(VALIDATE_CURRENCY_DOLLAR)."';
var message_validate_match = '".JTEXT::_(VALIDATE_MATCH)."';
var message_validate_one_required = '".JTEXT::_(VALIDATE_ONE_REQUIRED)."';
var message_validate_selection = '".JTEXT::_(VALIDATE_SELECTION)."';
";

Hi Bob!

I see that it's impossible to submit form using this path. You may press the button "Submit", but nothing happens.

You may see this effect here.

When you place the original files again, submit works.

Also the language support doesn't work properly in mod_chronocontact and ChronoForms_Plugin. If you don't insert the validation message manually in "Form Wizard" or "Form HTML", you will see only

VALIDATE_REQUIRED

message instead the message from language *.ini file.

If you will insert the validation message manually only in one field of the form, you will see the

VALIDATE_REQUIRED

too near all the fields before and the message that you have insert manually near all the fields after.

It's a bad news for me because I need mod_chronocontact and ChronoForms_Plugin in my site properly.

Would you can to repair this bugs, if it's possible?

Hi T34,

Ok - on the To-Do list but won't be instant :-(

Bob

Hi Bob!

Thank you. 🙂

I was hoping this would fix my problem but disabling mootools did nothing for me...

Any other suggestions on how to get this working correctly.

Step 1 with the wizard is disabled. None of the tools seem to function.

Hi Bspears,

What have you disabled?

MooTools must be enabled - it's just the MooTools Upgrade plug-in that needs to be disabled.

Bob

I apologize, It was the mootools upgrade I disabled.

Hi Bspears,

Hmmm . . . that's usually the problem when this symptom appears. It's probably some other JavaScript conflict :-(

By all means email or PM me the site URL and a SuperAdmin login and I'll take a quick look.

Bob

I sent you the PM. Thanks for taking a look.

Hi Bob!

I have enable the displaying of the error messages on my site today and I see the notice message now:

Notice: Undefined variable: script in /home/rasstan9/public_html/components/com_chronocontact/libraries/includes/JSvalidation.php  on line 5

There are 5 lines in the beginning of JSvalidation.php:

<?php
defined('_JEXEC') or die('Restricted access'); 

$formname = "ChronoContact_".$MyForm->formrow->name;
$script_domready = $script = "";

Your To-Do list, may be, needs this message. 🙂

Hi T34,

Hmmm I've not seen that one before, I think it must be the a = b = c; syntax.

Try making it

$script_domready = "";
$script = "";

Bob

Hi Bob!

I have modify that file, and there aren't notices now.

Thanks a lot!

Could you take us into confidence, when approximately the mankind shall be happy using your fixed mootools patch? 🙂

Hi T34,

It's not forgotten - but no firm date or time either. Just plain busy at the moment :-(

Bob

Hi Bob!

Good luck in your affairs. The mankind can wait a little, I think. :wink:

Hi BSpears'

It all seems to be working fine from here. I created a form and submitted it OK. I used FireFox but I don't think that makes any difference in this case.

Exactly what symptom do you see?

Bob

Hello, I am also interested in downloading replacement files to patch my chronoforms to work properly (at least in the front end) . Since there seems to be a lot of files and updates here, can you tell me which exact download(s) here are the right ones, or if I need to wait until they are ready. Thanks🙂

Sorry... should I just download the files from the download area and re-install or are there other files that I need to alter and/or install by hand? Sorry... things are not very clear to me here.

Hi paxman!

can you tell me which exact download(s) here are the right ones, or if I need to wait until they are ready. Thanks🙂

You, and I, and other persons need to wait. This patch doesn't work correctly now, and Bob have promise to repair them. Now you can download the latest archive of Bob or the latest my archive for testing them and for report the new errors, if they will have place during the work of patched CF.

Also you can wish Bob to finish his affairs successfully and begin to repair this path. 🙂

Hi Paxman & T34,

I'm a bit lost in the versions too but I think that the fix posted in the How-To doc at Greyhead.net works for a standard form unless you: [list]

Use an alternative theme that puts the inputs inside the <label></label> tags and need validate-one-required

or you need to use the ChronoForms plug-in or mambot. Those files have not been updated.

[/list]
Bob

Hi Bob!

Yes, it's right. The "standard" patch from GrayHead.net works correctly ONLY using the standard theme (not alternative of "Transform Form" option), ONLY without validation "one required" (radiobuttons or checkboxes).

This "standard" patch doesn't works correctly as plugin and as module using any theme.

The updated versions from this topic are experimental.

So waiting for solution.

Hi T34,

I finally got back to this. I think I have found the problem with the Transformed forms; and I've add the code to load the language files so that they are present when the module or plug-in are used.

The full package of files is attached but I think the only file changed is JSvalidation.php

Bob

\language\en-GB\en-GB.com_chronocontact.ini
These are the validation error messages, you should add a translated version in ru-RU

\components\com_chronocontact\libraries\includes\JSvalidation.php
This version is modified to use JTEXT to add the error messages from the language file

\components\com_chronocontact\libraries\includes\JSvalidation2.php
This file now does nothing but is a dummy to replace the previous ChronoForms file

\components\com_chronocontact\js\jsvalidation2.js
This is the updated script file to work with MooTools 1.2 and use the translated error messages

\components\com_chronocontact\js\customclasses.js
This script file is also updated to work with MooTools 1.2

Hi Bob!

Unfortunately this files don't work properly too.
Radio validation is wrong.
The error is using transformed form. If I select radio button I take the message "Please select one of the options" anywhere. You can see it on my site (you know the address🙂 ).

Is any way to fix it?